Features to comment out and uncomment the RMMV event commands

[Alexandr_7]

Features to comment out and uncomment the RMMV event commands

• Add the item "comment out" the selected event commands to the menu.
• Add the menu item "uncomment" the selected event commands.

This feature is great because of the following:

• Sometimes there is a case where you need to comment out a piece of code and not delete it. In any programming language there is such an opportunity. In RMMV, the script is written with the help of event commands and this can not be done. And if you need to comment out the script, you either need to delete the commands and then reinstall them or use the GOTO tags that are not effective.
  Spoiler: RUS

  Иногда бывают случае когда нужно закомментировать кусок кода а не удалять его. В любых языках программирования есть такая возможность. В RMMV скрипт пишется с помощью комманд событий и этого сделать нельзя. А если надо закомментировать скрипт то либо нужно удалять команды а потом заново их ставить либо использховать метки GOTO что не эфективо.

 

[Alexandr_7]

Maybe someone will say what is wrong or I do not understand why until now on the test by the moderator?

 

[mlogan]

Threads in this section can only be approved/disapproved by Archeia. As she is very busy, it can sometimes take a while for her to have a chance to look at them. Please be patient.

 

[Blue001]

If you mean "Disable" a section of code in an events "contents", the same way you can turn Plugins on and off temporarily to test things then I like this idea. You can do this in StarCraft 1 and 2's trigger editors, and along with THIS SUGGESTION would really improve event creation and testing.

I grabbed a random image from the internet that shows the "disabled" code sections in SC2s triggers (the ones on the right with an x) as a mockup for what Alexandr_7 means.

The code in red is off but still there while this person tests the one not in red, so you can keep it there and not have to remake it after your test if you discover you do actually need it after all.

 

[Alexandr_7]

If you mean "Disable" a section of code in an events "contents", the same way you can turn Plugins on and off temporarily to test things then I like this idea. You can do this in StarCraft 1 and 2's trigger editors, and along with THIS SUGGESTION would really improve event creation and testing.

I grabbed a random image from the internet that shows the "disabled" code sections in SC2s triggers (the ones on the right with an x) as a mockup for what Alexandr_7 means.

The code in red is off but still there while this person tests the one not in red, so you can keep it there and not have to remake it after your test if you discover you do actually need it after all.

Could be so. But I expected to add 2 buttons.
1. "Comment out" or "Disable commands"
2. "Uncomment" or "Enable commands"

When you click on "comment out", the commands are converted to comments or disabled by highlighting in red.
When you click on "uncomment" comments are converted again into commands or commands turn on highlighted in the usual color.

It does not matter how it will be implemented, the main thing is that the commands in the event that are for the developer a kind of code could be made inactive, but not deleting them.

 

[Meike]

This would be useful, but it's easy to work around. What I've done is I stuck the event commands I wanted 'commented out' in a conditional branch of "if self switch A is on" which then gets skipped because I never set self switch A to on.