[feature request] option for manual compilation instead of on-change compilation

[gdeOo]

When scripts start getting a bit large, or when some individual triggers are large, the automatic compilation performed by RATools when the script changes starts to become a nuisance, blocking the UI for a very noticeable interval of time.

Another situation I've run into is bugs that result in exception-related message boxes being hard to fix, because changes to the script that dont remove the bug-triggering code result in the message box showing up again. I usually end up copying the code into another editor to fix it before copying it back into RATools.

I'd prefer having the option to compile the script manually, preferably with an associated keyboard shortcut.

[Jamiras]

Eliminating the compilation will only cut the processing time in half (at best). Parsing (of the entire document) is performed for the syntax highlighting after every modification as well.

It would be hugely beneficial to only re-parse/re-highlight/re-compile the parts of the code around where the modifications occur, but determining what may or may not depend on any particular piece of code is not an easy task.

This logic is supposed to be occurring on a background thread, and can be interrupted if more modifications occur while it is occurring. When it completes, it raises PropertyChanged events to notify the UI to update via WPF databinding. I'm curious where the "blocking of the UI" is actually happening.

I'm fine with the idea of making compiling (and therefore error reporting) a manual process, but I don't know that it will have as much of an impact as you would expect due to the current syntax highlighting implementation.

[MagmarFire]

It would be hugely beneficial to only re-parse/re-highlight/re-compile the parts of the code around where the modifications occur, but determining what may or may not depend on any particular piece of code is not an easy task.

Would this potentially be worked around by supporting a project structure where scripts are split between multiple, smaller files, a la Visual Studio? That way, reparsing would only ever have to be done within files that had actually changed. There'd be no need to calculate what parts of the code within a file had changed.