https://linen.dev logo
Powered by
# haxe-ui
  • b
    no worries, i think i would do it that way... or maybe have an array of "allowed values" (.5, .25 etc) and turn them into a label
  • b
    (your way is probably simpler though)
  • u
    does haxeui do actual nativeui elements or just "native performance" but apps look the same on every platform?
  • b
    if you are using a backend like haxeui-hxwidgets then the components are native, ie, native to the OS (not just look but actual native windows via wxWidgets)
  • m
    @User I managed to isolate another glitch. https://github.com/haxeui/haxeui-flixel/issues/22
  • m
    Another thing I noticed that might be an issue, I'm not quite sure.
  • m
    I've added a bitmap to an image component. This bitmap seems to never leave the bitmap cache. Even if I switchStates to an empty state.
  • b
    hmmm, i wonder about the cache... maybe i can empty the cache on each state change? Not sure if that the best idea though
  • b
    I believe that already happens, so it’s possible the bitmap is unable to leave the cache
  • b
    Like it’s in use and is marked 
    persist
  • b
    Rather, just persist, it doesn’t have to be in use to stick around in that case
  • m
    From what I've been able to debug, it's not leaving the cache because useCount > 0
  • b
    so that issue above i think is something to do with flixel
  • b
    i dont think it handles visibility well in groups, well groups of groups
  • b
    (seeing if i can work around it now)
  • b
    @User - wanna pull latest core and backend and try again? #22 should be fixed now
  • b
    flixel just blanket sets .visible to true / false recursively, regardless if you've actually set it down the tree
  • b
    ie, it doesnt honour previous .visible calls and essentially resets them... i guess its not really supposed to be that hierarchical in nature, fix is pretty simple, i just "restore" haxeui's internal "hidden" state:
  • b
    Copy code
    haxe
private override function handleVisibility(show:Bool):Void {
    this.visible = show;
    for (c in childComponents) {
        c.handleVisibility(!c.hidden);
    }
}
  • b
    (the loop is the new bit)
  • m
    Testing right now
  • b
    👍
  • m
    I hope this solve another issue I'm having with visibility as well
  • b
    yeah? Sounds like it might do... i dont know the issue, but certainly under various circumstances this issue would rear its head
  • m
    It probably has to do with tabviews inside tabviews and visibility
  • m
    I was setting the image for a component it was not being shown, but when I switched tabs of the outer tabview back and forth, the image appeared.
  • m
    Must be some wrong visible=false that should've been restored
  • m
    This one I was having a hard time isolating...
  • b
    so does it solve both issues?
  • b
    basically, if you had, say an hbox with two buttons in it, you hid one of the buttons, then you hid the hbox, then you showed the hbox then (in haxeui-flixel only) both buttons would be visible again
1...613614615...1687Latest