https://linen.dev logo
Powered by
# haxe-ui
  • s
    so i have to 
    haxelib git https://github.com/haxeui/haxeui-flixel
  • s
    wait
  • s
    haxelib git haxeui-flixel https://github.com/haxeui/haxeui-flixel
  • b
    almost: 
    haxelib git haxeui-flixel https://github.com/haxeui/haxeui-flixel
    you'll also need to do the same with haxeui core: 
    haxelib git haxeui-core https://github.com/haxeui/haxeui-core
  • m
    @User I've managed to reproduce both problems in the same small project. All I had to do was add a tabview to the mix.
  • m
    The button in the bottom toggles the upper button's container visibility. If you toggle it off, it will still receive onClick events.
  • m
    And if you navigate to the second tab and back to the first, the button will appear, although its cointainer's visibility is supposed to be off
  • m
    I've also managed to reproduce the other issue of the image not appearing.
  • m
    If you click the "Icon Button" it sets the image component's resource to a texture from assets, but the texture does not appear. If you change to the second tab and back to the first tab, the image appears.
  • m
    I'm glad I was able to reproduce all the issues I had pending in such a short while. Hope these small projects help
  • m
    And also hope flixel doesn't get too much in the way of fixing them
  • b
    nice one, thanks guifes!
  • b
    ok, the first one (the visibility issue) should be fixed now, it was nothing to do wit tab view or anything like that. The "issue" was that you were using 
    .visible
    which is a flixel property, haxeui uses 
    .hidden
    or 
    .style.display = "none"
    (added recently) or 
    .show()
    or 
    .hide()
    ... that said, 
    .visible
    is totally valid so ive overridden it as i have in other backends (openfl / nme)
  • m
    I keep hitting that flixel over haxeui stuff. Damn!
  • m
    The visibility thing worked, just tested it, but this 👆 is still happening though!
  • b
    thats a seperate issue
  • b
    what does that mean?
  • m
    I mean, when I think I'm dealing with haxeui but I'm actually wrongly doing stuff in the flixel level. Like that time I was trying to set the transparency of a background by setting it's color's alpha, instead of using haxeui's background-opacity
  • b
    so you mean and then the haxeui style is overwriting it?
  • m
    No no. I meant just that, sometimes I forget about the duality of flixel + haxeui, and I end up doing things the flixel way without realizing
  • m
    And this leads to these issues, like setting the flixel visibility instead of haxeui's
  • m
    Or trying to control alpha through flixel's color instead of background-opacity
  • m
    I mean, yeah, haxeui style was overwriting the opacity yes, but not that that's an issue though
  • b
    sure, it might be a nice addition though to override certain parts in flixel sprite (like backgroundColor or whatever its called) and have that set the style, so it wouldnt be overwritten
  • b
    ... ... just a thought
  • m
    I think so as well
  • b
    @User - wanna pull latest haxeui-flixel and give that a run through...see if thats any better?
  • m
    On it
  • m
    Worked fine in the example
  • b
    but?
1...625626627...1687Latest