Bug? Macro.do nothing

unitedafterall · **Thanked:** 0 time(s) **Posted:** Sun Dec 14, 2014 4:45 am

Somehow this gets inserted into my script. Once it happens, if I remove it from design view, then copy\paste my code into a new macro, it stays gone. If I try to remove it from within the original macro, it just re-inserts itself when I switch back and fourth from code to design view. When I remove it, it removes an evaluating statement that follows it (if, while, when, etc...).

Syrifina · **Thanked:** 0 time(s) **Posted:** Sun Dec 14, 2014 7:34 am

Post the code; I think I know what it is.

unitedafterall · **Thanked:** 0 time(s) **Posted:** Sun Dec 14, 2014 7:48 am

Syrifina wrote:

Post the code; I think I know what it is.

I'll see if I still have a copy somewhere. For now, that laptop is closed for the next few weeks because I'm moving. If it's not too far packed I'll dig it out. What are you thinking it is?

Syrifina · **Thanked:** 0 time(s) **Posted:** Sun Dec 14, 2014 8:09 am

In Design View, if you click on an instruction BEM expects something to happen after that...if you click on another instruction, it has to fill in those gaps so it will insert "macro.do nothing". It basically has to do something and in this case "nothing" is something.

By reading the code I would be able to tell if this is what your describing or if it's something else that we could possibly duplicate and fix as a bug.

unitedafterall · **Thanked:** 0 time(s) **Posted:** Sun Dec 14, 2014 8:52 am

I was able to recreate by writing this bit...

Code:

 while  Mouse.Button is pressed("Left")
          and
          Color.At coordinate is (RGB)("255", "255", "255", "1198", "827")
          begin
               when  Color.At coordinate is (RGB)("156", "242", "80", "{Xpixel}", "{Ypixel}")
                    begin
                         Mouse.Click("Left")
                         Macro.Pause("8000")
                    end
          end

I am guessing it's caused because I have another conditional statement after a "begin"?

Syrifina · **Thanked:** 0 time(s) **Posted:** Sun Dec 14, 2014 8:59 am

Yes, that's correct.

unitedafterall · **Thanked:** 0 time(s) **Posted:** Sun Dec 14, 2014 10:13 am

Syrifina wrote:

Yes, that's correct.

Maybe it would be best to move this to feature request. Perhaps the code that is causing a macro.no nothing to be inserted should be flagged or warn the user. It can throw you a big curveball and waste your time if you don't use the design view. Drove me crazy because I couldn't figure out why my macro was .doing nothing :lol:

Blue Eye Macro

Bug? Macro.do nothing