Yeah, even though the warnings don't create problems, the order of the bangs is still wrong. It should always be, for example, [!CommandMeasure ... "Stop 1"][!CommandMeasure ... "Stop 2"][!CommandMeasure ... "Execute ..."]. In other words, stop all actions before executing an action. Right now, only some actions are stopped, and that is incorrectly done after executing an action, instead of correctly done before executing the said action.Yes, however those warning (not error) messages don't create other problems, excepting that they are visible in the log.
I noticed another error in code: the !CommandMeasure bang used into the LeftMouseUpAction option of the [Textfield] meter has one single parameter, even if it was assumed it must have two. This is the option: LeftMouseUpAction=[!CommandMeasure "InputText ExecuteBatch 1"]. In this case since InputText and ExecuteBatch 1 have been included into one single pair of quotes, they are considered being one single parameter, this is why I got a related error message. The correct form of this option is: LeftMouseUpAction=[!CommandMeasure "InputText" "ExecuteBatch 1"]. This way there will be two parameters: InputText and ExecuteBatch 1.
Indeed, I noticed that quote issue too and corrected it, but the code is still too chaotic for my taste and does not do what I suppose it should do (e.g. after entering something in the input field, slide a Google page where that something is looked for). Must format the code to "standard" before I can work with it, now it just hurts my eyes, lol. Just joking, but gotta clean and order the measures before meters first...
Statistics: Posted by Yincognito — Yesterday, 8:26 pm
