https://linen.dev logo
Powered by
# haxe-ui
  • b
    Copy code
    xml
<label text="Font Families:" />
<button text="Font Family: Default" style="font-size: 24px;font-name:default;" width="100%" />
<button text="Font Family: Decorative" style="font-size: 24px;font-name:decorative;" width="100%" />
<button text="Font Family: Roman" style="font-size: 24px;font-name:roman;" width="100%" />
<button text="Font Family: Script" style="font-size: 24px;font-name:Script;" width="100%" />
<button text="Font Family: Swiss" style="font-size: 24px;font-name:Swiss;" width="100%" />
<button text="Font Family: Modern" style="font-size: 24px;font-name:Modern;" width="100%" />
<button text="Font Family: Teletype" style="font-size: 24px;font-name:Teletype;" width="100%" />
<label text="Font Faces:" />
<button text="Font Face: Lucida Handwriting" style="font-size: 24px;font-name:'lucida handwriting';" width="100%" />
<button text="Font Face: Roboto" style="font-size: 24px;font-name:Roboto;" width="100%" />
<button text="Font Face: Onyx" style="font-size: 24px;font-name:Onyx;" width="100%" />
<button text="Font Face: Forte" style="font-size: 24px;font-name:Forte;" width="100%" />
  • b
    ^^ @User - latest git haxeui-hxwidgets & hxWidgets (if you want to see what fonts are on your system: 
    hx.widgets.FontEnumerator.faceNames
    )
  • p
    thanks! i will give it a try later
  • m
    @User updated all the git libs, so let me know when the heaps one is good. Thanks!
  • b
    for fonts you mean?
  • m
    yes, I pull all the latest ones from git so I can test it out. Looks like I need to figure out the change for rootScene
  • b
    so yeah, previously you needed to pass an hxd.App to haxeui... which was a shitty, esp as HaxeUIApp was supposed to be a helper class, which in haxeui-heaps it stopped being as you needed it... so now you can just pass a rootScene to toolkit.init (or not) and its where it will put things like dialogs etc
  • b
    if you try to put something on the "screen" without the rootScene you'll get a warning
  • b
    but you also dont need to set it if you arent using it, so you can just use whatever scene you want directly
  • m
    hmmm, in that case, I got a blank screen with the code that worked b4 the change - I'll need to debug it then
  • b
    what code, can you paste it?
  • m
    Copy code
    var mScr:Component = ComponentMacros.buildComponent("res/main-view.xml");  
        fui = new h2d.Flow(s2d);
        trace("After flow. mScr: " + mScr);
        Toolkit.theme = "myTheme";
        Toolkit.init();
        haxe.ui.core.Screen.instance.addComponent(mScr);
  • m
    ur main-view
  • b
    so yeah, there you are using Screen::addComponent... which needs a root scene
  • b
    this.s2d would probably be a good candidate
  • b
    Copy code
    haxe
Toolkit.init({rootScene: s2d});
  • m
    got fui defined as the root gui scene I think
  • b
    ok, then you can just add haxeui components to that then
  • b
    Screen isnt going to be able to magically know about your h2d.Flow
  • m
    s2d works just as good then
  • b
    one thing that is interesting... is i wonder if i should change rootScene to be rootObject?
  • b
    and the type being Object not Scene
  • b
    then you could have:
  • b
    Copy code
    haxe
Toolkit.init({rootObject: fui});
  • m
    that might be better since I believe that you can layer 2d objects in heaps - that way the haxeui stuff can be on the top layer (like 100). I'll need to look into that when I put all the old code back in
  • b
    yeah, i feel like using object makes more sense... to be honest, i didnt realise object had all the child management features... thought it was higher up the chain
  • b
    and should still work with scene objects anyway
  • m
    that's right. I'm not familiar enough yet to know if you can layer scenes. I hadn't got toe that point yet as I was playing with the 3d stuff which only had one 2d layer
  • b
    yeah, well, even without this stuff you could happily layer things... components in haxeui-heaps are just Objects so you could layer them as you would any other heaps objects... (just not using Screen.instance.addComponent and addChild directly)
  • b
    but using Object rather than Scene for an optional root feels more flexible regardless
1...546547548...1687Latest