yeah it seemed a bit wacky, I had to rename

<tabbar>

to

<tabview>

to get it to even stop the unidentified errors

huh... weird, yeah, i actually started rewriting all the component examples tbh

I can get the tabview example from the haxeui website component explorer to build, but that seems to throw errors about focus if you click anywhere that isn't a button or tab - probably a different issue

feels like I need to make proper issues for all these to help you keep track lol

hmmm, yeah, that would be super useful... esp. as none of these ive heard of before

small repros would be useful for sure

just put one up on the haxeui-core tracker

writing issues takes a while 😫

nice one - appreciated 👍

I was trying to use the raylib backend but it gives me this error:

/home/.../Haxelib/haxeui-raylib/git/haxe/ui/backend/ScreenImpl.hx:41: characters 30-45 : Field removeComponent overrides parent class with different or incomplete type
/home/.../Haxelib/haxeui-core/1,3,0/haxe/ui/backend/ScreenBase.hx:73: characters 21-36 : ... Base field is defined here
/home/.../Haxelib/haxeui-raylib/git/haxe/ui/backend/ScreenImpl.hx:41: characters 30-45 : ... Different number of function arguments
/home/.../Haxelib/haxeui-core/1,3,0/haxe/ui/core/Screen.hx:55: characters 30-45 : Field removeComponent overrides parent class with different or incomplete type
/home/.../Haxelib/haxeui-raylib/git/haxe/ui/backend/ScreenImpl.hx:41: characters 30-45 : ... Base field is defined here
/home/.../Haxelib/haxeui-core/1,3,0/haxe/ui/core/Screen.hx:55: characters 30-45 : ... Different number of function arguments

Use

haxeui-core

from git.

☝️

Ok, installed from git and seems to be compiling, thanks 👍

ill try and get a release out soon for all of them, just want to finalise a few things first

No problem, take your time 👍

I'm trying to debug the haxeui app but it crashes after printing these messages:

haxe/ui/core/Screen.hx:121: WARNING: Screen event "keydown" not supported
haxe/ui/core/Screen.hx:121: WARNING: Screen event "keyup" not supported
haxe/ui/core/Screen.hx:121: WARNING: Screen event "keydown" not supported

I'm using the raylib backend from git @User

Okay I think I got a weird one for you, trying to make a minimal here

On heaps, having a menubar added to the stage affects the hitbox of buttons within a grid

but as it stands, not adding a menubar to the stage causes the buttons hitboxes to be in their correct position

yup, got it now: Repositioning a ``Box`` container that holds a ``Grid``, it displaces the hitboxes of buttons inside of the grid:

haxe
package;

import haxe.ui.components.Button;
import haxe.ui.containers.Box;
import haxe.ui.containers.Grid;
import haxe.ui.containers.menus.MenuBar;
import haxe.ui.core.Screen;
import hxd.App;
import haxe.ui.Toolkit;
import hxd.Res;

class Main extends App
{
    
    static function main() 
    {
        new Main();
    }
    
    public function new()
    {
        super();
    }
    
    var box:Box;
    
    override function init():Void 
    {
        super.init();
        
        Toolkit.init({
            root : s2d
        });
        
        Res.initEmbed();
        
        box = new Box();
        box.backgroundColor = 0xCCCCCC;
        box.width = 400;
        box.height = 800;
        Screen.instance.addComponent(box);
        
        var gridview:Grid = new Grid();
        gridview.columns = 3;
        box.addComponent(gridview);
        gridview.y = 45;
        
        for (a in 0...100)
        {
            var btn:Button = new Button();
            gridview.addComponent(btn);
            btn.icon = "AASTINKY.png";
        }
        
        onResize();
        
        box.y = 45;
    }
    
    override function onResize():Void 
    {
        super.onResize();
        
        box.y = 45;
    }
}

Resize the hashlink window to trigger the bug

those warnings are nothing to do with the crash, they are just, warnings

can you zip your app and i can try this end?

Nice one, ill check it out later today 👍

OK, so the issue here (i think) is that you are using .y, which isnt really the "haxeui" way of doing things, in fact, even using ".top" (which is the haxeui way of doing things) wouldnt work since your container is a box, and that doesnt allow you to use absolute coords.... thats said, the behaviour is a little weird though

Should I not be using .x/.y for the location of any top level components?

for the very top level you can but .left/.top are the "haxeui" props

in fact, id thought i'd overridden x / y to call .top/.left but it seems i removed that, probably caused a problem

... its weird though, as i can find a commit that either added, or removed overriding "set_x" or something