https://linen.dev logo
Powered by
# haxe-ui
  • b
    cool
  • d
    in the code above, the 
    spriteContainer
    shows in the right place, and has the right size, but the image is not inside the 
    spriteContainer
  • b
    yup
  • b
    the box should be where the outline (i added) was
  • b
    i guess because in flixel there is no parent / child stuff in that way
  • d
    would a custom component help in this case?
  • b
    for sure
  • b
    ill show you the custom component route, just for completness, but ill also have a look at seeing if haxeui-flixel can actually make the box appear at 0,0 relative to its component
  • b
    (which is a nicer fix)
  • d
    ok thank you, agreed, that would be a nicer fix, but custom components are not a bad option either. Just have to make one for every non-component needed
  • b
    yeah, exactly, which is why the custom component route might also come in useful
  • b
    but once ive knocked up a silly example, i think you'll probably be able to see how haxeui-flixel can probably do the same internally
  • b
    blue is right
  • b
    Copy code
    haxe
class SpriteContainer extends Component {
    private var sprite:FlxSprite;
    
    public function new() {
        super();
        sprite = new FlxSprite();
        sprite.makeGraphic(50, 50, FlxColor.BLUE);
        add(sprite);
    }
    
    private override function repositionChildren() {
        super.repositionChildren();
        sprite.x = this.screenLeft;
        sprite.y = this.screenTop;
    }
}
  • b
    so my thought is that haxeui-flixel can probably do the same to any of the members of the group
  • d
    ahhh, I see, yes, something like
    Copy code
    haxe
for (c in this){
  c.x = this.screenLeft;
  c.y = this.screenTop;
}
  • d
    but thank you - easy enough as is with custom components
  • b
    ok, both methods should be fine now
  • b
    i think i like the idea of haxeui-flixel allowing non haxeui sprites to be 0,0 relative to their parents... feels more correct
  • b
    (latest git haxeui-flixel btw)
  • b
    ^^ @User
  • d
    perfect, thank you
  • b
    @User - this may, or may not, help you:
  • b
    so there is a little known 2nd paramter to build macros, that lets you define certain bits, so in this example (this is just a code dump):
  • b
    Copy code
    haxe
class BaseDialog extends Dialog {
    public function new() {
        super();
        
        buttons = DialogButton.OK | "Bob";
    }
}
  • b
    base-dialog.xml:
    Copy code
    xml
<dialog title="${title}">
    <hbox width="100%">
        <label width="120" text="Shared field 1" verticalAlign="center" />
        <textfield width="100%" />
    </hbox>    
    <import source="${contents}" />
    <hbox width="100%">
        <label width="120" text="Shared field 2" verticalAlign="center" />
        <textfield width="100%" />
    </hbox>    
</dialog>
  • b
    Copy code
    haxe
@:build(haxe.ui.macros.ComponentMacros.build("assets/base-dialog.xml", {title: "Dialog1", contents: "contents1.xml"}))
class Dialog1 extends BaseDialog {
    public function new() {
        super();
    }
}
  • b
    contents1.xml:
    Copy code
    xml
<hbox width="100%">
    <label width="120" text="Contents 1 field A" verticalAlign="center" />
    <textfield width="100%" />
</hbox>
  • b
    Copy code
    haxe
@:build(haxe.ui.macros.ComponentMacros.build("assets/base-dialog.xml", {title: "Dialog2", contents: "contents2.xml"}))
class Dialog2 extends BaseDialog {
    public function new() {
        super();
    }
}
  • b
    contents2.xml:
1...488489490...1687Latest