I think I have fixed all bugs that were reported. I hope I didn’t miss any!
I believe I have fixed the outlining bug. It now works properly in the "class name { " format, with the opening brace on the same line as the class / event name.
During first startup, it is still impossible to select any other folder than ‘etmain\maps’, and you should still use this folder. However, if you have your scripts somewhere else, you can select a secondary ‘scripts’ folder in the Options. The Open / Save dialogs will initiate in this directory.
When you open a script file, the corresponding BSP file (based on its name) is searched in the same directory. If it is not found, a search for the same BSP file is done in the ‘etmain\maps’ directory you selected, as it is likely that your BSP file is there. If the BSP file is found in the etmain\maps directory, a message in the Message List informs you about that.
This is why it is important that you still use the correct etmain\maps directory.
Additionally, you can now also use the Select BSP button to manually select a BSP file to import.
The File Browser Task Pane will, by default, carry two directories: the etmain\maps directory, and your chosen scripts directory (if it is different than etmain\maps). You can now add or remove directories from the File Browser. Only directories carrying script files will be added.
The only ‘bug’ left is the weird contextmenu bug, where a different contextmenu was used for some reason. I have only seen this once and have not been able to reproduce it, so I’m hoping it was a one-off quirk…
I am still working on the readme, it’s a long write!
I will release a beta2 version very soon, probably tomorrow, containing a list of bug fixes and changes. I doubt the readme will be included (although I could always include a partially finished document? We’ll see…)