https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    Which results in there being more messages about that, than anything else. 😄
  • b
    ah
  • f
    These splitters, no more than four lines of XML, radically improve the UI - thanks so much Ian!
  • b
    This makes me wanna make an editor too... 😄
  • f
    Making a right click menu using the code on the left - is there something I need to do to make the menu close when it is clicked away from, as normal menus do? Also, this is acting on the whole layer component. Is there a way I can bind this to the individual elements of the layer listview? Cheers 😄
  • f
    I'm off for now, gonna try and stop getting to bed at like 2am, might have more brain juice that way 😄
  • h
    Hey guys I'm gonna start making an editor now!
  • h
    I figured the more the merrier
  • h
    jk jk lol
  • b
    splitters looking good 🙂
  • f
  • f
    Feels pretty solid. Added HSL sliders but removed them, felt like something I was only putting in because everyone has it. The precision is just unneeded in an editor like mine 😛
  • b
    ... ... looks really solid
  • f
    Getting a HxCPP GC crash at the moment, though I've also posted this stack trace to #162395145352904705, as I think this is more of a HxCPP issue than a Haxe UI one.
  • f
    Very frustrating
  • b
    what changed?
  • f
    A few things :/ I usually build for html5 and then get a nasty surprise when I build natively. I'll try and narrow it down though 🙂 I just thought I'd post that there because the issue is clearly triggered by Haxe UI, but yeah, strongly doubt that Haxe UI is actually doing anything wrong.
  • b
    If it's reproducible, that would be nice. The new GC apparently still has a few kinks, although from what Rob said last night, seems like only when multithreading.
  • f
    Mmh. My codebase feels large and hairy, and stack traces like that make me feel pretty helpless in diagnosing where my code goes wrong, but if I can make a reproducible, I will 🙂
  • b
    Well GC crashes are probably one of the worst things you can try to debug.
  • b
    Especially when multithreading is in the mix.
  • f
    Yep. Looks like Rob's run into it https://github.com/HaxeFoundation/hxcpp/issues/872 so I've asked him in #501447516852715525
  • b
    I wonder how my soft would go. The way I write things now, they should be deterministic, so once I reach the bug, I should be able to replay back to it (assuming I had logging enabled, and GC is deterministic too – which it might not be).
  • f
    Forgive my beginner question, but by deterministic, you mean not dependent on eg. Math.random or thread operation orders, etc, right? Because my code is large and has lots of moving parts, but nothing really eccentric (threads etc) - the weird stuff must be done by Kha (or, less likely, haxe ui)
  • b
    Yeah, random, time sources, etc. It's not trivial, and always possible I make an error somewhere. 😄
  • b
    But I try to keep it working. And feels pretty solid for now, though I'm at the beginning of it all.
  • b
    Should be fun once I get bugs, or odd visual stuff. I can replay client logic/rendering or server logic separately.
  • b
    Would be nicer if I could also remove all JS dependencies and just run it all in HL or something with better debugging.
  • f
    Mmh. What is it? 😄
  • b
    What is what? 🙂
1...317318319...1687Latest