https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b

    bitter-family-72722

    06/17/2019, 8:03 AM
    does that only happen on hxcpp, or neko too?
  • f

    fierce-restaurant-45913

    06/17/2019, 8:03 AM
    neko too
  • f

    fierce-restaurant-45913

    06/17/2019, 8:03 AM
    but neko don't throw error
  • b

    bright-gpu-74537

    06/17/2019, 8:12 AM
    ok, so the fix in that issue above does stop the crash
  • b

    bright-gpu-74537

    06/17/2019, 8:13 AM
    Copy code
    haxe
            trace(path);
            if (path == "/manifest/default.json") {
                path = "manifest/default.json";
            }
  • b

    bright-gpu-74537

    06/17/2019, 8:13 AM
    in lime.utils.Assets
  • b

    bright-gpu-74537

    06/17/2019, 8:13 AM
    but, now it seems it cant find any assets (like the css files)
  • b

    bright-gpu-74537

    06/17/2019, 8:14 AM
    i could put them as haxe resources... wouldnt cause any issues, but i guess this indicated an underlying problem with lime?
  • b

    bitter-family-72722

    06/17/2019, 8:17 AM
    yeah.. maybe it would be good to comment in the issue, so it becomes clear this is something that affects a lot of people
  • b

    bright-gpu-74537

    06/17/2019, 8:17 AM
    👍
  • b

    bitter-family-72722

    06/17/2019, 8:17 AM
    not me for some reason though, just built a Flixel demo and it runs fine ¯\_(ツ)_/¯
  • b

    bitter-family-72722

    06/17/2019, 8:18 AM
    so I wonder what the conditions to reproduce it are
  • b

    bright-gpu-74537

    06/17/2019, 8:19 AM
    yeah, it does seem strange, as it just sort of popped up... with an app that was previously working
  • b

    bright-gpu-74537

    06/17/2019, 8:19 AM
    i think the only thing that updated was hxcpp
  • b

    bright-gpu-74537

    06/17/2019, 8:20 AM
    well, i replied
  • b

    bitter-family-72722

    06/17/2019, 8:22 AM
    hm... I'm on latest hxcpp too though
  • b

    bright-gpu-74537

    06/17/2019, 8:49 AM
    @User - one small thing (doesnt affect the crash though) is in your css you have:
  • b

    bright-gpu-74537

    06/17/2019, 8:49 AM
    Copy code
    css
    .hbox {
        width:100%;
        content-width:100%;
    }
  • l

    loud-salesclerk-7438

    06/17/2019, 8:49 AM
    I had the same default asset issue yesterday, it only happened on Windows (Linux build was fine) with C++ (neko also fine) and it would either show an error message and a stacktrace (when using
    -debug
    ) or just show a white screen with a frozen progress bar (without
    -debug
    )... I "fixed" it by downgrading from hxcpp 4.0.19 to 4.0.8 (that's the version I had running before, there might be later versions that also fix the issue)
  • b

    bright-gpu-74537

    06/17/2019, 8:49 AM
    this makes ALL hboxes 100% width, which you almost certainly dont want to do... a good example of why you dont want to do this is the tabview buttons:
  • b

    bright-gpu-74537

    06/17/2019, 8:51 AM
    ie, you'll notice the little buttons on the tabview bar because there are more buttons than fit
  • b

    bright-gpu-74537

    06/17/2019, 8:51 AM
    thats because i removed making all hboxes 100% width
  • b

    bright-gpu-74537

    06/17/2019, 8:52 AM
    again, doesnt fix the crash (which i can reproduce) but thought i would mention it since i noticed it (thought there was something wrong with tabview at first)
  • b

    bright-gpu-74537

    06/17/2019, 8:53 AM
    @loud-salesclerk-7438 - ok interesting, so it probably is something to do with hxcpp then
  • l

    loud-salesclerk-7438

    06/17/2019, 8:54 AM
    yeah, I think something changed in 4.0.19 that makes lime/openfl fail on Windows...
  • u

    user

    06/17/2019, 8:57 AM
    so it was just hxcpp then?
  • b

    bright-gpu-74537

    06/17/2019, 8:57 AM
    checking now
  • u

    user

    06/17/2019, 8:58 AM
    I had the same problem
  • u

    user

    06/17/2019, 8:58 AM
    i reverted back a version for all my libs tho and it works nice 😛
  • b

    bright-gpu-74537

    06/17/2019, 9:00 AM
    yup, confirmed... rolling back to 4.0.8 fixed it
1...626364...1687Latest