# haxe-ui
- k
kind-policeman-40412
07/30/2020, 4:37 AMI mean there's nothing related to haxe ui except the invalid call )) - k
kind-policeman-40412
07/30/2020, 4:38 AMš© - f
fast-rain-20339
07/30/2020, 4:40 AMYou've probably said this before, but what target? Can you build for a different target? - f
fast-rain-20339
07/30/2020, 4:40 AMoh neko - k
kind-policeman-40412
07/30/2020, 4:40 AMyeah - f
fast-rain-20339
07/30/2020, 4:40 AMYeah try JS or native, if you can. Often the errors are different and sometimes more useful. - k
kind-policeman-40412
07/30/2020, 4:40 AMI can build for linux hxcpp but it still trows - k
kind-policeman-40412
07/30/2020, 4:41 AMthrows ) - f
fast-rain-20339
07/30/2020, 4:41 AMDifferent error? - k
kind-policeman-40412
07/30/2020, 4:41 AMsame š - f
fast-rain-20339
07/30/2020, 4:41 AMUnforunate :/ - f
fast-rain-20339
07/30/2020, 4:41 AMJS? - k
kind-policeman-40412
07/30/2020, 4:43 AMoh not the same actually. I've just mixed things a bit as I tried a lot in process. Now the linux target works and even registerEvent works and callback is successfully fired. But I've seen that already. Wait a sec I will try to access ui.joinButton and ui.joinButton.onClick. - f
fast-rain-20339
07/30/2020, 4:43 AMš - k
kind-policeman-40412
07/30/2020, 4:44 AMCopy codeā client git:(haxeui) ā lime run linux source/vortex/shooter/Game.hx:82: resize: [932x1021] source/vortex/shooter/states/TitleState.hx:38: new() source/vortex/shooter/states/TitleState.hx:100: onActivate() source/vortex/shooter/states/TitleState.hx:110: onDestroy() source/vortex/shooter/states/LobbyHaxeUIState.hx:49: new() source/vortex/shooter/states/LobbyHaxeUIState.hx:135: onActivate() source/vortex/shooter/states/LobbyHaxeUIState.hx:69: onReady -> ui:,[object Box] source/vortex/shooter/states/LobbyHaxeUIState.hx:70: onReady -> event:,UIEvent - f
fast-rain-20339
07/30/2020, 4:44 AMš Looks as expected. - k
kind-policeman-40412
07/30/2020, 4:44 AMyeah. but I'm confused even more because why it does not work for Neko then ))) - f
fast-rain-20339
07/30/2020, 4:45 AMMe too, though macro magic is involved, so might be something to do with how it's built? Not sure, I'll say it again, Ian'll know more š - f
fast-rain-20339
07/30/2020, 4:45 AMI would recommend using classes with the build macro thing, they've worked really well for me and my code feels organised. - f
fast-rain-20339
07/30/2020, 4:46 AMThey're also very easy to use š - k
kind-policeman-40412
07/30/2020, 4:48 AMOhh, I wanted to try HaxeUI exactly because of xml support. I already have my UI written with OpenFL except there's a lot of boilerplate code for layout, resizing, etc - f
fast-rain-20339
07/30/2020, 4:49 AMAh, maybe you misunderstand - I still use XML š - k
kind-policeman-40412
07/30/2020, 4:49 AMoh yes, but you told you have a separate class for every xml component? - f
fast-rain-20339
07/30/2020, 4:50 AMThe xml is applied via a macro to the classes - f
fast-rain-20339
07/30/2020, 4:50 AMYeah. - k
kind-policeman-40412
07/30/2020, 4:53 AMThat pretty much ruins all the fun for me as I already have States and StateStack. So I have separate State for every screen. All the context and initialization and logic for given State is contained within that State class. The best way would be just pass my State context into the Component and access that context properties and their methods. - f
fast-rain-20339
07/30/2020, 4:54 AMhm - k
kind-policeman-40412
07/30/2020, 4:54 AMBut I'll think about your solution as well )) - k
kind-policeman-40412
07/30/2020, 4:54 AMMaybe it's still good to go. - f
fast-rain-20339
07/30/2020, 4:54 AMI'm not quite sure I understand, but at the very least, your way doing things should at least work. See what Ian says š