https://linen.dev logo
Powered by
# haxe-ui
  • m
    The visuals I'm going for a basically what you did here (http://haxeui.org/builder/?ixeqjy), but I'm not sure how to achieve it with haxeui-flixel
  • f
    What's the appropriate event to listen to for when a ListView's selected index changes? Originally I was listening to 
    ItemEvent.COMPONENT_EVENT
    but I think that's wrong. Mouse click might work, but I'm not sure about edge cases and it triggers even if empty space in listview is clicked 🙂
  • f
    Ah nevermind, 
    UIEvent.CHANGE
    of course 😄
  • f
    New question, is there a way to determine whether the mouse is actually over something, not obscured? Perhaps this is a bug, but all the events for my world canvas box are triggering through this menu (which means the mouse cursor is hidden)
  • f
    I tried getting the length of 
    rootComponent.findComponentsUnderPoint(mouse)
    but bizarrely it doesn't seem to change when the mouse is over the menu
  • b
    hmmm, i would have expected findComponentsUnderPoint to work
  • b
    what about using the screen?
  • b
    something like Screen.topLevelComponents[0].findComponentsUnderPoint(...)
  • b
    (sounds like it would be useful to have a util function in screen also)
  • f
    Screen.instance.rootComponents[0].findComponentsUnder...
    doesn't work either, strange 🤔
  • f
    Well, it just usually returns 4 (sometimes 3 if on the edge, but not changed by the open menu)
  • b
    what about iterating through all the rootComponents on the screen?
  • b
    the menu will probably another rootcomponnet
  • b
    ill add a util function to do it, but for now just to see if it fixed the issue
  • f
    Ah yep, that's it. It prints 4 when the menu is closed, and 1 and 4 when the menu is open. So one heuristic would just be 'is there one root component'
  • f
    I'll have to see whether the dialog that pops up for export is a second root component too
  • b
    ill add a "Screen.instance.findComponentsUnder" which will iterate over the root components... keeps things tidy
  • f
    That might be useful indeed, but perhaps not for my particular issue. I'll solve mine with the rootComponents length check now I think. Should events like mouse over be triggering if they're hidden by a menu?
  • b
    hidden components shouldnt get any interactive events, no
  • b
    why wouldnt it help in your case?
  • b
    find all the components and a give point... if one of them is menu, then dont hide the mouse when its over you canvas?
  • b
    if (inCanvas && Screen.findComponentsUnderPoint.contains(myMenu)) ...
  • f
    It probably would work, but means that this code has to concern itself with menus, dialogs etc, which ideally it shouldn't
  • b
    another nice addition would be the abilty for findComponentsUnderPoint to be able to filter based on class type (like findComponent)... then you could just have:
  • b
    if (inCanvas && Screen.findComponentsUnderPoint(Menu).length > 0) ...
  • f
    Mmh. I'm also wary because this runs per frame when the mouse is moving in the canvas, because it's a MOUSE_MOVE handler. Doing full tree traversal is probably not ideal for that
  • b
    hmmm, right
  • b
    that sounds costly
  • b
    so how are you planning to do it? Just by the length of rootComponents?
  • f
    This works at the moment. If a menu is open, the cursor is shown even if the menu isn't directly hovered over, which I think I'm fine/happy with
1...521522523...1687Latest