send "end mouseUp"

[richmond62]

I wonder why this code:

Code: Select all

if intersect(grc "bug", image "path", 2) then
                  move grc "bug" to 70, 630
                  --send "end switch"
                  send "exit mouseUp"
               end if

throws a bluey.

[Klaus]

Maybe because LC thinks this does not make much sense?

If this snippet is part of a "mouseup" handler, then a simple "exit mouseup" will suffice, no need to SEND anything.
If not, please post the complete handler.

[SWEdeAndy]

Indeed! "Send" is a command and needs a handler name as argument. "exit mouseUp" is not, an can never be, a handler name.

[richmond62]

Thank you very much for your help.

[dunbarx]

Richmond.

I am not sure if this helps or not but if you had this in a button script

Code: Select all

on mouseUp
   beep 3
   send "exitMouseUp" && "5" to this cd
end mouseUp

:
and this in the card script:

Code: Select all

on exitMouseUp var
   answer var
end exitMouseUp

The real difference is that the message "sendMouseup" is ONE word, as all message names must be. The only method, and likely the only reason to send more than one word is in the example, that is, appending a parameter to the message.

Craig

[richmond62]

Humpf . . .

This throws a bluey:

Code: Select all

 if ctrlKey() is down then
      put numToCodePoint(122933) after fld "OOT"
      end mouseUp
   end if
   if altKey() is down then
      put numToCodePoint(11767) after fld "OOT"
   else
      if shiftkey() is up then
         put numToCodePoint(1077) after fld "OOT"
      else
         if shiftkey() is down then
            put numToCodePoint(MAGIC) after fld "OOT"
         end if
      end if
   end if

Where I have 'end mouseUp' (which throws the bluey) I should like to, erm, exit the mouseUp script . . .

[richmond62]

OK, OK, just for a change answering my own query:

exit mouseUp

[Klaus]

Nope, I already answered that about two weeks ago, see my first answer here!