https://linen.dev logo
Powered by
# haxe-ui
  • m
    Niiice! For the UI Builder I'm pretty sure it's doable in VSCode as well
  • m
    Time flies it was 3 years ago
  • b
    yeah, i think the UI builder could be made in a way that it would work everywhere (including as a standalone app)
  • m
    Are you backed for haxe ui?
  • b
    backed?
  • m
    Do you get any funds from all the work on haxe ui?
  • m
    You've been on it for yeaaaars
  • b
    ah, right... well, there is patreon, github sponsers and im working on some paid projects that use haxeui
  • b
    yeah, its crazy really... like years and years and years 😄
  • e
    make the haxe-ui ui builder with haxe-ui
  • b
    for sure... 100%... earlier versions of the builder were made with haxeui, and later versions will be also
  • m
    Thanks for keeping it up to date all this long. I'm rebooting a few project and I realise how some libraries/tech are plainly dead.. it hurts
  • b
    i think thats OSS for ya... to be honest, the fact that bunch of people use it (i reckon i must directly know of 10-15 projects - some private, some not) is defo a huge motivator for me
  • m
    Yes exactly OSS ftw
  • i
    if Microsoft used their own UI tools the way Ian tests his own work, windows would have been fun to develop for past windows 7 🙂
  • i
    nothing like releasing half-baked SDKs and then ignoring them completely for your own apps to let you know it’s a Redmond product
  • n
    then deprecating them 12~24 months later for 
    shiny_new_thing
  • b
  • i
    How do I set the callback of a custom dialogue button? One that's set like
    Copy code
    haxe
this.buttons = EditorState.i18n.tr(prefix + "save-button");
    rather than using 
    DialogButton.OK | DialogButton.CANCEL
  • i
    all I can find is the dialogue's onDialogClose callback
  • i
    essentially I want to get the text input and dropdown choices of the dialogue box and store them to variables, before the dialogue box is destroyed
  • i
    oh ignore me, I didn't realise I could still access the dialogue var from inside the callback 🤦‍♂️
  • b
    cool
  • b
    there is also a "validateDialog" function that you can override, you could do things in there also (if you wanted)
  • b
    as well as stopping the dialog from hiding - for example if certain things arent "right"
  • i
    that sounds very useful, I'll take a look
  • b
    this is the default impl:
  • b
    Copy code
    haxe
    private function validateDialog(button:DialogButton, fn:Bool->Void) {
        fn(true);
    }
  • b
    so basically its always considered "valid" and will always close...
  • i
    button
    being the text of the button that was pressed to activate it, right?
1...864865866...1687Latest