https://linen.dev logo
Join Discord
Powered by
# ceramic
  • b
    But that could be tricky, not sure field access restriction works well with my events macros
  • o
    I expect it is not easier in the Kha api...if you look at how that is done.
  • o
    that was suggestion to NotBilly
  • a
    I don't have the states context though afaik
  • b
    @ambitious-knife-25690 when in doubt about using some object api, feel free to double check with me that it won’t should you in the back 😁
  • a
    i think that's why kha needed a whole custom setup, because the logic had to be moved to the haxeui-kha side
  • b
    Yeah I don’t know how that is supposed to be on haxeui side so state might not be the right word
  • a
    yeah, i'm ignorant enough on both haxeui and ceramic to not be sure of my answers 😅
  • a
    but it seems like, if I can only get 1 event from a mouse interaction per hierarchy it isn't clear to me where to go from here
  • a
    because whilst i may get a visual with the interception route, i have no idea what said visual does or if it needs focus or not
  • b
    You can retrieve any visual in the hierachy from the hitting one, so imo everything is possible
  • b
    But @bright-gpu-74537, what are the rules regarding events in haxe ui?
  • a
    haxeui sends 
    mouse_down
    flag to backend, backend spits out event
  • a
  • b
    When does haxeui send mouse_down flag?
  • a
    this is the current event map implementation
  • a
    from a component, that is in haxeui-core, not in haxeui-ceramic
  • o
    You can do flat mouse api's ... for instance in Kha, you might find you need to do similar in ceramic?
  • o
    there is a test demo link
  • b
    so, when you say in haxeui "add a listener for down", it calls the backend mapEvent, this should only ever add one listener in the backend component, multiple events of the same type will be handled by core (from the single event in the backend). As for sending "mouse downs" or something, that never happens, haxeui simple restyles components based on events... the backend will never (by default) know its "down"
  • b
    Ah so haxeui is calling mapEvent once when the component is built I guess
  • b
    well, once you call 
    registerEvent
    , that in turn calls 
    mapEvent
  • b
    Ok
  • b
    And the rule is: an event should be triggered on all elements in the hierarchy right?
  • b
    (Not just the deepest child)
  • b
    if it has a listener, yeah - i think the best way to handle it is to recursively walk up the tree and see if you should redispatch the event ( @ambitious-knife-25690 )
  • b
    Yes that’s how it should be done I think
  • b
    psuedo code:
  • b
    Copy code
    haxe
function checkRedispatch(x, y, event) {
    if (hasEventListner(event) && inBounds(x, y)) {
        dispatch(event);
    }
    parent.checkRedispatch(x, y, event);
}

function onMouse(event) {
    dispatch(event);
    parent.checkRedispatch(event.x, event.y, event);
}
  • o
    but is that bubbling up and down... that can be heavy in complex apps
1...899091...124Latest