Recently, Ken Norris (dialup) wrote:
>> on mouseRelease
>> mouseUp
>> end mouseRelease
> --
> Is this some kind of backup redundancy for PC's? As far as I know, the
> mouseUp message gets sent automatically when you release the mouse, and
> doesn't need a separate handler.
You need this
on 2/23/02 12:47 PM, Scott Rossi at [EMAIL PROTECTED] wrote:
> If I understand your request, this is one way you could do the above. Make
> 3 small graphics named box 1, box 2 and box 3 within the region you define.
> Then place the following script in your oval:
>
> on mouseDown
> set the uAll
Recently, Ken Norris (dialup) wrote:
>> If you have a specific need that seems to require "repeat while the mouse is
>> down," post it and we'll see if we can figure a way around it.
>>
> --
> Not exactly, but, how about this:
>
> on mousestilldown
> put max(81,min(557,the mouseh)) into
on 2/20/02 10:47 PM, Geoff Canyon at [EMAIL PROTECTED] wrote:
> If you have a specific need that seems to require "repeat while the mouse is
> down," post it and we'll see if we can figure a way around it.
>
--
Not exactly, but, how about this:
on mousestilldown
put max(81,min(557,the
On 22/2/02 12:07 am, "Scott Rossi" <[EMAIL PROTECTED]> scribed:
> On Thursday, February 21, 2002, at 03:27 PM, Ken Norris (dialup) wrote:
>
Doesn't "grab" do what you want? I think it suspends other messages
while
the user is dragging and automatically exits when the user lets go
>
-Original Message-
From: Scott Rossi [mailto:[EMAIL PROTECTED]]
Sent: Friday, 22 February 2002 11:07 AM
To: [EMAIL PROTECTED]
Subject: Re: Polling the mouse state
On Thursday, February 21, 2002, at 03:27 PM, Ken Norris (dialup) wrote:
>>> Doesn't "grab"
On Thursday, February 21, 2002, at 03:27 PM, Ken Norris (dialup) wrote:
>>> Doesn't "grab" do what you want? I think it suspends other messages
>>> while
>>> the user is dragging and automatically exits when the user lets go of
>>> the
>>> mouse button.
>>
>> No, drag doesn't let me check whe
on 2/21/02 12:10 PM, Ian Summerfield at [EMAIL PROTECTED] wrote:
> On 21/2/02 4:24 pm, "Jacqueline Landman Gay" <[EMAIL PROTECTED]> scribed:
>
>>
>> Doesn't "grab" do what you want? I think it suspends other messages while
>> the user is dragging and automatically exits when the user lets go of
Jacqueline Landman Gay writes:
> Doesn't "grab" do what you want? I think it suspends other messages while
> the user is dragging and automatically exits when the user lets go of the
> mouse button.
The grab command could give me everything I need for 90% of the times I need
such a thing, if onl
On 21/2/02 4:24 pm, "Jacqueline Landman Gay" <[EMAIL PROTECTED]> scribed:
>
> Doesn't "grab" do what you want? I think it suspends other messages while
> the user is dragging and automatically exits when the user lets go of the
> mouse button.
No, drag doesn't let me check whether the object ha
> At 4:37 AM + 2/21/02, Ian Summerfield wrote:
>> Using the mousemove is no good. I want to suspect all the messages from
>> happening while I'm dragging a pin around on my timer plug. With
>> mousemove
>> I'm effectively dropping back to an "idle" state between each call, I
>> need
>>
on 2/20/02 6:50 AM, Jim Hurley at [EMAIL PROTECTED] wrote:
> This issue of polling the mouse state continues to crop up. I have
> had to avoid the use of the old HyperCard standby:
>
> "repeat while the mouse is down"
--
I love "repeat while the mouse is do
On 20/2/02 2:50 pm, "Jim Hurley" <[EMAIL PROTECTED]> scribed:
> Hi Ian,
>>
>>> I don't like the grab command, it seems to me program flow doesn't
>>> stop,
>>> i.e.
>>
>> maybe you missed some of the previous posts, where experts (!) are
>> advising to
>> not poll the mouse-state.
>>
>> It
ck if the mouseloc is
>> within the bounds of another object, and if so hilite that object, etc.
>> It's much more flexible.
>> ...
>
>maybe you missed some of the previous posts, where experts (!) are
>advising to
>not poll the mouse-state.
>
>It is far m
14 matches
Mail list logo
