Agreed, and I have done exactly that in my mouseUp handler.
Pete Haworth
On Feb 1, 2011, at 11:54 AM, Richard Gaskin wrote:
> The comfort level that matters most is that of the end-user. :)
>
> Instead of "wait 15" you could use the doubleClickInterval, which is the
> number of milliseconds th
DunbarX wrote:
I think a note is definitely called for. I would test the
doubleclickinterval just a little more, but I have never found it to help at
all.
Given how rare it is that a UI will use both messages in a single
control, the doubleClickInterval is equally uncommonly used.
But the
I will toss in my 2 cents as I am wont to do. We had a problem with our
accounting app throwing errors something to the effect that a modal window had
to be closed before another could be opened.
This stymied the tech support who could not figure out what the heck was
happening. It was not rep
On 2/1/11 1:04 PM, dunb...@aol.com wrote:
Richard.
I disagree. It seems that those two click options in a single button is a
compact and natural way to get increased functionality. The actual work that
either operation might perform could be anything.
I use this all the time. Maybe It is just m
I've just come across another inconsistency with this. The QC asked me to
supply a stack to demonstrated the problem so I put together a simple stack and
substack for them that mimics the stacks that caused the problem, but the
defaultstack is set correctly! I'm still working on it because wh
I think a note is definitely called for. I would test the
doubleclickinterval just a little more, but I have never found it to help at
all.
Craig Newman
In a message dated 2/1/11 2:04:08 PM, p...@mollysrevenge.com writes:
> I did see the doubleclickinterval in the dictionary but preferred not
Richard.
I disagree. It seems that those two click options in a single button is a
compact and natural way to get increased functionality. The actual work that
either operation might perform could be anything.
I use this all the time. Maybe It is just my way...
Craig
In a message dated 2/1/11
I'm not entirely happy with using double click for the user interface either -
I may switch to a button or something as you suggest.
I do think this is either software or a documentation bug though. I know it's
unusual to have mouseUp and mouseDoubleup for the same control but there's
nothing
On 2/1/11 11:10 AM, Peter Haworth wrote:
destroyStack is false. Sounds feasible but doesn't explain why the
problem only occurs when I dynamically add new controls to the modal
dialog and change its height.
I'm about to submit a bug report for this.
The act of manually manipulating controls w
Peter Haworth wrote:
> On Feb 1, 2011, at 6:55 AM, DunbarX at aol.com wrote:
>
>> I have always had this problem, that the engine will not distinguish
>> the two "ups" if they are in the same handler.
>>
>> I use the old HC method:
>>
>> on mouseUp
>> wait 15 --your comfort level
>> if the mo
destroyStack is false. Sounds feasible but doesn't explain why the problem
only occurs when I dynamically add new controls to the modal dialog and change
its height.
I'm about to submit a bug report for this.
Pete Haworth
http://www.mollysrevenge.com
http://www.sonicbids.com/MollysReven
Hmmm... does the modal stack have the destroystack property set to true? I
wonder if not doing so leaves it in memory and it remains the default stack?
Just guessing...
Bob
On Jan 31, 2011, at 11:36 PM, Peter Haworth wrote:
> I still have no idea why this is happening but I have fixed it by s
Thanks. mouseUp is passed right now.
Pete Haworth
On Feb 1, 2011, at 8:16 AM, Jim Lambert wrote:
> You might also try comparing the effect on your mouseDoubleUp of passing the
> mouseup vs. not passing the mouseup.
>
> Jim Lambert
> ___
> use-liveco
You might also try comparing the effect on your mouseDoubleUp of passing the
mouseup vs. not passing the mouseup.
Jim Lambert
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your sub
Thanks Craig, I'll give that a try. Sounds like a bug in LC.
Pete Haworth
On Feb 1, 2011, at 6:55 AM, dunb...@aol.com wrote:
> I have always had this problem, that the engine will not distinguish the
> two "ups" if they are in the same handler.
>
> I use the old HC method:
>
> on mouseUp
>
The single mouse click invokes the modal dialog that was the subject of my
defaultStack problems. The double click basically undoes the what the modal
dialog logic did.
Pete Haworth
http://www.mollysrevenge.com
http://www.sonicbids.com/MollysRevenge
http://www.myspace.com/mollysrevengeba
> on mouseUp
> wait 15 --your comfort level
> if the mouseCllick then doDoubleStuff
> else doSingleStuff
> end mouseUp
>
> You can do triples and more this way.
Ooh nifty... tho i never had problems with both mouseUp and mouseDoubleUp...
only that mouseDoubleUp tends to trigger once, whe
I have always had this problem, that the engine will not distinguish the
two "ups" if they are in the same handler.
I use the old HC method:
on mouseUp
wait 15 --your comfort level
if the mouseCllick then doDoubleStuff
else doSingleStuff
end mouseUp
You can do triples and more this way
Peter Haworth wrote:
> I'm now chasing down another problem. I have a mouseUp and a
> mouseDoubleUp handler for the same control.
> When I double click, the mouseUp handler is triggered, not the
> mouseDoubleUp. How do suppress the mouseUp processing in favour
> of the mouseDoubleUp?
What do y
I still have no idea why this is happening but I have fixed it by setting the
defaultStack to the topStack immediately on return form the modal dialog.
I'm now chasing down another problem. I have a mouseUp and a mouseDoubleUp
handler for the same control. When I double click, the mouseUp hand
20 matches
Mail list logo
