https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • no one will know it exists, and i personally have no idea what the consequences of this error even is šŸ˜‚
    a
    no one will know it exists, and i personally have no idea what the consequences of this error even is šŸ˜‚
  • I ran into an issue with Kha and Images using `Image.resource = kha.Image`. Created an issue on the haxeui-kha repo that covers the details
    h
    I ran into an issue with Kha and Images using 
    Image.resource = kha.Image
    . Created an issue on the haxeui-kha repo that covers the details
  • a

    https://cdn.discordapp.com/attachments/565569107701923852/1095332086459666452/image.pngā–¾

  • <@525025580106907659> - do you know when events was added to `sys.thread.Thread`... my 4.0.5 CI fails, and im wondering if i just say "must use haxe 4.2" (or whenever it was added)... unless there is a 4.0.5 way to achieve the same?
    b
    @powerful-morning-89 - do you know when events was added to 
    sys.thread.Thread
    ... my 4.0.5 CI fails, and im wondering if i just say "must use haxe 4.2" (or whenever it was added)... unless there is a 4.0.5 way to achieve the same?
  • cool - it doesnt shadow timer anymore, and instead implements the haxe event loop, ive also update core/http (if you hadnt already updated)
    b
    cool - it doesnt shadow timer anymore, and instead implements the haxe event loop, ive also update core/http (if you hadnt already updated)
  • oh, i didn't, i'll do that now
    a
    oh, i didn't, i'll do that now
  • basically, update everything šŸ˜„
    b
    basically, update everything šŸ˜„
  • ohhh may have a 4.3 + haxeui issue
    a
    ohhh may have a 4.3 + haxeui issue
  • where is the @:bind metadata defined?
    a
    where is the @:bind metadata defined?
  • but the error magically went away with restarting the language server
    a
    but the error magically went away with restarting the language server
  • but i want to see if i can fix it should it crop up again
    a
    but i want to see if i can fix it should it crop up again
  • you can try the `-D no-macro-cache` build option too, see if that makes any difference?
    i
    you can try the 
    -D no-macro-cache
    build option too, see if that makes any difference?
  • at some point a year or two back, it was the only way I could get menubars working
    i
    at some point a year or two back, it was the only way I could get menubars working
  • I may have to try that option, Iā€™m getting bizarre cache behavior again, where adding a trace causes my UI to show up
    b
    I may have to try that option, Iā€™m getting bizarre cache behavior again, where adding a trace causes my UI to show up
  • (not haxeui specific)
    r
    (not haxeui specific)
  • No because I can't figure out how to repro it
    r
    No because I can't figure out how to repro it
  • It happens seemingly at random
    r
    It happens seemingly at random
  • yeah, I'm not sure if it's haxe 4.3 or haxeui, even tho the error occurred on haxeui things
    a
    yeah, I'm not sure if it's haxe 4.3 or haxeui, even tho the error occurred on haxeui things
  • that's why I wanted to know where the @:bind meta was defined so I could confirm in the moment
    a
    that's why I wanted to know where the @:bind meta was defined so I could confirm in the moment
  • It's happened to me pretty often in haxeui, then fixed/uncommon at some point last year, now back with either 4.3 or a very recent haxeui or heaps backend commit
    b
    It's happened to me pretty often in haxeui, then fixed/uncommon at some point last year, now back with either 4.3 or a very recent haxeui or heaps backend commit
  • For me, `Screen.rootComponents` should be empty, but somehow `.indexOf(rootUICompo) > -1` returns true. It triggers a `removeChild` in heaps and never actually gets added
    b
    For me, 
    Screen.rootComponents
    should be empty, but somehow 
    .indexOf(rootUICompo) > -1
    returns true. It triggers a 
    removeChild
    in heaps and never actually gets added
  • But when I add `trace(this)` in that chain, the condition evaluates to false as expected, and it all works fine
    b
    But when I add 
    trace(this)
    in that chain, the condition evaluates to false as expected, and it all works fine
  • Or, like right this moment, it works fine without any code changes
    b
    Or, like right this moment, it works fine without any code changes
  • In other words, I kinda have a repro if you guys have `-D` or macro-related suggestions to debug
    b
    In other words, I kinda have a repro if you guys have 
    -D
    or macro-related suggestions to debug
  • I can't tell if this is related to NotBilly's thing lol, it's been bugging me tho
    b
    I can't tell if this is related to NotBilly's thing lol, it's been bugging me tho
  • https://gyazo.com/2cfc21ee5b3acf838ba14f1ad6e881c4
    c
  • rust-wasm certainly is a target that exists
    c
    rust-wasm certainly is a target that exists
  • its really worth pointing these things out, cause there are people actively looking to solve these issues
    a
    its really worth pointing these things out, cause there are people actively looking to solve these issues
  • ik what rust is but rust-wasm? nope, dunno what that could be
    c
    ik what rust is but rust-wasm? nope, dunno what that could be
  • ohh
    c
    ohh
1...163216331634...1687Latest