mouseUp

Typemessage
DictionaryLCS
LibraryLiveCode Script
Syntax
mouseUp <pButtonNumber>
Associationsstack, card, field, button, graphic, scrollbar, player, image
Summary

Sent when the user releases the mouse button.

Introduced1.0
OSmac, windows, linux, ios, android, web
Platformsdesktop, server, mobile
Parameters
NameTypeDescription
pButtonNumber

Specifies which mouse button was pressed:

"1": the left button on systems with a multi-button mouse and the mouse button on Mac OS systems with a single-button mouse.
"2": the middle button on systems with a three-button mouse.
"3": the right button on systems with a multi-button mouse and Control-click on Mac OS systems with a single-button mouse.
Example
on mouseUp
  answer "You clicked" && the name of the target
end mouseUp
# checking the right button
on mouseUp pBtnNum
  if pBtnNum is 3 then
    answer "You used the right button."
  end if
end mouseUp
RelatedKeyword: control
Property: script
Message: mouseStillDown, mouseDoubleUp, mouseRelease, mouseUpInBackdrop
Command: click
Function: mouseClick
Glossary: field, handler, mouse button, Browse tool, message, message path, unlock, card, pixel, mouse pointer, image, object, double-click
Description

Handle the mouseUp message to perform an action when the user releases the mouse button after clicking.

The mouseUp message is sent to the control that was clicked, or to the card if no control was under the mouse pointer.

Note: If the user clicks a transparent pixel in an image, the mouseUp message is sent to the object behind the image, not to the image.

The mouseUp message is sent only when the Browse tool is being used. If an unlocked field is clicked with mouse button 1 or 2, no mouseUp message is sent.

If the mouse has moved outside the control that was originally clicked before the user releases the mouse button, the mouseRelease message is sent instead of mouseUp. If the click is the second click of a double-click, the mouseDoubleUp message is sent instead of mouseUp.

Tip: If the user clicks several times in rapid succession (for example, if the user clicks an "Increase" button that increases a number by 1), some of the clicks may send a mouseDoubleUp message instead of mouseUp. If your script only handles the mouseUp message, these accidental double-clicks will be lost. One way to prevent this is to install a handler in an object that's further in the message path, to re-send double-click|double-clicks:

on mouseDoubleUp
  if "on mouseUp" is in the script of the target and \
     "on mouseDoubleUp" is not in the script of the target then
   send "mouseUp" to the target
  end if
end mouseDoubleUp

If the user double-clicks an object whose script contains a mouseUp handler but no mouseDoubleUp, the above handler will automatically send a mouseUp to the object so the second click can be handled normally (instead of as a double-click).

Tagsui