https://linen.dev logo
Powered by
# haxe-ui
  • b
    or you can just do:
    Copy code
    css
.heaps .label { ... }
.html5 .label { ... }
... ...
  • b
    but yeah, if the backend doesnt support it, haxeui cant
  • b
    really ?
  • b
    really what? That you can use the backend id in styles?
  • b
    yes
  • b
    yeah
  • b
    can i do
    Copy code
    css
.heaps * {}
.html5 * {}
    also ?
  • b
    every component has 
    addClass(Backend.id, false);
    in the constructor
  • b
    yeah, should work
  • b
    @refined-laptop-39041 so for heaps i need to use the fnt+png file than ? xml or txt flavor ?
  • b
    Copy code
    // Supported formats:
        // Littera formats: XML and Text
        // http://kvazars.com/littera/
        // BMFont: Binary(v3)/Text/XML
        // http://www.angelcode.com/products/bmfont/
        // FontBuilder: Divo/BMF
        // https://github.com/andryblack/fontbuilder/downloads
        // Hiero from LibGDX is BMF Text format and supported as well.
        // https://github.com/libgdx/libgdx
  • b
    seems these are the supported ones
  • r
    I think both works
  • b
    i have some lying around but they are all from libgdx in txt flavor
  • b
    oh
  • r
    there is a guide
  • r
  • b
    they mention libgdx
  • r
    make sure your settings are right
  • b
    i generate the png+fnt with my own code, so this has max flexibility
  • b
    lol
  • r
    Ohhhh that works a lot better! 😄 But if you can't guarantee the tabs will be removed in the order they were added in, is there a better way to do it than making a function like
    Copy code
    haxe
    function findTabID(component:Component):Int{
        for(i in 0...this.mytabview.pageCount){
            if(mytabview.getPage(i)==component){
                return i;
                break;
            }
        }
        return -1;
    }
    ?
  • r
    (since you can only remove tabs by ID, and there doesn't seem to be a method to keep track of the tab ID of an component, as near as I can tell...)
  • r
    Because I found "addComponent" to add a page, I didn't consider that there might be a removePage 😄
  • b
    what did you use?
  • b
    removeComponet should also work
  • b
    hmmm, ok, removeComponent / removeComponetAt behave strangely, but they should have worked, so its a bug
  • b
    right, removeComponent fixed
  • b
    removeComponentAt fixed also, both were silly bugs / oversights - i guess the code changed at some point and remove/removeAt werent tested
  • b
    finally, ive also added "getPageById", so you can also do things like: 
    tv.removeComponent(tv.getPageById("box2"));
    if you want (
    tv.removeComponent(tv.findComponent("box2"));
    also works, and always did, but getPageById is semantically clearer i think 🙂 )
1...105510561057...1687Latest