https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • q
    (There's nuance and flexibility and the devil in the details, like everywhere.)
  • q
    I plan to poke this hard next time I'm at my codebase.
  • b
    hmmm, right, i think i see what you mean conceptually... would it be possible to create an issue on haxeui-flixel with a small test case? I dont really know the internals of flixel (like this is the first ive heard about substates) so would be good to be able to run some code and see where it goes weird / wrong
  • q
    That is the plan šŸ˜ƒ
  • b
    great, thanks!
  • u
    Test
  • u
    ping :)
  • q
    But does it work both ways?
  • q

    https://cdn.discordapp.com/emojis/502861002069639171.gifā–¾

  • b
    Good this gives me an excuse to delete gitter off my phone
  • b
    oh thats intersting... nice one
  • s
    @bright-gpu-74537 I'll try to get back to you later this week after my travel is done. Did you try the kha app I linked? I'm feeling like it's likely to be something I'm doing in my layouts. I'm building everthing in code instead of xml, and I'm wondering if that's why I'm having issues.
  • u
    Rōnin Announcement - Restarting Bridge
  • q
    What I have for followup on that isn't a broken mess, actually. @brave-kangaroo-30399 's method seems to be the one covered in Could we maybe work this class in as a shim?
  • q
    That's a bit much, I'm sure.
  • q
    That's the gist of the four folders there.
  • b
    I'm frankly surprised this went as well as it did.
  • b
    šŸ˜„
  • b
    so does "ideal" work? Thats how i think i would have used it, again, not knowing anything about flixel though
  • b
    I guess Iā€™m more worried about memory leaks than it not working from my suggestion, I know it works
  • b
    And the haxe UI substate kinda defeats the purpose of HaxeUI, which is to blend seamlessly into your existing workflow
  • b
    The UI state is how flixel-UI did it, and itā€™s limiting if you want a custom state or substate class
  • b
    whats wrong with the "ideal" method though? Isnt that valid?
  • b
    What the ideal isnā€™t doing is hiding the ā€œoldā€ UI when it would display the substateā€™s one
  • b
    Hiding, deactivating, etc
  • b
    ah
  • b
    My way removes them all from the active container in a sense, which (maybe) is the same as deactivating them
  • b
    right
  • b
    yeah, i mean, you could also just use 
    Screen.instance.addComponent
    and 
    Screen.instance.removeComponent
    i guess?
  • b
    the component would be a view, which would be, like a substate
1...303132...1687Latest