The dialog designer crashes on me for a specific dialog. It wouldn't even let me send a bug report, it just freezes and windows terminates the program.
Attached the dialog
Additionally, I would suggest using a folder or something of the sort, where the default script files are stored. The program could pull the SC2 script files from your game by pressing a button and put them in that folder. But you also have the chance to use script files for other versions, modified versions or even additional files (which may be included in mods or something).
I'm currently editing the Galaxy++ source so that functions are automatically gathered from the various starcraft 2 script files inside the game mpq's. As SBeier said, right now the available functions are hardcoded, so there may be some missing ones. Functions added with 1.5 are also not available yet.
I'm not sure when I will finish this but it's going well so far. So reading the script files and parsing them for functions/constants works already but the integration with the editor is missing. Since I don't really have a good understanding of the project yet, this may take some time.
Highlights the last line as comment, but it is included in the output script.
Suggestion: Add a "Save As" functionality, so we can quickly save a project under a new name (for backups etc). Currently, we need to copy the files manually.
I might have mentioned it already, but I would really like to have copy%paste support for the dialog designer. Either for just copy&pasting fields (you can copy most fields, but paste doesn't work that good. Try to paste a string in an image field), probably by just selecting the field instead of the actual text, similar to how it is possible in the Galaxy Editor for Data fields, and/or for entire dialogs or dialog items.
Bug with dialog items for the dialog designer: When trying to change min/max values for certain dialog items, you are only allowed to write fixed numbers in a,b format, instead of a.b. This , will be added to the output script, causing a syntax error.
The switch is not a bug. In the documentation it does say "Note that it is possible to fall through to the next case if one doesn't write break, like it is done from marine to zealot."
Yes, it should be able to fall though, but the 2nd case should only be called, if the case itself is true, right? For this code, the 2nd case should never ever be true; the switch variable is always true and the case is always false. Even if it falls through the first case, it should not run the 2nd one in this case, or did I misunderstand something?