https://linen.dev logo
Powered by
# haxe-ui
  • b
    myComponent.onClick = onClickPassedIn
    would be the same as just 
    myComponent.onClick = ...
    outside
  • m
    Not sure I follow
  • m
    What I have now is a callback that does not change after the creation of ItemSlot, the outside handler for this callback is always the same, but it needs info that might change, which is item: Item.
  • m
    The callback should only be triggered when there is an Item set in the component
  • m
    So after the creation of ItemSlot, I just do setItem() from the outside. An if it's eventually clicked, it triggers the callback passing item, and itself (ItemSlot) as arguments
  • m
    What would you do differently?
  • b
    i mean, you have something like this now, correct?
  • b
    Copy code
    haxe
class MyComponent {
    new(cb:Void->Void) {
        something.onClick = function(_) { cb(); }
    }
}

var myC = new Component(function(_) { ... });
  • m
    Something like that, except for the fact the cb is ItemSlot -> Item -> Void
  • b
    sure, so maybe something like:
  • b
    Copy code
    haxe
class MyComponent {
    new() {
        something.onClick = function(e) { dispatch(e); }
    }
}

var myC = new MyComponent();
myC.onClick = function(_) { ... }
  • b
    or, if you wanted, use a custom event...
  • b
    Copy code
    haxe
class MyComponent {
    new() {
        something.onClick = function(e) { dispatch(new MyEvent(item)); }
    }
}
  • b
    (you'll a little more wiring, and will obviously need to create "MyEvent")
  • m
    Just not sure in the top example where do I get ItemSlot and Item from
  • m
    Assuming in the bottom example they go inside the creation of MyEvent?
  • b
    yeah, if you wanted to add custom data to an event you could create a custom event
  • b
    then 
    myC.registerEvent(MyEvent.FOO, function(e:MyEvent) { ... })
  • b
    and then ofc, you could use the haxeui macros to get a nice "onMyEvent" if you wanted
  • m
    I'll try to go the custom event way
  • m
    Sounds cleaner definitely
  • b
    so actually... you can use a normal UI event
  • b
    it has a "data" param which can be anything
  • m
    Dynamic?
  • b
    yup
  • m
    That seems simpler 😂
  • m
    I'll try that instead
  • m
    It's a "click" event after all
  • b
    custom events are better tbh, its cleaner and you'll know exactly whats going on
  • b
    something.onClick = function(e) { dispatch(new MyEvent(item)); }
    is better than 
    something.onClick = function(e) { dispatch(new UIEvent(UIEvent.click, false, item)); }
1...628629630...1687Latest