Dont put "cancel wait events" in RM rules that do not have a "wait"!
Was a habit.
Now a hinderance, as the firmware has evolved.
Had some strange issues with partially firing/running.
Remove,works much more dependably.
Live and learn, just a note to self.
Note to Self:
In Visual Basic 6 don't code: "On Error Resume Next"....
As I worked for the Federal government I wasn't allowed to install software, even if I wrote it. (And, of course, as a Fed employee I had to pass a basic security background. In fact, a retired FBI guy not only interviewed me, but also some of my neighbors).
So I had to use VBA. Sometimes they didn't have a call like if something existed or not. So I would write a function that would try to use what I wanted to test if it existed or not. If it existed it would return True, if not it returned False. Not exactly the same, but similar.
There were a couple of bugs I stumbled upon that would cause an error and in my error trapping I would have to put in that if the error # was one of those to Resume Next. Didn't happen a lot, but was definitely useful a few times.
Don't put a command to delete all files and subdirectories starting from the current directory anywhere in your code. Because someone will miss something important that causes it to be unintentionally called from the Windows Documents folder.
Yes, that would be bad.
...or better still, called from the root directory.
I'm not sure you understand that expression...
Reminds me of years ago, warning people against putting "." in their Unix path (or, worse yet, putting it first). To illustrate this to some people who didn't believe me, I put an "ls" command in my home directory that essentially echoed "\rm -rf ~/." to the screen, waited a while, then said something about them being stupid or something.
So much fun.
My example was unfortunately a true story - our SW team shipped a release w/that wonderful "option" included. Was not a good time at work for them (or anyone, really) that week...