https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • h
    also this doesn't set the checkbox and I'm not entirely sure why
  • h
    fixed this, still working on the checkbox listener
  • b
    im not sure im following, can you setup a test project either send here, or on the builder - its usually easier to see code rather than try and grep whats meant
  • h
  • h
    I added some comments to mainview for clarity
  • b
    ill have to double check, but i think you might need to listen for a "ItemEvent.COMPONENT_EVENT" on the treeview (as you would with tables and lists)
  • h
    I'll try that
  • b
    doesnt seem to work
  • h
    yeah I'm not sure how this should work
  • b
    well, usually, you would do something like:
  • b
    Copy code
    haxe
        unitSelector.registerEvent(ItemEvent.COMPONENT_EVENT, (event:ItemEvent) -> {
            trace(event.source.text);
        });
  • h
    the thing that's messing with me is that the data of the node doesn't change when the checkbox does
  • h
    first is when I remove a check, second is adding one
  • b
    ill check it out, but i would have expected it to... i mean, its all just item renderers
  • h
    the code that adds the listener that logs that is
    Copy code
    hx
var node = coolTree.addNode({text:unitNames[EnumValueTools.getIndex(unit)], checked:(unit==A1)});
node.onClick = (_:UIEvent) -> {
  if (node.data.checked) {
    gp.units.push(unit);
  }
  else {
    gp.units.remove(unit);
  }
  trace(node.data);
}
  • h
    ok it gets weirder actually
  • h
    if I click the label exactly 3 times it reverts to whatever it was at declaration
  • b
    OK, well, i can see why the item event isnt being dispatched, which also explains why the value in .data isnt being updated
  • b
    ... ... bear with me
  • h
    http://haxeui.org/builder/?541416cb that behavior doesn't happen on the builder also, which is weird
  • h
    the data not changing does but the triple click is bizarre
  • b
    one thing at a time... 🙂
  • h
    sorry yeah, I'm also trying to debug in case it's somehow my code
  • b
  • b
    ok, this works now... one issue is you get two events... one for change and one for click... thinking of a good way around it... :/
  • h
    I think I can work around that
  • h
    tysm
  • b
    its shitty though... i dont like it, but technically it is perfectly valid
  • h
    it's def good enough for now
  • h
    does everything I need it to
1...138813891390...1687Latest