Justin Clark-Casey (justincc) 25baa2d894 Avoid reporting false positives when a colon is in a comment in the first line of a script where the user was not trying to select a different script engine. ... This works by only posting the "Selected engine unavailable" message if we're falling back on XEngine and the language is one handled by XEngine. In cases where the language is not handled or not allowed, the user will still be notified by the later compiler error. This avoids the overwhelming majority of false positives where the first line contains a : for other reasons (e.g. source control systems, vim settings, etc.) Ultimately, I think it would be better to detect script language/engine with a mechanism that didn't just rely on : detection (e.g like #! in unix scripts).		2012-06-28 01:01:18 +01:00
..
Interfaces	Fix script "Running" behavior	2012-06-23 04:15:14 -04:00
Shared	Add stub for llCastRay	2012-06-26 15:15:25 -04:00
XEngine	Avoid reporting false positives when a colon is in a comment in the first line of a script where the user was not trying to select a different script engine.	2012-06-28 01:01:18 +01:00