https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • i
    I think the reason I put them in was to try to make it responsive to resizing, like adding space between the labels and and select boxes if there were room
  • b
    i think autosized and % sizes are (kinda) mutally exclusive, you might be able to do something funky with 
    initial-width
    / 
    initial-height
    in css, but might not work at all, not sure
  • b
    this is fun:
  • b
    set the font size on the label, and the menu font changes... wtf 😄
  • h
    How would i do this
  • f
    when you drop the component A on a container B, you make the container B the parent component of A,. But, what do you want to do, you want to drop a label on a a vbox for example ?
  • b
    well, the component would need to be farther "down" the tree in order to be "above" previous children
  • b
  • h
    If i did something like add the boxes on page load it would default to the top, right?
  • b
    think were about there, just need to do some clean up, etc
  • b
    nope, i dont think so, by default addComponent will add things to the end of the component tree (well, end of the parents child list)
  • h
    So the easiest way to do this would be something like making the draggable box at the end and setting its x and y programmatically?
  • h
    or just not making it draggable
  • b
    well, the way i would do it (assuming im understanding), is put all your "behind" UI in a box, then put your draggable stuff in that box, so it will then be "above" the "behind" UI... but if you are talking about dragging arbitrary UI components from anywhere in the tree to anywhere else in the tree, then you'll have to do more work (like removing it from its current location and adding it to some top level component / screen)
  • c
    wow, very nice! how did you end up handling the sdf properties?
  • b
    yeah, so i was just about to write that... so, you'll need to do something like this:
    Copy code
    haxe
haxe.ui.backend.heaps.SDFFonts.register("sbf/segoeui.fnt", 4, .5, .45);
  • c
    ah ok
  • b
    even if you dont want to screw with the params, you'll have to still "register" the font as SDF:
    Copy code
    haxe
haxe.ui.backend.heaps.SDFFonts.register("sbf/segoeui.fnt");
    since haxeui will need to know this is an SDF font... i might be able to autodetect it, but im not sure, and this feels like a safer way
  • c
    that's probably for the best, since both types of fonts are .fnt, Bitmapfont, etc.
  • c
    it's up to the user to distinguish it
  • b
    yeah, i think i could open the .fnt file as text as search for things, like 
    <distanceField fieldType="msdf" distanceRange="4"/>
    maybe, but im unsure and it feels brittle
  • b
    anyways, thats all in now, latest haxeui-heaps and latest haxeui-core (needed a tiny change to allow the font name to passed around)
  • b
    lemme know if it works 🙂
  • c
    eh that's probably overkill
  • c
    looks like I'm still getting weird results
  • c
    bitmap:
  • c
    sdf:
  • c
    sdf looks like it's partially working, like it was just cut up wrong
  • b
    can you try and repro in a minimal repro? I gotta pop out, but i can take a look when i get back (are you sure you got the changes, haxelib lies sometimes)
  • c
    sure, one sec
1...137913801381...1687Latest