https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    OK, that probably shouldnt crash it... what happens if you do 
    Screen.instance.addComponent(v)
    ?
  • r
    That works!
  • b
    OK, cool - ill check it out though, i would have expected your code to crash though
  • r
    Would have or would not have?
  • b
    (was kinda hoping that it would also crash)
  • b
    sorry, wouldnt
  • b
    i have such an issue with "can/t" "would/nt"... constantly make typos there which changes the whole meaning
  • r
    for repro's sake, I'm using the latest git for heaps, haxeui-core, and haxeui-heaps
  • b
    cool - i havent changed anything in haxeui-heaps in a while, so my guess is its always been there - i just never do things that way... Screen.instance is defo the preferred way to go here since then haxeui knows about it, but ill see if there is an event i can listen to or something in heaps
  • r
    I will stick with the preferred way either way, then
  • b
    cool - probably safer that way, but ill check it out anyway, might be indicative of a deeper issue / bug
  • r
    Thanks very much as always!
  • b
    so the issue is as i thought it was: haxeui doesnt know about the child:
    Copy code
    haxe
        msg.onDialogClosed = function(_) {
            var button = new Button();
            button.text = "Added";
            //Screen.instance.addComponent(button); // <--- this is fine
            Screen.instance.rootComponents.push(button); // <--- without this it crashes
            Screen.instance.root.addChild(button);
        }
  • b
    but i dont think there is an easy way to know if the a child has been added to s2d, so i think for now you are safer with using 
    addComponent
  • r
    Works for me! I honestly just didn't know about the addComponent way 😄
  • r
    But I guess it makes a lot more sense if you ever want to change backends
  • b
    yeah, its what all the components (like dialog, dropdown, menus,etc) use internally since they wouldnt know about "s2d" or "stage" or "whatever"
  • c
    heaps: is it possible to pass an h2d.font into a component's style? I want to use an Sdf font but it seems font-name only resolves bitmap fonts
  • b
    It used to be the other way around lol
  • b
  • b
    Not sure how you'd unify them, as haxeui's 
    FontData
    is an alias for 
    BitmapFont
  • c
    was looking at the way FontCache imports them and it should work, but for some reason I'm getting messed up glyphs
  • b
    From experience, that looks like a bitmap font that got treated as an SDF font
  • c
    and it's the other way around
  • c
    just gonna use a regular old bitmap font, thanks for your help though
  • b
    I've never intentionally used SDF, so if you have any suggestions or ideas for how to implement we can try that
  • b
    Alongside bitmapfont
  • c
    well, not even bitmapfont is working - text is inverted and crashes the program when placed in components that have variable width/heights
  • c
    oh wait
  • c
    because it's anticipating SDF
1...137413751376...1687Latest