https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    yeah, all events are... i mean, haxeui-core doesnt even really know what an event really means (so to speak)
  • b
    I'll do the quick fix in the backend then play around with it in a project, see if anything else is necessary
  • b
    in fact, you already have 
    FlxUIMouseEventManager
  • q
    shrugs I'll be here, breaking things 😉
  • b
    Yeah you're right I may be able to handle it in there
  • b
    Idk, I'm also just assuming 
    active
    gets set when states are disabled
  • b
    I should double check
  • b
    i think the screen should never be deactivated though... as you say, you'll need that for "clicked outside a dropdown, hide the dropdown list"
  • b
    focus might be an issue here though
  • b
    if you had a deactivated state and another ontop... then i think you could be tabbing all the disabled states too
  • b
    can you override the "active" prop?
  • b
    or is it "var active:Bool"
  • b
    ?
  • b
    It's 
    (default, set)
  • b
    ok, so wrt to the focus you could set "allowFocus" to whatever is set
  • b
    Yeah
  • b
    so maybe, for now at least, the way to handle it is the backend?
  • b
    ... actually now I'm wondering if the substate mouse event thing has anything to do with haxeui...
  • b
    I don't think the normal mouse manager would check either
  • b
    no idea how the mouse manager works
  • b
    Hmm
  • b
    Yeah this doesn't work in flixel either
  • b
    Welp
  • b
    oh... so disabled sub states always get mouse events?
  • b
    It doesn't set any property of the children, so yes
  • b
    or inactive states i mean
  • b
    It no longer updates the children, but they are still active and visible as far as mouse events are concerned
  • b
    right
  • b
    well, at least haxeui-flixel is the same as flixel 😄
  • b
    I'll have to try it with real code, but it seems like it's a flixel thing
1...606162...1687Latest