https://linen.dev logo
Powered by
# haxe-ui
  • b
    @User - what backend is this? Flixel, right? But basically MSGHero is spot on
  • d
    Yes Flixel - any examples on making custom components? I can imagine the basics, but if I make a custom component, will it adhere to positioning specified by containers like 
    HBox
    and 
    VBox
    ?
  • d
    I guess it should because then 
    addComponent
    will work?
  • b
    yeah, custom components are just components... i mean, all components in haxeui-core are basically just Component derived "Custom" components
  • b
    i am wondering though if, in flixel, you might be able to get away with just "add"ing to the Component... i mean, in haxeui-flixel components are just FlxGroups
  • b
    so i wonder if you could so something like:
  • b
    Copy code
    haxe
var c = new Component();
c.add(myFlxSprite);
myHBox.addComponent(c);
  • b
    i feel like something like that might work, i wonder if there are any gotchas though that stop that from working?
  • d
    I can just add to any component (like directly adding to a container), but then positioning is not respected. I haven't tried with adding to a component directly and adding that component to a container (like what you just posted)
  • d
    I actually don't understand how it positions when you just use 
    add()
    . It seems to treat either the parent or the parent's parent as the first positioned ancestor (i.e. it positions the sprite at that parent's or parent's parent position)
  • d
    But I'll give a custom component a try, that seems like the easiest solution
  • m
    for a custom dialog, can I make a generic one and add components to it? should I just make seperate ones? I'm thinking about an entry box that my have different numbers of input boxes per use
  • d
    I actually use .add in multiple places...maybe I should have switched to custom components a long time ago...lol
  • d
    @User here's a quick demo of the kind of thing I'm trying to accomplish. The issue is that while the components are placed correctly, the sprites inside the component are not placed at the component's (0,0). In my case, both the sprites are placed at the VBox's (0,0) (i.e. they are on top of each other, not in vertical order specified by the order of adding 
    c1
    and 
    c2
    ) Anyone know of workarounds/solutions? Other than placing everything absolutely?
    Copy code
    haxe
var vbox = new VBox();
var c1 = new Component();
c1.add(mySprite);
vbox.addComponent(c1);
var cc = new Component();
c2.add(mySprite);
vbox.addComponent(c2);
  • b
    @User : this is what i use:
    Copy code
    haxe
@:build(haxe.ui.macros.ComponentMacros.build("mydialog.xml"))
class MyDialog extends Dialog {
    ...
}

...

var d = new MyDialog();
d.show();
  • b
    @User - right so maybe the add() method wouldnt work... i guess that makes sense... ill have a play to confirm - but maybe a custom component is the best / only way to go
  • b
    can you paste me some code that you are using to load the sprite? (just so were working from the same page)
  • d
    but even with a custom component, wouldn't we need to 
    add
    the sprite?
  • d
    yes I can send over a minimal example
  • b
    with a custom component it'll almost certainly work
  • b
    (but i can double check that)
  • d
    ok how about I give that a try first - I haven't done that yet, don't want to expend your time unnecessarily
  • b
    @User - sorry, just reread - if you want to reuse the dialog for a different number of inputs cant you just hide fields?
  • b
    @User - send over any sprite loading code you have if you want though, im here now and will take just a few moments to understand a few things 🙂
  • d
    ok sure - here's the sprite loading code
    Copy code
    haxe
var sprite:FlxSprite = new FlxSprite();
sprite.loadGraphic(entry.path, false, Globals.tileSize, Globals.tileSize);
  • b
    this would also work, right:
  • b
    Copy code
    haxe
            var sprite = new FlxSprite();
            sprite.makeGraphic(50, 50, FlxColor.RED);
  • d
    Here's the rest of the code
    Copy code
    haxe
legendContainer = new VBox();


for (entry in legendEntry)
{
    var hbox:HBox = new HBox();

    var name:Label = new Label();
    name.text = entry.name;

    var spriteContainer:Component = new Component();
    var sprite:FlxSprite = new FlxSprite();
    sprite.loadGraphic(entry.path, false, Globals.tileSize, Globals.tileSize);

    spriteContainer.add(sprite);
    spriteContainer.width = sprite.width;
    spriteContainer.height = sprite.height;
    hbox.addComponent(spriteContainer);
    hbox.addComponent(name);
    legendContainer.addComponent(hbox);
}
    I'm trying to make a legend, where each 
    entry
    in 
    legendEntry
    has a 
    name
    and a 
    path
  • b
    (i mean, it ends up being the same thing)
  • d
    yes, I think so
1...487488489...1687Latest