https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • k
    In examples I only see how to call Logger.method static methods
  • k
    I create a component using ComponentMacros.buildComponent("path_to_comp");
  • f
    I don't know if there's a cleaner solution, but the way I do it is have a 
    setEditor(editor)
    in my XML component's haxe class. I use that to pass in the variable from a parent class, referring to my class by id.
  • f
    Ah
  • f
    Okay, yeah well it wouldn't work if you just build the component
  • f
    You'd need to extend the component as I always do, with a build macro.
  • f
    There may be a cleaner soln that I'm not aware of
  • f
    Hold on
  • f
    But if you do it your way, then you can just refer to the class things by ID
  • f
    and you're already in your code, not a class, so it shouldn't be a problem.
  • f
    Unless you're specifying onClick in the xml, in which case, don't 😆
  • k
    I need to refer a runtime instance of the class so I call a method in some context. I mean the State(Screen) from which I instantiate a HaxeUI component.
  • k
    But I think it's intended to be handled some other way with HaxeUI ))
  • k
    As I don't see anything except 
    params
    you can pass into ComponentMacros.buildComponent() which is unrelated to component context.
  • k
    So writing a wrapper component is the only way to go?
  • k
    I would like to avoid that extra code 🙂
  • k
    Ok, what is a BindingManager class? Isn't it there to bind some variables to a component?
  • f
    Sorry, was afk grabbing lunch. I haven't used BindingManager before, so I can't help you there. I think you can do this super simply through ID's though, without a 'wrapper' class.
  • f
    buildComponent is generating the xml dynamically off the xml, which means that components with ID's can just be referred to as a property
  • f
    Copy code
    myXMLComponents = ComponentMacros.buildComponent(...)
var a = 1
myXMLComponents.theButtonID.onClick = function () { trace(a); };
  • k
    No problem. I'm not in a hurry. You're very helpful 🙂
  • k
    Hmm. Trying to wrap my head around ID's. I think I'm missing some context.
  • k
    oh i see
  • f
    So if you xml file has a button that you want to refer to in haxe, just specify an ID attribute in the xml button 
    <button id="theButtonID" text="My button that prints a" />
  • k
    yeah. just figured out. thanks )
  • k
    This actually looks like a viable solution.
  • k
    Referring by ID does not work without wrapper component. The 
    buildComponent
    method returns a Box instance which apparently does not have my 
    joinButton
    property which results in 
    Uncaught exception - Invalid field access : onClick
    on joinButton which is null.
  • f
    Hm, but 
    joinButton
    appears in autocomplete?
  • k
    I code in Vim and vaxe somehow does not autocomplete anything for me for some time. I just use it as is 🙂
  • f
    Ah yes, vaxe has given me my fair share of grief in the past. Gave up about a month ago and have been using vscode with the vim plugin 😆
1...322323324...1687Latest