Known issues

[jojorne]

Here are some known issues by me that I'll try to fix in the future:

• [ ] Start debug then close console. There is no other way to reopen it. The code expect that the console should never be closed to begin with while in debug mode.
• [x] "while/if (TRUE)": works on SL but not on editor. The code treats TRUE as "int" and not "integer", there is a difference here.
• [ ] "integer num;": not initializing a variable might cause trouble. The code never initialize the variable nor reinitializes it while SL does.
• [ ] The new feature, LSLI, does not obey the editor TAB format rules. The problem here is that it relies on "\t" for indentation.
• [ ] Output format has wrong naming convention in code and UI. UI doesn't show unknown encoding. Like "UTF8" instead of "UTF-8" and "UTF-16 L/BE" instead of commonly used "Unicode (Big Endian)", etc.
• [ ] Save docked control position, like the Solution Explorer position.
• [ ] Update does not work for the help file.
• [ ] Missing new LSL features like constants and methods.

[jojorne]

1. I'm trying to embed the console to the form, this should satisfy the code needs.
2. I'm testing if changing from "int" to "integer" will cause a bug. Also should I change all the "int" or just for special cases? Note: "int" is how the editor understand the lsl's "integer" at the end and so, feeding "int" too soon is causing trouble for the editor to translate LSL.
3. I'm currently studying the code for a fix.
4. idk, I'm currently studying the code... I would like something like Firestorm's Preprocessor.
5. Currently the code loads OS default encoding for script and does not show it to you, actually it just uncheck all output format options.
6. I'm currently studying the code for a fix.
7. The update simply stops after checking the editor version match.
8. What is missing? I'm kidding... No, serious, it's missing stuff but what? It's all that!? omg...

[niel]

2- Do special cases for now. We'll look into the rest another time. 5- Yeah, that's always bugged me. We should force to UTF-8 if no other is detected. 6- uh huh... Nothing has been updated in several years, since I stopped using Windows, so I expect there is a lot missing.

[jojorne]

2. Fixed for TRUE and FALSE only.