https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    and what does that mean? No mouse events?
  • b
    Means it doesn’t get `update`d
  • b
    So no events
  • b
    right
  • b
    ok, and so whats the issue?
  • b
    inactive haxeui-flixel states still get events?
  • b
    Yeah, like a pop up menu would typically disable whatever UI is underneath it
  • b
    Or behind it in layers I should say, it may not cover all UI elements below
  • b
    right, i see
  • b
    I could do it in CompImpl, by ignoring mouse events if it’s inactive
  • b
    But I’m wondering if that covers everything
  • b
    wouldnt it be haxeui-flixels job to respond (or honour) active = false?
  • b
    i just mean, what does "deactivated" mean to haxeui-core?
  • b
    Yes but does that happen in the mouse handler or in something that core overrides
  • b
    I was comparing it to visible
  • b
    Or hidden? Whatever core calls it
  • b
    right, like 
    handleVisible
    or something?
  • b
    HandleActive?
  • b
    Not sure it makes sense
  • b
    Just wanted to talk it out before committing something
  • b
    i mean, its possible, ofc...
  • b
    and, it doesnt have to make sense for everything, esp with the new hierarchy
  • b
    i wonder if the path of least resistance at the moment is to avoid core changes, and just skip mouse events in haxeui-flixel
  • b
    (in active = false)
  • b
    and if it, indeed, doesnt cover everything then we look at possibly adding a deactivated to core?
  • b
    though im still unsure what deactivated would actually achieve being core
  • q
    I would be concerned about what other events haxeui is listening for.
  • b
    All events are routed through the backend though right?
  • q
    No input or update events should happen to the parent state when a substate is active and saying "pause parent" (which is default)
  • b
    I guess even Screen events are...
1...596061...1687Latest