https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    Might be related to a dumb flash rule with loading things
  • b
    there defo does seem to be some "weirdness" with haxeui-flixel
  • b
    not sure if it might just be me though... checking some stuff
  • b
    im not event getting mouse events
  • b
    Copy code
    haxe
class PlayState extends FlxState {
    public var uiGroup:FlxGroup = new FlxGroup();
    
    override public function create():Void {
        FlxG.mouse.useSystemCursor = true;
        
        super.create();
        
        this.bgColor = 0xFFFFFFFF;
        Toolkit.init({ container : uiGroup });
        this.add(this.uiGroup);
        
        var button = new Button();
        button.text = "Open Substate";
        uiGroup.add(button);
    }

    override public function update(elapsed:Float):Void {
        super.update(elapsed);
    }
}
  • b
    @brave-kangaroo-30399 - any idea what im doing completly wrong here??
  • b
    ok, so there is defo something up with the haxeui-flixel... if you dont load with the buildComponent macro then you dont get events
  • b
    and all that does it build "addComponent" type code... but probably in some type of order that haxeui-flixel is ok with
  • b
    actually, that might not be right
  • b
    Copy code
    haxe
        var button = new Button();
        button.text = "Open Substate";
        
        var box = new Box(); // <------- have to add button into a box to get mouse events??
        box.addComponent(button);
        
        add(box);
  • b
    (doesnt have to be a box, any component will work, but doesnt seem right)
  • b
    Oh yeah I’m not sure how to get around that
  • b
    Has to be added to the “stage” which is the main container
  • b
    I can look into it tonight
  • b
    fair enough... not a huge deal, but certainly a gotcha when you just want a button
  • b
    im just trying to get it to integrate with a flixel collision demo... i mean, ideally it should work
  • b
    I honestly didn’t think of that use case haha
  • b
    so the first issue is it seems haxeui needs to know when flixel has updated coords
  • b
    (i think thats the issue anyway)
  • b
    Copy code
    haxe
        var button = createButton("Bob");
        button.x = 100; // this doesnt work
        button.y = 100; // this doesnt work
//        button.left = 100; // this works
//        button.top = 100; // this works
        add(button);
  • b
    Copy code
    haxe
    public override function set_x(value:Float):Float {
        var v = super.set_x(value);
        this.left = value;
        return v;
    }
    
    public override function set_y(value:Float):Float {
        var v = super.set_y(value);
        this.top = value;
        return v;
    }
  • b
    ... that worked... ... better but screws a load of other things up
  • b
    I don't think you want to make accessors public
  • b
    ok, well, im just playing about, its not the cause of the further issues after that
  • b
    sure, just pointing that out since it's a fairly common mistake / misconception
  • b
    sure... just brain on auto... i do do that sometimes and usually realise when "set_x" shows up in auto completion
  • b
    making the accessors public doesn't have any effect on the property, and you basically never want to call the accesors directly / appear publicly in code completion
  • b
    right 😃
  • b
    am i right in thinking, in flixel, there isnt any child co-ords?
  • b
    i mean, everything is relative to screen co-ords?
1...343536...1687Latest