https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • c
    since property group is the container for the properties
  • c
    wonderful
  • m
    Copy code
    haxe
package editor;

import haxe.ui.macros.ComponentMacros;
import haxe.ui.containers.VBox;
import haxe.ui.containers.properties.Property;
import haxe.ui.containers.properties.PropertyGrid;
import haxe.ui.containers.dialogs.Dialog;
import haxe.ui.containers.dialogs.Dialog.DialogEvent;

class MapProperties extends Dialog
{
    var uiRoot: VBox;
    var mapIdProperty: Property;

    public function new()
    {
        super();

        uiRoot = ComponentMacros.buildComponent("assets/editor/xml/map_properties.xml");

        mapIdProperty = uiRoot.findComponent("map_id", Property, true);
        
        title = "Map Properties";
        buttons = DialogButton.CANCEL | DialogButton.APPLY;

        onDialogClosed = onClose;

        addComponent(uiRoot);
    }

    function onClose(e: DialogEvent)
    {
        trace(mapIdProperty);

        trace(mapIdProperty.value);
    }
}
  • m
    But I still don't know exactly what this line does:
    Copy code
    haxe
@:build(haxe.ui.macros.ComponentMacros.build("assets/editor/xml/map_properties.xml"))
  • c
    that line, simplest way i know.... prebuilds and prepares the data needed for what may be asked of it from within that class or page it is within. It ties the data to that class it is called with. I believe thats how that works.
  • m
    But ultimately it should add itself to Dialog hierarchy as a child right?
  • m
    Assuming that, I also assumed searching for something on Dialog recursively would also work, but aparently it doesn't
  • c
    in the way you use the buildcomponent, it ties it to the uiRoot
  • c
    in your code
  • c
    in your case, VBox is the Warden.... you want answers for anything held within, you ask the Warden..... its his block to control.
  • m
    This is clear. But when I use
    Copy code
    haxe
@:build(haxe.ui.macros.ComponentMacros.build("assets/editor/xml/map_properties.xml"))
    How can I find components contained in map_properties.xml afterwards?
  • c
    in stead of buildComponent, just use the findComponent. i believe it is.
  • c
    there shouldnt be a need to build again afterwords, all the data will be availabe to what ever needs it then so long as that class or module is called within other classes or modules so to speak. Then being able to share the info.
  • m
    that's what I did before, got null
  • c
    I may not understand that part perfectly, but.... its how im understanding it. ahhhhhh..... i think i see now....
  • c
    mapIdProperty = findComponent("map_id", Property, true);
  • c
    lass MapProperties extends Dialog { var uiRoot: VBox; var mapIdProperty: Property; public function new() { super(); uiRoot = ComponentMacros.buildComponent("assets/editor/xml/map_properties.xml"); mapIdProperty = uiRoot.findComponent("map_id", Property, true);
  • c
    give me just a sec.... to type this....
  • c
    var mapIdProperty = MapProperties;
  • c
    after that...... then, mapIdProperty = uiRoot.findComponent("map_id", Property, true);
  • c
    if using the @build.........
  • c
    that, i believe should do the trick
  • c
    or something real close.....
  • b
    ill look at this tomorrow, but the first example:
  • b
    Copy code
    haxe
package editor;

import haxe.ui.containers.properties.Property;
import haxe.ui.containers.properties.PropertyGrid;
import haxe.ui.containers.dialogs.Dialog;
import haxe.ui.containers.dialogs.Dialog.DialogEvent;

@:build(haxe.ui.macros.ComponentMacros.build("assets/editor/xml/map_properties.xml"))
class MapProperties extends Dialog
{
    var mapIdProperty: Property;

    public function new()
    {
        super();

        title = "Map Properties";
        buttons = DialogButton.CANCEL | DialogButton.APPLY;

        onDialogClosed = onClose;
    }

    function onClose(e: DialogEvent)
    {
        mapIdProperty = findComponent("map_id", Property, true);

        trace(mapIdProperty);

        trace(mapIdProperty.value);
    }
}
  • b
    makes complete sense and is exactly how i would have done it
  • b
    so if the two traces are returning null, something is off
  • c
    wonderif mapIdProperty: PropertyGrid; would have done it in that
  • b
    i dont see anything wrong with the original example (but i havent run it), if it doesnt work, it should (though i cant think of reason why it wouldnt work)... @User - can you zip the project? (im not going to look at it now though, but will do tomorrow)
  • c
    true.... it should have worked.
1...227228229...1687Latest