https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    ... well... it only took me TWO days ( 😮 ) ... but i finally got native tree view working! 🥳
  • e
  • b
    yeah, will have to wait... treeview too waaaaaay longer than i thought
  • b
    pdcurses, as a backend, isnt my highest priority. 🙂
  • b
    @bright-gpu-74537 when you compile haxeui projects to neko, do you encounter stack overflows?
  • b
    i get a stack overflow whenever compiling any haxeui-openfl project
  • f
    is there a reason why input fields like text or number don't work inside heaps?https://gyazo.com/23cbaf0c4b1fd80d27ea8157be5bd8e7
  • b
    hmmm, nope they should work fine i think... ill check it out
  • b
    i hadnt compild to neko for ages, just tried now and yeah, i get the SO error... :/ This is going to be almost impossible to track down
  • b
    do you know how to get a stack trace out of neko?
  • b
    sadly i dont, but thats iffy because i need a download bar and detached processes - hl doesnt launch 
    PROGRESS
    when downloading something with openfl, and hxcpp doesnt support detached/non-blocking processes
  • b
    iirc neko works for both, and is also small in exe size
  • b
    i think id be surprised if neko had different behaviour to hl and/or hxcpp (but i could be wrong). You might want to check that. Obviously id like to get it working with neko, but its going to be an absolute nightmare trying to back track to when in started happening (years and years of commits)
  • b
    i asked the openfl team, turns out hl is still not fully supported by openfl
  • b
    so PROGRESS event just doesnt work, and when compiling to hl/debug you cant even request in the first place because of an internal curl error
  • p
    @bright-gpu-74537 a basic haxeui projects gives me a stack overflow on openfl+neko even with Haxe 3.4.7. So it's not a regression in the compiler, but in haxeui.
  • b
    right, didnt really think it was the compiler tbh, figured it was haxeui, but working out when and what is going to be a pain
  • b
    (but thanks for confirming 🙂 )
  • p
    git bisect
    is your friend in cases like this assuming you have lockfiles and can still compile old commits
  • b
    yeah, i should be able to compile old versions, ill basically go back to like, dunno, haxe v1.1 or something, see if that works, if it does, then 1.2 and see if i can whittle it down... but not going go down that rabbit hole for a while... got loads of (non haxeui) stuff to get on with
  • p
    I get a stack overflow even with haxeui-core 0.0.1.
  • b
    hmmmmm
  • b
    ive defo run haxeui-openfl on neko before... for sure
  • b
    but not for ages no idea how long long, but years
  • b
    neko compilation seems to be causing stack overflows for a lot of people recently
  • p
    haxeui-core 0.0.1 is 5 years old at this point. So at least 5 years?
  • b
    honestly no idea... years, dunno if its 5, 3...
  • b
    :/
  • b
    gonna have to convince the compiler team that it's worth fixing before they completely stop working on neko 😅
  • p
    The easy solution is 
    rm src/generators/genneko.ml
1...123412351236...1687Latest