https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    basically the area that is visible after clipping is the area where the clipQuad would be drawn if it was not set visible=false
  • a
    this.x = -value.left; this.y = -value.top; this.clipQuad.x = left; this.clipQuad.y = top;
  • a
    i move both
  • a
    this is weird
  • a
    it always catches the hover effect, it never has issues with the click ability of the button
  • a
    but mouseover is intermittently called
  • r
    I'm missing a concept here: In the custom tree view example, how are you meant to hook up an event handler to, for example, the switch in the item renderer? (one that knows what node it is in etc)
  • b
    switch in the item renderer?
  • b
    ah, i think i understand what you mean: http://haxeui.org/builder/?252c13e0
  • b
    short answer is:
    Copy code
    haxe
        tv2.registerEvent(ItemEvent.COMPONENT_EVENT, function(event:ItemEvent) {
            trace(event.source.id, event.source.value, event.sourceEvent.type);
        });
  • b
    interestingly though, that didnt work for the switch, which i dont quite get... will check it out... but it should have worked with any InteractiveComponent...
  • b
    ... ... i love it when a plan comes together
  • b
    basically zero effort validation 🥳
  • r
    Aah... it seems things in expandable aren't working in general? if I put a button in there it also does nothing
  • b
    oh yeah? That seems weird, i mean, its all just item renderers in the end... ill check it out when i get a moment
  • b
    you are right though... put a checkbox in the expandable item renderer and it doesnt dispatch the event - and that 100% works in the non-expandable item renderers... strange... 🤔 Likely to be something dumb (repro: http://haxeui.org/builder/?fb2072fd)
  • r
    http://haxeui.org/builder/?bce037e3 yep I was about to send you this similar repro :D
  • b
    almost certainly something really small / dumb - there isnt anything special going on here... or at least there shouldnt be
  • b
    alright, this is working now... as expected it was tiny: when the new item renderer was created, it didnt copy over the "itemIndex" from the old one, which is needed in order to dispatch component events 🙂
  • r
    Amazing!
  • r
    Very much appreciate the fast fix :)
  • b
  • b
    i thought it would be something dumb / simple - nice catch 🙂
  • r
    oh wow the TreeNode's 
    data
    is available from every component in the item renderer's event
  • r
    that is super handy and should probably be emblazoned somewhere
  • b
    yeah, it passes the item renderer data when sending the event
  • b
    (wip - super simple atm, like 70 LoC)
  • a
    @bright-gpu-74537 Bug with button bar
  • a
    selectedindex/selectedbutton never gets set
  • r
    In the validation examples, what is it that ties the validators to a form? Eg, how do you tell the submit button which validated fields are relevant to it?
1...145814591460...1687Latest