https://linen.dev logo
Powered by
# haxe-ui
  • q
    a router is about right, isn't it? with the response in one hand and the UI state tree in the other
  • q
    and, like you say, bubble up events to a front controller
  • b
    there isnt anything inbuilt into haxeui to handle any of those types of interactions automagically though unfortunately, can create a model / view easy enough, but you'll still have to wire bits up manually, which arguably defeats the purpose
  • q
    the event handling is more than sufficient
  • q
    take request response, apply to view is as much as I can fit in the brain right now
  • b
    well, if you get something working, id love to see it... i defo want to make something to help with this type of stuff as i tend to be reinventing it each time for each project... i just dont know a) if it should be in haxeui-core and b) how to make it useful others (if thats even possible)
  • q
    A simple simple thing to do would be for an event to accrue the path to it's source as it bubbles up: which would give both a pretty good guide for what URL to shoot for, and the scope of the returned data
  • b
    that could be interesting... and as you say, pretty simple
  • q
    I'm early days here looking for how to select which component is visible in a Stack
  • b
    what version of haxeui are you using?
  • q
    git
  • b
    from where?
  • q
    (not being rude). directly
  • b
    ah, sorry, thought there was no Stack.hx in haxeui-core... was wrong 😄
  • b
    but just to confirm, you arent using this version of haxeui: https://github.com/ianharrigan/haxeui
  • q
    I'm hoping that at the end of the bug hunt I'm on there will be completion
  • q
    but I've done a little digging and 'selected' or something is not found
  • b
    so assuming you are using this https://github.com/haxeui/haxeui-core there isnt anything clever about a Stack, its just a Box, and the items are just shown ontop of each other
  • b
    so the top item with will be the visible item
  • b
    can you confirm the URL you are using for git?
  • q
    yes, don't worry
  • q
    so setComponentIndex(0, component)
  • b
    yeah, that would set it to the bottom... so you'll want 
    setComponentIndex(childComponents.length - 1, component)
  • q
    ok😀
  • b
    to be honest... i think im going to add four utility functions: bringToTop, sendToBack, firstComponent, lastComponent
  • b
    ive been needing the first two often
  • q
    👍 aha
  • q
    I didn't realise that thumbs up was that callosal
  • b
    heh heh
  • o
    @User I have bringToTop and SendToBack but also recently added Swap feature, still not sure if that is enough for depth in my lib
1...508509510...1687Latest