https://linen.dev logo
Powered by
# haxe-ui
  • b
    ie, where Screen.instance.addComponent will add things
  • b
    you can do that by either doing:
  • b
    Copy code
    haxe
Toolkit.init({
   root: Main.rootScene
});
    or
    Copy code
    Screen.instance.root = Main.rootScene
    (im assuming Main.rootScene is the right one)
  • l
    Ah that's handy
  • l
    Copy code
    haxe
package;

import haxe.ui.Toolkit;
import haxe.ui.containers.menus.MenuBar;
import haxe.ui.containers.menus.Menu;
import haxe.ui.containers.menus.MenuItem;
import hxd.App;

/**
 * ...
 * @author Kaelan
 */
class Main extends App
{
    
    static function main() 
    {
        new Main();
    }
    
    public function new()
    {
        super();
    }
    
    override function init():Void 
    {
        super.init();
        
        Toolkit.init();
        
        var foobar:MenuBar = new MenuBar();
        s2d.addChild(foobar);
        foobar.width = engine.width;
        
        var fooItem:Menu = new Menu();
        fooItem.text = "Foo";
        foobar.addComponent(fooItem);
        
        var barItem:MenuItem = new MenuItem();
        barItem.text = "Bar";
        fooItem.addComponent(barItem);
    }
    
}
  • b
    does:
    Copy code
    haxe
Toolkit.init({
   root: Main.rootScene
});
    fix it?
  • b
    or 
    root: this.h2d
  • l
    Neither of those work
  • l
    The MenuBar component shows, and the Menu shows within that bar, but clicking on the menu does not display the MenuItems
  • b
    hmmm, right, so i can repro
  • b
    ... whats strange is i think it thinks there are no menu items... thats why the menu button looks different
  • l
    That's an interesting bug!
  • b
    hmmm yeah, i just dont get why though
  • l
    You know, I did once have a weird issue where the name of a variable caused me problems
  • l
    Crazy idea: Rename whatever... array, assuming it's an array, holds those components
  • l
    This was specifically a Hashlink thing
  • b
    it does work though, just not the way you have done it for some reason
  • b
    Copy code
    xml
    <menubar width="100%">
        <menu text="Test">
            <menu-item text="Item" />
        </menu>
    </menubar>
  • b
    im going to see what the macro spits out for that
  • l
    Make the macro generate XML code that feeds into another macro
  • b
    OK, so its an order issue... that defo shouldnt happen - you should be able to add components in any order and it shouldnt make a difference, but with menu thats not the case
  • b
    so for you, you have to add things in the "right" order until i fix it
  • b
    Copy code
    haxe
Toolkit.init({
    root: this.s2d
});

var foobar:MenuBar = new MenuBar();
foobar.width = engine.width;

var fooItem:Menu = new Menu();
fooItem.text = "Foo";

var barItem:MenuItem = new MenuItem();
barItem.text = "Bar";

fooItem.addComponent(barItem);
foobar.addComponent(fooItem);
s2d.addChild(foobar);
  • l
    ... hwat
  • b
    ?
  • l
    I'm just baffled at how that's a thing
  • l
    What broke to causes that, lol
  • b
    it makes sense... i mean, its wrong, but it makes sense... lots of UI frameworks require you to add things in specific order... haxeui isnt one of those, but i this case it it is unfortunately... i will fix it though as it doesnt happen in other places
  • b
    i havent looked at the code, but my guess is that menu has to be initialised before its ready to accept menu items, and that happens in menubar somehow
  • l
    So, until a fix happens, I need to build my UI from a bottom up approach?
1...782783784...1687Latest