https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • h
    @bright-gpu-74537 one difference between mine and yours is that I don't use 
    app.ready()/app.start()
  • h
    I use 
    Screen.instance.renderTo(g2);
  • h
    Not sure if that's what's done internally
  • h
  • h
    In a list view say you had an item renderer that included a button. How would you enable/disable that button? I tried in the onComponentEvent of the listview to do 
    e.source.findComponent("btn", Button).disabled
    but that failed to work. . .
  • h
    Ohh hmm I suppose the source could be the button actually. Didn't think about that
  • b
    i actually dont think there is a good way to link this up yet (at least using default / xml type renderers)
  • b
    ideally it would come from the datasource and something like binding, something like:
    Copy code
    xml
<item-renderer>
    <button disabled="${myDisabledProperty}" />
</item-renderer>
...
<data>
    <item myDisabledProperty="true" />
</data>
  • h
    Oh for sure, that'd be pretty sweet!
  • b
    i actually think i have a stashed change somewhere that does exactly that, was a while ago though, so it likely conflicts - ill have a look when i get a moment - i do remember i wanted / needed it for something - i think in the end i went with a fully custom (class based) renderer
  • h
    The binding aspect of it would be pretty interesting, getting it to work across different components that use item renderers sound interesting too. I wonder what the API for it would look for it in general
  • b
    i think it would be the same, this would be at the itemrenderer level, not "the component that uses item renders" level
  • h
    Ahh gotcha
  • a
    I'm getting an error
    Copy code
    ComponentMacros.hx:891: characters 92-94 : Reification $v is not allowed outside of `macro` expression
    when using haxeui-flixel, seen this problem on this channel and the heaps discord quite a bit, any suggestions as to how to solve it? I'm thinking this might be because of the version of haxe I'm using possibly
    Copy code
    haxe: 4.3.0-rc.1+a985681

flixel: [5.2.2]
haxeui-core: [1.5.0]
haxeui-flixel: [1.5.0]
haxeui-openfl: [1.5.0]
  • f
    Try to use git versions of haxeui-core / flixel/openfl
  • a
    Updated all dependencies to use git versions and now I get an output to the console that says Stack Overflow
  • b
    yoplala, you are like a ninja - i never see you but then... swooosh, solution.
  • f
    hmm, still try haxelib list to see if it's the case, I know there's a bug with ahxelib when you set like haxeui-openfl to git, it sets haxeui-core to 1.5. I think Ian Harrigan was playing with haxe 1.3 lately, so I would think it works with haxe 1.3
  • a
    I see both 1.5 and git
  • b
    that doesnt make sense, what does stack overflow have to do with anything?
  • b
    which has the square brackets around? Can you screen shot / paste?
  • a
    Git has the brackets, I just tried removing 1.5.0, but the same error pops up

    https://cdn.discordapp.com/attachments/565569107701923852/1098703489653293108/image.png▾

  • f
    lol 🥷 I actually wear ninja shoes in real life .... yeah I haven't been so much on discord lately . It just coincidence.
  • b
    looks right, restart vscode? Same issue from terminal / cmd?
  • b
    a happy coincidence none-the-less
  • a
    Tried restarting vscode and powershell, still the same issue
  • b
    im not sure, it defo is (was) a valid issue, that was (is) defo fixed in git versions
  • b
    i plan on making a release this weekend, but im just gathering notes at this point, and you might want to work out whats going on in your system regardless
  • f
    When I open the discord webpage it opens haxeui ... I actually I registered to discord because of haxeui , before I had always temporary accounts, then this haxe discord forced me to have a registered one
  • a
    I have another computer with the standard 4.3.0 version of haxe, I'm thinking maybe it has something to do with the release candidate. I'll give it a try after dinner (and possibly after trying out the new dota 2 patch that I'm super excited about) and see if it's an issue just with this dev environment
1...163816391640...1687Latest