thanks to everyone who suggested solutions
to my problem.
The "send" solution associated to a mousedown /
mousemove works great (although I had to rewrite
parts of my scripts).
It's a shame it didn't cross my mind before I asked...
Thanks again.
JB
At 10:03 pm + 9/7/02, jbv wrote:
>Hi list,
>
>First I want to point out that I've read the archives
>and am aware of Scott's advice to not use a repeat
>loop inside a mousedown handler, but to use
>mousemove / mouserelease instead.
>
>However, I'm facing a problem for which using
>a repeat loo
Recently, "Scott Rossi" wrote:
> on doScroll
> if not the uAllowScroll of this stack then exit doScroll
> put item 1 of the uMLoc of this stack into x
> show img 1 at max(-633,min(1432,x - (trunc((x-400)/10,300
> send "doScroll" to me in 2 milliseconds
> end doScroll
Sorry, the "show im
Recently, "jbv" wrote:
> I'm facing a problem for which using
> a repeat loop inside a mousedown seems to be the
> only solution, and of course I met the problem of
> the mouseup event not being trapped by my script.
>... I can't use mousemove, since the image must
> keep scrolling even when th
I already tried that : problem was the same.
JB
I used
a procedure similar to this once but instead of:
repeat until the mouse
is up
I used:
repeat while the mouse
is down
I do not recall ever experiencing
a problem with it not stopping to scroll. You might try that just
to see if it
I used a procedure similar to this once but instead of:
repeat until the mouse is up
I used:
repeat while the mouse is down
I do not recall ever experiencing a problem with it not stopping to scroll. You might try that just to see if it makes a difference.
Philip Chumbley
Hi list,
F
On Tuesday, July 9, 2002, at 04:03 PM, jbv wrote:
> If anyone has a brilliant idea for a possible solution,
Just a wild idea. Use a send cycle (or both a send cycle and mouse
messages) to do the show. Start it with mouseDown and terminate it
with mouseUp.
Dar Scott
(A Rev guy lurking--most
Hi list,
First I want to point out that I've read the archives
and am aware of Scott's advice to not use a repeat
loop inside a mousedown handler, but to use
mousemove / mouserelease instead.
However, I'm facing a problem for which using
a repeat loop inside a mousedown seems to be the
only solu
On 9/6/01 5:44 pm, Scott Raney <[EMAIL PROTECTED]> wrote:
>> Using a repeat loop within a mouseDown handler is how I've done this for
>> years, and how RunRev does a lot of its stuff as well.
>
> Jeez, I hope you're wrong about that. This technique is just poor and
> no advanced scripter should
Scott Raney wrote:
> This technique is just poor and no advanced scripter should even be
> tempted to use it. And with the mouseMove message, there's never
> any need to. Using "repeat until will *never* be as smooth
> or reliable as doing it the right way, using messages.
If you want to see
> A common task in xTalks involves dragging objects with the mouse.
> In many cases the grab command works great for this, but for objects
> like pane dividers you need some custom scripting to handle it.
Actually I've found that "grab" is seldom useful for this kind of
thing because you can't do
>A common task in xTalks involves dragging objects with the mouse. In many
>cases the grab command works great for this, but for objects like pane
>dividers you need some custom scripting to handle it.
>
>The problem I'm having is that I'm seeing sporadic cases of the mouse not
>releasing control
Hi Richard
> I've considered restructuring the handler to use mouseMove for the stuff
> that's currently within the repeat loop, for for presumably the
> same reasons
> as the RunRev folks this is not often a workable solution in cases like
> dragging a separator bar.
>
I use mouseMove for all t
A common task in xTalks involves dragging objects with the mouse. In many
cases the grab command works great for this, but for objects like pane
dividers you need some custom scripting to handle it.
The problem I'm having is that I'm seeing sporadic cases of the mouse not
releasing control of t
14 matches
Mail list logo
