https://linen.dev logo
Powered by
# haxe-ui
  • b
    macros are the only danger as far as i can see, since the resulting .js code is run on the browser, not my server
  • b
    btw why shouldnt you release haxeui 1.4.1 for core now? it has a bunch of bug fixes + lots of docs
  • b
    ... ... probably
  • b
    tbh why not now
  • b
    because im busy, and releasing haxeui isnt a 10 second job either
  • b
    because of the changelog or website update?
  • b
    just releasing all the backends, i have a mostly automated system, but its not bullet proof and things need checking
  • b
    oh i didnt mean to release for the backends
  • b
    i ment specificly haxeui-core
  • b
    they need to stay in parity version wise
  • b
    since it contains a bunch of bug fixes and little things
  • b
    otherwise it leads to confusion
  • b
    so if haxeui-core goes to 1.4.1 so do all the backends, even if there are no changes
  • b
    well that takes waaaaayyyyyyyyyyyy too much time
  • a
    probably but it's definitely the better long term solution
  • a
    less confusing for people who use the lib
  • b
    i ment releasing 1.4.1 for everything takes too much time
  • r
    Thank you!!
  • r
    Works as expected!
  • b
    I successfully added monaco editor, but typing in it activates other elements in HaxeUI. 😄
  • b
    Didn't find any code to prevent that in the haxeui-code-editor repo. Any hints? 🙂
  • b
    Fixed by 
    editor.onDidFocusEditorWidget(_ -> this.focus = true);
    . 🙂
  • b
    interesting, what other elements were "activated" ?
  • b
    and how were they activated? Like with tab or something?
  • b
    Dunno, I just have one button, I guess it was active as first element.
  • b
    So when I pressed enter/space in monaco, it triggered the button.
  • b
    Cos HaxeUI didn't know the focus is on the editor.
  • b
    ah
  • b
    how did you add the monaco editor?
  • b
    maybe if it was wrapped in an InteractiveComponent it would work
1...102610271028...1687Latest