https://linen.dev logo
Powered by
# haxe-ui
  • s
    SDL prob the problem then
  • s
    let me see if I can find an SDL test app
  • s
    yep launching that app makes my computer upset
  • s
    to the arch wiki!
  • b
    Yep, although I'm not able to get 
    absolute
    working, even the website snippet just has them all stacking at 0,0
  • b
    Tracing the position of each component gives the correct number though
  • b
    got a repro? absolute is defo one of the more basic layouts, i defo would have expected that to work
  • b
    Let me put a quick one together... I saw the last changes to it were 5 years ago, so I figured it was rock solid
  • b
    Might be the backend...
  • b
    Yeah the most basic case doesn't work:
  • b
    Copy code
    xml
<absolute id="box1" width="200" height="200" style="border: 1px solid #ababab">
    <box left="25" top="25" width="50%" height="50%" style="background-color: red;border:1px solid red;background-opacity: .5" />
    <box left="50" top="50" width="50%" height="50%" style="background-color: green;border:1px solid green;background-opacity: .5" />
    <box left="75" top="75" width="50%" height="50%" style="background-color: blue;border:1px solid blue;background-opacity: .5" />
 </absolute>
  • b
    From the website, along with
  • b
    Copy code
    haxe
package;

import haxe.ui.macros.ComponentMacros;
import haxe.ui.Toolkit;
import hxd.Res;
import hxd.App;

class Main extends App {
    
    static function main() {
        Res.initEmbed();
        new Main();
    }
    
    override function init() {
        
        Toolkit.init({ root : s2d, manualUpdate : false});
        var ui = ComponentMacros.buildComponent("assets/abs.xml");
        s2d.addChild(ui);
    }
}
  • b
    weird, ill check it out
  • b
    seems fine, so must be something with the way things are being initialized / added - if you do 
    Screen.instance.addComponent(ui)
    does that work?
  • b
    I’ll check in a bit, maybe it’s like the flixel backend where you have to force ready or something
  • b
    Although the other components and containers are fine
  • b
    @User - looks like you need:
    Copy code
    haxe
    private override function update(dt:Float) {
        BackendImpl.update();
    }
    in your app class, and you have to use 
    Screen.instance.addComponent(ui)
  • b
    or you can call 
    ui.ready()
    , i was sure you didnt need this tbh
  • b
    but only for 
    absolute
    ... thats so strange
  • b
    I turned manual update off in the init, but I didn’t actually look into how it works
  • b
    yeah, you are right... its all fine with other containers
  • b
    i dont get whats special about absolute
  • b
    I’ll just try 
    ready
    that’s fine for this case
  • b
    It’s too basic haha
  • b
    Maybe something isn’t supered
  • b
    .ready() doesnt work either... for absolute to work (for some bizarre reason) you have to use ready and manual update
  • b
    so strange
  • b
    looking at it now
  • b
    so thats interesting, absolute layout does absolutely (heh heh) nothing with left / top, which make sense
1...920921922...1687Latest