https://linen.dev logo
Powered by
# haxe-ui
  • h
    unfortunately not, the buildComponent is right under the initialization the error went away by closing and reopening vscode as usual, I just got preoccupied because it's the fourth time I have to restart the program this evening which is way more than usual
  • b
    @handsome-processor-40961 it’s super annoying, something to do with the completion server and haxeui’s macros not being happy together
  • b
    You can restart the language server in VScode to avoid the longer turning off the whole thing
  • h
    sorry to hear, but I'm glad the issue is known and thanks for the tip!
  • p
    @bright-gpu-74537 have you made any progress on the Editor? Dont want to pressure you though
  • b
    @User - not yet, needs another few hours. I was going away for the weekend, but were in lockdown now, so that aint gonna happen. Gives me a chance to finish off the editor, play with the focus manager and mess about with flixel actions
  • b
    @User - yeah, language server and haxeui dont play well it seems... ive tried a few things to make it better, but nothing seems to have worked... One thing i did see the other day was this "registerModuleDependancy", i have no idea if that will help, but its worth a try... ill have a play with it at some point and see
  • c
    🙂 I'd welcome some examples of that (googling and forum, couldn't find any yet while ) . I've just been trying to play with it on a HTML5 target with no luck.
  • c
    (FocusManager)
  • b
    to be honest, the FocusManager is in need to a total rewrite (probably)... its in pretty much the same state from the very initial implementation god knows how long ago
  • b
    and that initial impl was always supposed to be a placeholder of sorts
  • b
    it just never got anymore attention after that
  • b
    or not much / enough anyway
  • c
    Ok don't know if we can be of any help...
  • b
    i think the first step is just to roll out a new, better thought out manager, and then take it from there really
  • p
    Alright thanks
  • l
    setPosition(x,y) not working ?
  • l
    Did I miss something to make it work ? seems other properties works , e.g. rotation alpha , but x,y not..
  • m
    @User no pressure but, any news on flixel backend supporting mobile?
  • b
    @User - 👍
  • b
    @User - the problem is that i cant override set_x / y in heaps as they are inline... you can use .left / .top though (which are the correct haxeui properties, if i could override the setters in heaps then they would just set left / top)
  • b
    @User - ive obviously completely forgotten, but whats the issue with mobile? v1.3 is going to be all about mobile (native too), but i assumed flixel was fine on mobile (as i said, ive likely just completely forgotten)
  • b
    Macros could fix that for you... 😄
  • b
    can they?
  • b
    on heaps' h2d.Object?
  • b
    I don't know context of the issue, but... as a very hackish solution to any 3rd party code problems...
  • b
    You can do a hxml --macro to add build metadata to anything you want in the 3rd party code.
  • b
    And adjust it there. Removing inline or completely changing code, not difficult.
  • b
    right, and then i could just remove the inline from the field
  • b
    top / left is the more "haxeui" way to do it anyway, so i wonder if its worth going through all the effort of hacking heaps code though
1...563564565...1687Latest