https://linen.dev logo
Powered by
# haxe-ui
  • a
    but they have a custom implementation whereas vshaxe uses the foundations official implementation
  • b
    HD is super dogdey in its own ways, and its gotten worse since its never updated
  • b
    i guess im more used to its quirks
  • a
    yeah
  • a
    i switched over to vshaxe/code in the early days. compared to what it used to be, it's a lot better lol
  • a
    i think it'll improve in time, they probably just have certain priorities that we'll probably never know
  • a
    it might just end up being fixed by some smart community member
  • a
    the flaws of vshaxe help me learn the api better so it's not all bad 😁
  • b
    yeah, i think that possibly why my gripe is minimal... i know my api, and also, i was used to just dev'ing cpp in notepad type things where completion simply wasnt a thing
  • b
    ive never been a "i cant function without my ide telling me what to type" basically
  • b
    that said, it is useful, no doubt... and vshaxe is "alright", fd / hd is "better" (for me at least)
  • r
    It's honestly my biggest gripe with haxe :/
  • r
    The cycle of "I don't know what this part of the library wants so I'll wait for completion", then completion never happens so I click go to definition, then "no definition found", then I restart the language server a few times until it gives me a suggestion other than "final"
  • r
    I feel like it shouldn't be that slow; I get that it has to resolve macros and stuff but so does c etc
  • r
    Using vscode at work for ts and then at home for haxe are unfortunately two very different experiences
  • m
    I do miss faster auto completion, more from the perspective of writing faster than actually figuring out APIs though. I don't know why it's so slow though.
  • m
    TS autocompletion is lightning fast
  • o
    Ian 'Lapace' is much faster to render than vscode so hoping it eventually gets haxe support
  • o
    I think the vs layout engine is not fast with haxe macros together expect it is worse
  • a
    i'm not sure haxe's macros are what cause it to slow down, but more of the lsp itself
  • a
    i've used cpp in vscode as well (abeit not for a very long time) and it worked fine/faster
  • a
    afaik, any issue that is present in vscode, will translate to any other IDE that also uses haxe's LSP
  • b
    how can i make a VBox scroll?
  • b
    like vertically
  • b
    it doesnt do that automatically when i set maxHeight
  • m
    you have to use scrollview for that
  • m
    http://haxeui.org/explorer/ and go to scrollviews
  • m
    if you want only to scroll vertically you have to use 
    contentWidth="100%"
  • m
    using the haxeui component example it will be something like this http://haxeui.org/builder/?innvtw
  • b
    👍
1...111711181119...1687Latest