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

    bright-gpu-74537

    06/20/2019, 9:00 AM
    yeah, like me... its not a great "entry" to android via haxe i guess
  • b

    bitter-family-72722

    06/20/2019, 9:00 AM
    I proposed adding a nice error message for incompatible NDK versions at least
  • b

    bright-gpu-74537

    06/20/2019, 9:00 AM
    yeah, thats the easiest route i guess, though, i do agree, better that you can just "downloading, install, run"
  • b

    bright-gpu-74537

    06/20/2019, 9:01 AM
    rather than "download, install, fail, dispair, google, downgrade, install, run, sigh"
  • b

    bright-gpu-74537

    06/20/2019, 9:01 AM
    😄
  • b

    bright-gpu-74537

    06/24/2019, 9:43 PM
    https://twitter.com/IanHarrigan1982/status/1143272159629991938
  • h

    handsome-television-62908

    06/24/2019, 9:46 PM
    That's fantastic!
  • q

    quick-king-64105

    06/24/2019, 11:38 PM
    That's cool, actually
  • b

    brainy-machine-50829

    06/25/2019, 5:58 AM
    Pretty sweet. Does that support different item heights? I had issues with that in wpf, after lot of trials I found a hackish way to override calculation of item height to not use layout but custom code (I knew exactly how big my items were). Still was around 10-100 times slower than fixed height items. 😦
  • b

    bright-gpu-74537

    06/25/2019, 7:02 AM
    there is scope for variable item heights in virtual scrollvews (listview / tableview) but i havent looked at it in a whlie
  • b

    bright-gpu-74537

    06/25/2019, 9:53 AM
    2.3 million with a pretty complex renderer
  • b

    bright-gpu-74537

    06/25/2019, 9:53 AM
    😮
  • b

    bright-gpu-74537

    06/25/2019, 9:54 AM
    https://pastebin.com/W3RZbnGh
  • q

    quick-king-64105

    07/01/2019, 7:53 AM
    Any news on those two issues, by chance?
  • b

    bright-gpu-74537

    07/01/2019, 9:37 AM
    im not sure tbh... @brave-kangaroo-30399 ? 😃
  • q

    quick-king-64105

    07/01/2019, 10:04 AM
    I ran a quick test because curiousity.
  • q

    quick-king-64105

    07/01/2019, 10:04 AM
    This is interesting and may explain some things
  • q

    quick-king-64105

    07/01/2019, 10:04 AM
    https://github.com/HaxeFlixel/flixel/blob/master/flixel/FlxState.hx#L169
  • q

    quick-king-64105

    07/01/2019, 10:05 AM
    Insofar as where it's opened... not what you'd expect, either.
  • q

    quick-king-64105

    07/01/2019, 10:05 AM
    https://github.com/HaxeFlixel/flixel/blob/master/flixel/FlxState.hx#L76
  • q

    quick-king-64105

    07/01/2019, 10:06 AM
    As to why it's not what one would expect...
  • q

    quick-king-64105

    07/01/2019, 10:07 AM
    The sort of typical way to do this is to set
    FlxState.active = false
    if you were to do so manually. But it's not what substates are doing.
  • q

    quick-king-64105

    07/01/2019, 10:07 AM
    I'm not sure how to work around that.
  • b

    bright-gpu-74537

    07/01/2019, 10:07 AM
    So that one might be a flixel issue?
  • q

    quick-king-64105

    07/01/2019, 10:08 AM
    "Issue" is a strong word. "Quirk" is more appropriate, I think.
  • b

    bright-gpu-74537

    07/01/2019, 10:08 AM
    Right
  • q

    quick-king-64105

    07/01/2019, 10:08 AM
    It is possible to see if a substate is open, I think. I'd have to double check that logic.
  • b

    bright-gpu-74537

    07/01/2019, 10:08 AM
    But i mean, its flixel that exhibits the quirk, rather than haxeui-flixel?
  • q

    quick-king-64105

    07/01/2019, 10:09 AM
    Well, it's true that haxeui-flixel doesn't incorporate into flixel's state/substate flow nicely and neatly, but the fact that this is the design also may explain both errors somewhat under the hood. I can't give a straight answer because it seems like "flixel is a little strange here" and "haxeui-flixel doesn't incorporate into flixel's way of doing this" are both true.
  • b

    bright-gpu-74537

    07/01/2019, 10:10 AM
    right - that makes sense
1...727374...1687Latest