Update on defaultStack problem
bobs at twft.com
Tue Feb 1 14:40:00 EST 2011
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 reproducible easily, as it only happened once in a great while.
Finally I got ahold of a wise and savvy tech support person who asked, "Is the user double clicking the link?" I asked the user, and they replied in the affirmative! It seems that if you could double click at just exactly the right speed, the parent app, not seeing that the first instance was running, tried to launch a second instance with the second click, which the code normally forbid. But since the second click came so fast, the parent app didn't have time to create the first instance yet so it proceeded merrily on it's way.
The moral to the story? Stick to the interface guidelines. :-)
On Feb 1, 2011, at 11:18 AM, J. Landman Gay wrote:
> On 2/1/11 1:04 PM, DunbarX at aol.com wrote:
>> 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...
> I don't know of any HIG that officially supports double-clicking a button. In fact, it's common to put in scripts explicitly blocking double-clicks from doing anything.
> Jacqueline Landman Gay | jacque at hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode