https://linen.dev logo
Powered by
# haxe-ui
  • b
    kha also a fair amount
  • a
    cool, I was meaning to take a look at those (probably not kha)
  • a
    is the html5 one using the dom?
  • b
    html5 is my go to for composites, or if i wanna quickly test things, kha is my goto if i wanna test drawing stuff... openfl too ofc, and increasingly flixel... and hxwidgets, well, its native, so i like it
  • b
    yeah, exactly... even though haxeui-html5 is a composite backend it doesnt actually "draw" anything, it builds up dom nodes
  • b
    so its not a great test for draw related issues / tests
  • a
    cool in other ways though
  • a
    native html uses
  • b
    yeah, exactly... its actually a hybrid backend in reality
  • b
    as it can also create native components
  • b
    native to the browser
  • b
  • b
    you can also set native via styles, so you can just do groups of types of components... or you can set the theme to "native", which basically just does 
    * { native: true; }
  • b
    tbh, its pretty cool... but i actually very rarely use it... i prefer the L&F of the composite versions
  • a
    very cool 😎
  • b
    its one of those things, i added it haxeui-html because it was cool, and could be useful (and moreover was possible) but in reality, i just dont use it
  • b
    i doubt most other people do either, or even know about it
  • b
    (though i do mention it in the guides now)
  • b
    Actually I’m not sure how it works without dirty lol
  • b
    i guess if you use .pixels.fillRect it sets dirty?
  • a
    filth
  • b
    😄
  • b
    No lol that does not
  • b
    You must be doing some operation that sets dirty every frame or something
  • b
    what kinda operations would do that?
  • b
    doesnt look like the older version of FlxStyleHelper explicitly set dirty = true
  • h
    any clue what this might be? I'm still not getting the top menu bar coloured (even after fixing the layers and updating 
    haxeui
    , 
    haxeui-flixel
    and 
    haxeui-core
    ) and only the menu buttons actually display, so I don't know if it could be related since the error is on the first vbox containing the menubar
  • b
    I thought I had it in the component class, I don’t remember
  • b
    I’ll go through it this weekend, I’m curious at the very least
  • b
    @User - that sounds great, a more experienced eye over the flixel backend would be pretty great after the updates i made, just to sanity check me 🙂
1...392393394...1687Latest