https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    when you say "writing a macro" what do you mean?
  • b
    you mean a vscode task? Or a haxe macro?
  • h
    vscode task
  • b
    gotcha
  • h
    ok yeah lmao vscode just doesn't know how to build
  • b
    yeah, i dont think language server comes into it at that point
  • h
    Copy code
    json
{
    "type":"shell",
    "command":[
        "haxe",
        "hxwidgets.hxml"
    ],
    "label": "Build [default]"
}
    this one works
  • h
    even though it does literally the exact same thing
  • h
    I'm just gonna blame microsoft and keep working
  • b
    or the vshaxe plugin? Maybe type:hxml is doing something cooky
  • h
    lemme look
  • h
    yeah I have no idea
  • h
    for all intents and purposes I'm 99.99% sure these do the same thing
  • b
    well... ... ... ... they cant be 😉
  • b
    if input is the same, and the output is different the process must be different 🙂
  • h
    it could be that one runs as a process and the other runs as a shell, and hxcpp doesn't like process runners
  • h
    that's what my first thought is at least
  • b
    well, this is the build though... so i think its more about module resolution (ie, paths)
  • b
  • h
    yeah, they both reference the same libraries
  • b
    ¯\_(ツ)_/¯
  • h
    problem is solved enough for me so like
  • h
    brb, I'm "at work" so I have to "do my job"
  • h
    what event should I bind to if I want something to run when an item is selected from a menu bar?
  • h
    I have it set to MouseEvent.CLICK on the menu option itself, is there something better?
  • h
    or, like, something that works at all
  • b
    MenuEvent.MENU_SELECTED
    on the menu bar
  • h
    but how can I tell what option was selected through that?
  • h
    does MenuEvent have an option I can feed into a switch?
  • b
    event.menuItem.id
1...125212531254...1687Latest