https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • q

    quick-king-64105

    07/01/2019, 11:44 AM
    The only problem is that you have to put that check on every event handler. The exact thing MSGhero is hoping to avoid.
  • q

    quick-king-64105

    07/01/2019, 11:44 AM
    So I'll be doing that and hoping and praying for something better 😦
  • q

    quick-king-64105

    07/01/2019, 11:45 AM
    And, yes, I agree - it's really not fun or good or pretty code.
  • q

    quick-king-64105

    07/01/2019, 11:45 AM
    And probably innefficient and a million other whingy things to put here.
  • b

    brave-kangaroo-30399

    07/01/2019, 11:56 AM
    Mouse handling is done in a plugin which isn’t tied to a state
  • q

    quick-king-64105

    07/01/2019, 11:57 AM
    Okay. Could we somehow chain it to the update cycle?
  • b

    brave-kangaroo-30399

    07/01/2019, 11:57 AM
    Not without modifying flixel
  • q

    quick-king-64105

    07/01/2019, 11:57 AM
    No way to manually call the mouse handler's "update" (or whatever) step, huh?
  • q

    quick-king-64105

    07/01/2019, 11:58 AM
    Bummer 😦
  • b

    brave-kangaroo-30399

    07/01/2019, 11:58 AM
    Nah, it’s run every frame before any state gets updated
  • b

    brave-kangaroo-30399

    07/01/2019, 12:00 PM
    The core issue is that there’s some kind of parent-child relationship that needs to be established for this kind of thing, and flixel doesn’t have parents
  • q

    quick-king-64105

    07/01/2019, 12:00 PM
    What is the idiomatic way to open a "sub-ui" in haxeui anyway? That would be the other way around it and then we just slap "caveat emptor, known workaround, yes we're sorry" all over it.
  • q

    quick-king-64105

    07/01/2019, 12:00 PM
    Define "parent". Because states are parent/child and groups are parent/child.
  • b

    brave-kangaroo-30399

    07/01/2019, 12:01 PM
    I think you would just add a new UI over the first one
  • b

    brave-kangaroo-30399

    07/01/2019, 12:01 PM
    The child has no access to the parent
  • q

    quick-king-64105

    07/01/2019, 12:01 PM
    Child... what?
  • b

    brave-kangaroo-30399

    07/01/2019, 12:01 PM
    It could have multiple parents
  • b

    brave-kangaroo-30399

    07/01/2019, 12:01 PM
    It has no idea if it’s part of the current state
  • q

    quick-king-64105

    07/01/2019, 12:01 PM
    Okay, you mean sprites in general.
  • q

    quick-king-64105

    07/01/2019, 12:02 PM
    Well, I guess FlxObjects, at a base level.
  • q

    quick-king-64105

    07/01/2019, 12:02 PM
    Substates interact with their parents directly and have a pointer. That's the only one I know OTOH, and only because I stared at it this morning.
  • q

    quick-king-64105

    07/01/2019, 12:02 PM
    That doesn't help when you want FlxObjects, however. I know.
  • b

    brave-kangaroo-30399

    07/01/2019, 12:08 PM
    Mmk I think I figured it out
  • b

    brave-kangaroo-30399

    07/01/2019, 12:08 PM
    Just need to find time to code...
  • q

    quick-king-64105

    07/01/2019, 12:13 PM
    could we... Use whether or not it's within world bounds considering most UIs should be stationary and focused? Ask FlxState if contains a specific member making use of FlxGroup iterator? (Think this would have to be recursive search, may be easier way) Poke Grey hard in the ribs and tell her that she needs to be faster if she has ideas that might not be useless?
  • q

    quick-king-64105

    07/01/2019, 12:14 PM
    Do ya thing. I had already typed it.
  • b

    brave-kangaroo-30399

    07/01/2019, 12:19 PM
    I added
    memberAdded
    to FlxGroup I think in order to make flixel at all compatible with HaxeUI
  • b

    brave-kangaroo-30399

    07/01/2019, 12:19 PM
    I guess like the most basic ā€œchild is aware it has a parentā€ kind of thing
  • q

    quick-king-64105

    07/01/2019, 12:20 PM
    facepaws
  • q

    quick-king-64105

    07/01/2019, 12:20 PM
    That's right. Haxe supports dynamic compile-time extension.
1...747576...1687Latest