https://linen.dev logo
Powered by
# haxe-ui
  • b
    im not sure onChange bubbles up, you could always handle the onchange and "re dispatch" it
  • m
    But how do I access them in the class implementation?
  • m
    Suppose I define:
    Copy code
    xml
<zoom-selector max="1" min="8" />
    How do I access max and min in code?
  • b
    well, presumably "min" and "max" would be class level properties, no?
  • b
    ie, they would have to be on order for the xml above to work
  • m
    Yes, I'm retarded and did not make that connection automatically
  • m
    now that you mentioned, it seems so obvious
  • b
    heh heh 🙂
  • m
    hahahaha
  • m
    I tried re-dispatching it like this:
    Copy code
    haxe
@:bind(zoomLabel, UIEvent.CHANGE)
    function someFunc(e) {
        onChange(e);
    }
    But it didn't work
  • b
    Copy code
    haxe
@:bind(zoomLabel, UIEvent.CHANGE)
    function someFunc(e) {
        dipatch(e);
    }
  • m
    Oh! I'll try that
  • b
    i wonder if it would be a useful addition to be able to specific if you wanted an event to bubble up (per handler)... eg:
  • b
    registerEvent("somevent", function(e) { }, true)
    (last param being "bubbles")
  • b
    ill have a think about it
  • m
    Copy code
    haxe
@:bind(zoomLabel, UIEvent.CHANGE)
    function someFunc(e)
    {
        ...
    }
    This function is not being called when the text of the label changes
  • m
    🤔
  • b
    yeah, i dont think .text changes dispatch a change event 😄
  • b
    ok, label does dispatch a change event now
  • b
    fyi, you could have also listened for "UIEvent.PROPERTY_CHANGE"
  • b
    but seeing as for label .text = .value it make sense to dispatch a CHANGE when either change
  • b
    (latest git btw)
  • m
    great!
  • m
    I noticed that by just forwarding the change event, the event target ends up being the label, is it easy to instead of forwarding the event, creating a new one where the target is the custom component?
  • m
    Ok I think I guessed it correctly?
    Copy code
    haxe
dispatch(new UIEvent(UIEvent.CHANGE, false, this));
  • m
    Yeap, it works
  • b
    yeah, that'll do it
  • b
    if you just forward the event then, as you found out, you'll have the target of the original event
  • b
    btw, you can just do: 
    dispatch(new UIEvent(UIEvent.CHANGE, this));
  • b
    haxe will subst default params based on type
1...610611612...1687Latest