https://linen.dev logo
Powered by
# haxe-ui
  • r
    @most-caravan-45834 I find it's more enlightening to read the source for the component explorer along with it: https://github.com/haxeui/component-explorer/blob/master/src/views/DragManagerView.hx
  • m
    Thank you!
  • b
    Yeah, the tree must be populated in code currently
  • b
    also, the .hx file should have been included in the builder, not just the .xml file, but i see i forgot to add it as a "relevant file", so i will do later
  • r
    Can't quite figure it out... when you're using a DataSource with a TreeView, how do you make nested items?
  • r
    actually what's going on here in DataSource.hx?
  • r
    This means that this in TreeView will never do anything, no?
  • r
    Hmmm... am I right in guessing that DataSource by itself is not actually functional, and you're supposed to extend it and implement your own?
  • r
    I'd love an example of how to use it, if there is one.
  • r
    I give up, how do I make a tree view node's text label reflect changes to its underlying data?
  • r
    none of these things produce any effect
  • b
    > Yeah, the tree must be populated in code currently
  • b
    @refined-greece-48002
  • b
    data sources dont work with treeviews currently
  • r
    Ah gotcha, I was hoping to switch to that but I can do without
  • b
    the will though, just not working yet.
  • r
    What about updating the label/text of a node that's already been added?
  • b
    hmmm good question, not sure...
  • b
    lemme have a play
  • b
    so i think you could do:
    Copy code
    haxe
myNode.data = { text: "changed" }
  • b
    thought it might be nicer here to just be able to do "myNode.text", "myNode.icon"...
  • r
    this is so bizarre... 
    node.data.text = "changed";
    ^ this works 
    node.data.text = myString;
    ^this doesn't even tracing out myString shows that it's different to the value of node.data.text, but it doesn't update...
  • b
    i think the problem is that when you use 
    node.data.text
    it doesnt actually invalidate the node, it probably works "by accident" in your "changed" case
  • r
    it seems almost like only the first update is working
  • r
    ah, that makes sense - it's probably happening before the first draw in the case that I put a literal there
  • b
    myNode.data = { text: "changed" }
    would work every time since you are resetting the "data" which does revalidate the node
  • r
    right, but none of the invalidate-flavored methods seem to invalidate the node either?
  • b
    but i think ill add .text and .icon overrides also, as its a bit of a gotcha, ive also noticed that invalidating the component manually wouldnt work (i dont think)... the treeview is experimental, so there are bound to be these type of teething problem
  • r
    ahh, makes sense
  • b
    yeah, exactly, this i think is also a bug... well, oversight really... will give it a bit of a once over shortly... ive never had to change the node labels dynamically yet (personally) but it defo needs to work that way - especially when i come to link data sources up
1...105810591060...1687Latest