https://linen.dev logo
Powered by
# haxe-ui
  • m
    I'll try to isolate that, because the project is a little big with 99% unrelated stuff
  • b
    in fact, looking at the code again, you shouldnt even need the findComponent... you should be able to do 
    trace(map_id.value)
  • m
    I'll post it here as soon as I have it
  • m
    I might try that and see if it works
  • b
    ok, cool... ill knock up a nonsense example tomorrow and see if that does something wrong
  • c
    now that whole trace thing working with the @build makes more sense to me, i can visualise it.
  • c
    sweet, thanks
  • c
    now to go back to figure out how to convert a few lines of javascript to haxe..... these slight variable/array differences in layout are like trying to solve a rubix cube to me.
  • c
    and i'm not good with a rubix cube lol
  • c
    once i understand it i'll have to write a short guide..... "Understanding JS vs Haxe Types and Arrays for Dummies"
  • m
    @User seems like I can't have a custom constructor for a class that extends Dialog, is that intended? haxe ui macros complain of missing parameters.
  • c
    did it say which parameters?
  • m
    the only one I've created
  • m
    function new(onSave: String -> Void)
  • m
    then it complains onSave is missing at build time
  • c
    maybe..... function new onSave(onSave: String->Void) or something similar.... so it clearly knows what onSave is? hmmm.... or is there something missing.... i'll take a peek at the api.... if you couldnt have a custom constructor for it, it would cleary tell you i do believe.
  • c
    clearly.....
  • b
    haxeui components should always be able to be constructed with no params (because of xml) so you can create custom constructors, but they have to have default params also (assuming im understanding the issue)
  • m
    Ok, I can work with that
  • b
    Copy code
    haxe
@:build(...)
class MyComponent extends Box {
    public function new(foo = "bar") {
        super();
    }
}
  • b
    something like that should be fine
  • m
    I tried that, worked fine. Maybe the best would be to respect the empty constructor, and maybe work with an initialization routine, but anyway, that problem is out of the way
  • b
    yeah, i generally dont use constructor params and rather expose properties on the class, but i guess its preference
  • b
    var d = MyDialog("bob", "tim")
    vs 
    var d = MyDialog(); d.x = "bob"; d.y = "tim"
  • b
    with dialogs its i suppose different, but they are, after all, haxeui components and normal haxeui components with constructor arguments become a pain with xml (or markup in general)
  • b
    <myComponent constructor="bob, 1, true, 'tim'" />
    <--- i dont like the idea of this
  • b
    i prefer 
    <myComponent a="bob" b="1" c="true" d="tim" />
  • c
    that gives me a new view on that dang js i'm trying to make work..... heheh, thanks again.... i'll just change how its setup to make it work.
  • c
    yep, that was great timing..... just like a rubix cube.... tear it apart and put it back together the way I know to solve it.
  • m
    @User One last thing 😅 ... I'm trying to fill e property of type "list" with dynamic options loaded from script. But I can only make it work when it already has options in the xml. When it's empty in the xml I get:
    Copy code
    Called from haxe.ui.core.Component::addComponent haxe/ui/core/Component.hx line 291
Called from haxe.ui.containers.properties._PropertyGroup.Builder::addComponent haxe/ui/containers/properties/PropertyGroup.hx line 132
Called from haxe.ui.containers.properties._PropertyGroup.Builder::buildEditor haxe/ui/containers/properties/PropertyGroup.hx line 175
Error : Null Object Reference
1...228229230...1687Latest