@:behaviour

- these are pretty complex, but basically haxeui is behavior driven, this means that when you call "myButton.text" rather than that lead directly to some code that does stuff it leads to a behviour that does stuff - the reason is because haxeui is cross framework and supports native backends... Backends are split into two broad categories: Composite (where haxeui handles all the internals) and Native (where haxeui delegates component creation and behaviours to a backed). So take openfl and hxwidgets: .text leads to a default behaviour (which is a composite based beahviour) which will create a haxeui Label component, add it to the button, tell haxeui the composite layout is invalid and get it recalc all that - that'll kick in for composite backends (openfl, nme, kha, heaps, etc, etc)... however, for native backends that aint gonna work, the component is a native button window and we dont want to add a label to that (as its handled by the native framework) and we dont control the layout. So the behaviour that gets called is overridden from that composite one, to one that can do anything it wants (in this case it will set the text of the underlying native button text directly)

for the most part you wont really need to use that, unless you are creating you own cross framework component suite

clonable and bindable are arguably more important but only if you are creating your own custom components ofc (and want them to work with things like ItemRenderers, which uses cloneComponent) and have xml accessible binding

sorry for the "wall of text"... 😄

O_o thanks -a lot- for this great answer. I'll have a lot to do/try with it :D I will try the validateComponentData call which seems to be what i'm searching for (I already made a subclass of ItemRenderer) and play around with all the rest of your advices Thanks again. it's very appreciated.

No worries, let me (us) know how you get along and if you hit and roadblocks 🙂

sure 😉

I don't understand thde program flow. the flow starts at: main.hx calls MenuState goto MenuState.hx then calls clickplay and goto playstate. after that i have no idea how the program calls coin and player.hx. This is the tutorial on:https://haxeflixel.com/documentation/tutorial/

how it using the coin.hx and player.hx??

package; import flixel.FlxG; import flixel.FlxObject; import flixel.FlxState; import flixel.addons.editors.ogmo.FlxOgmo3Loader; import flixel.group.FlxGroup.FlxTypedGroup; import flixel.text.FlxText; import flixel.tile.FlxTilemap; class PlayState extends FlxState { var player:Player; var map:FlxOgmo3Loader; var walls:FlxTilemap; // var coins:FlxTypedGroup; var coins:FlxTypedGroup; override public function create() { map = new FlxOgmo3Loader(AssetPaths.turnBaseRPG__ogmo, AssetPaths.room_001__json); walls = map.loadTilemap(AssetPaths.tiles__png, "walls"); walls.follow(); walls.setTileProperties(1, FlxObject.NONE); walls.setTileProperties(2, FlxObject.ANY); add(walls); coins = new FlxTypedGroup(); add(coins); // player = new Player(20, 20); player = new Player(); map.loadEntities(placeEntities, "entities"); add(player); FlxG.camera.follow(player, TOPDOWN, 1); super.create(); } function placeEntities(entity:EntityData) { if (entity.name == "player") { player.setPosition(entity.x, entity.y); } else if (entity.name == "coin") { coins.add(new Coin(entity.x + 4, entity.y + 4)); } } override public function update(elapsed:Float) { super.update(elapsed); FlxG.collide(player, walls); FlxG.overlap(player, coins, playerTouchCoin); } function playerTouchCoin(player:Player, coin:Coin) { if (player.alive && player.exists && coin.alive && coin.exists) { coin.kill(); } } }

Main -> MenuState -> PlayState

I don't understand thde program flow. the flow starts at: main.hx calls MenuState goto MenuState.hx then calls clickplay and goto playstate. after that i have no idea how the program calls coin and player.hx. This is the tutorial on:https://haxeflixel.com/documentation/tutorial/

yes , but after that .. on the playstate.hx how is it using player.hx and coin.hx?

just a reminder by the way, this isnt a flixel room, its specific to haxeui... you'll get better answers in #165234904815239168 and generally this room is for haxeui questions

sorry.

i think i've tried there and no one answered.

its fine, just for you, you'll get better answers there and other users (who arent interested in flixel) wont get flooded by non-haxeui related questions

right, they'll answer eventually hopefully :) Im no flixel expert (though some people here are) but for general flixel questions i would still probably advise to ask there

i asked a question a few hours ago and still nonone answered.. it's not as active there.

i understand you're not an expert on flixel but you know your way around haxe. so i figured i ask here.

fair enough, still doesnt really change the fact that this isnt a flixel room and any advice you do get here will be from flixel people who know more about flixel than i do

sure, i dont mind answering general haxe question (even flixel ones) - ill help if can, but just dont want this turning into a "flixel2" room 🙂

ok..

i guess i'll work on it tomorrow..

did the answer i gave not enough info?

that the PlayState uses Coin class

PlayState creates and array of "Coins" which is built inside "placeEntities"

just a few quick questions. are you making a game ??

nope