2019-04-24, 04:48 PM
Hello, I have two new suggestions (for when the times open.mp client will be made).
1. Fast Testing
Please, make that after compiling the new script, you can quickly test?it without a GMX or reloadfs. This could create some problems in some scenarios where a restart is necessary?of course, but in many cases it will just speed the workflow up (for example when dealing with text draws).
2. Debugging
Allow breakpoints, pausing, changing the instruction pointer's position?and reading/writing variables?at runtime (without pausing the multiplayer sync). Also it would be cool to integrate in the compiler a tool that generates sort of .pdb files, which would give you line numbers and positions when a runtime error occurs.
Thanks.
1. Fast Testing
Please, make that after compiling the new script, you can quickly test?it without a GMX or reloadfs. This could create some problems in some scenarios where a restart is necessary?of course, but in many cases it will just speed the workflow up (for example when dealing with text draws).
2. Debugging
Allow breakpoints, pausing, changing the instruction pointer's position?and reading/writing variables?at runtime (without pausing the multiplayer sync). Also it would be cool to integrate in the compiler a tool that generates sort of .pdb files, which would give you line numbers and positions when a runtime error occurs.
Thanks.