https://linen.dev logo
Join Discord
Powered by
# ceramic
  • a
    just to confirm
  • a
    i can't double/multi bind to an event(mouse/input) in any way, can i?
  • a
    @billowy-waiter-28954 as an example, I want to have 2 seperate or more events on a 
    screen.onPointerMove
  • a
    a bit hard to follow code due to macro stuff
  • a
    i'll do some messing around with owner
  • a
    hmmm, seems to work with owner
  • a
    neat
  • b
    @ambitious-knife-25690 I'm not sure I understand what you mean?
  • a
    I wanted to know if I could have multiple events assigned to a 
    visual.onPointerUp
  • a
    as an example
  • b
    you mean multiple event handlers?
  • a
    yea
  • b
    Yeah you can, it's intended to be used this way
  • b
    you can add as many handlers as you want to an event
  • b
    Copy code
    haxe
visual.onPointerUp(owner1, info -> { ... });
visual.onPointerUp(owner2, info -> { ... });
visual.onPointerUp(owner2, info -> { ... });
...
  • a
    ahhh
  • a
    the way i was thinking about it was more like:
  • b
    You can also add multiple handlers with the same owner, nothing restrictive about that either
  • a
    visual.onPointerUp = event
  • b
    it's just that if the owner gets destroyed, all handlers related to this owner will be unbound
  • a
    Ohh! that's really cool to know
  • b
    pointerUp
    is the event
  • b
    Might be worth reading that a second time: https://ceramic-engine.com/guides/events/
  • a
    ahh, i completely forgot that the owner is purely for this. I had been making custom entities
  • a
    But it may be worth mentioning in there as well that doing 
    visual.onPointerUp()
    doesn't mean you can't do something like
    Copy code
    hx
class Foo extends Visual {
  function new() {
    visual.onPointerUp(this, a);
    visual.onPointerUp(this, b);
  }
  function a(info) {
    //logic
  }
  function b(info) {
    //logic
  }
}
  • a
    maybe it is obvious, but to me i had assumed that the second call overwrote the first event
  • a
    😅
  • b
    That's right I don't mention this detail because it's so obvious for me xD but I guess I should
  • b
    @ambitious-knife-25690 And if you want to unbind one handler specifically, following your example code:
    Copy code
    haxe
visual.offPointerUp(a);
    In that case 
    a
    becomes unbound but 
    b
    is still bound and will be called when the event is fired
  • b
    visual.offPointerUp();
    (without arguments) unbinds every handler (no specific handler provided)
1...969798...124Latest