Re: set cursor to busy
Mike Kerner MikeKerner@... writes: In case you didn't understand, the way you get the busy cursor (beachball) to animate is to set it. Each time you set it, it moves. Thus repeat 100 times set the cursor to busy end repeat You can rotate it or not rotate it as much as you want. Right. That's why I don't get all the sturm und drang. If you want to animate it, you do it explicitly. It doesn't steal cycles. -- Mark Wieder mwie...@ahsoftware.net ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: set cursor to busy
William, In case you didn't understand, the way you get the busy cursor (beachball) to animate is to set it. Each time you set it, it moves. Thus repeat 100 times set the cursor to busy end repeat You can rotate it or not rotate it as much as you want. On Wed, Oct 9, 2013 at 3:50 PM, Richard Gaskin ambassa...@fourthworld.comwrote: william humphrey wrote: I always wished that there was some LiveCode example stacks which showed proper design and procedure for different platforms. FWIW, the Human Interface Guidelines for most popular platforms are linked to in the right-hand column on this page: http://www.fourthworld.com/**resources/http://www.fourthworld.com/resources/ -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web __**__** ambassa...@fourthworld.comhttp://www.FourthWorld.com __**_ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/**mailman/listinfo/use-livecodehttp://lists.runrev.com/mailman/listinfo/use-livecode -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, This is good. ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: set cursor to busy
Setting the cursor to busy eats cycles and adds a time-overhead. Personal preference is to simply 'set the cursor to watch' for any actity lasting up to a few seconds, or a progress bar updated every nth iteration (such as n mod 100 =0) for longer routines. For indeterminate activity length, I use an animated gif such as a barber's pole. Short answer is I haven't used 'busy' in a long time. 2p/2c Hugh Senior FLCo ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: set cursor to busy
Can you explain what is different between setting cursor to busy instead of setting cursor to watch? Why does setting cursor to bust eat cycles? This is now a second reason not to use setting cursor to busy. The first being that it tells the user something is seriously wrong (I didn't know this one). I assume that seeing the watch just means wait a moment something is going on that is supposed to take time. (I see the watch cursor all the time when I run windows stuff). Brevity and errors in this email probably the result of being sent by a mobile device. On Oct 9, 2013, at 2:50 AM, FlexibleLearning.com ad...@flexiblelearning.com wrote: Setting the cursor to busy eats cycles and adds a time-overhead. Personal preference is to simply 'set the cursor to watch' for any actity lasting up to a few seconds, or a progress bar updated every nth iteration (such as n mod 100 =0) for longer routines. For indeterminate activity length, I use an animated gif such as a barber's pole. Short answer is I haven't used 'busy' in a long time. 2p/2c Hugh Senior FLCo ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: set cursor to busy
I probably added to the confusion here, so I'll try to explain again. The *colored* beachball cursor (drawn by OS X) is the one that means an app is not responding. This is different than the black and white busy cursor that you can use in LiveCode, which can be used to indicate an application is, well, busy doing something. The colored cursor is the one you want to avoid. The difference between the LiveCode watch and busy cursors is the busy cursor has multiple frames which advance each time you set the cursor. See cursor in the dictionary. Hope this clears things up. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 10/9/13 3:27 AM, William Humphrey shoreag...@gmail.com wrote: Can you explain what is different between setting cursor to busy instead of setting cursor to watch? Why does setting cursor to bust eat cycles? This is now a second reason not to use setting cursor to busy. The first being that it tells the user something is seriously wrong (I didn't know this one). I assume that seeing the watch just means wait a moment something is going on that is supposed to take time. (I see the watch cursor all the time when I run windows stuff). Brevity and errors in this email probably the result of being sent by a mobile device. On Oct 9, 2013, at 2:50 AM, FlexibleLearning.com ad...@flexiblelearning.com wrote: Setting the cursor to busy eats cycles and adds a time-overhead. Personal preference is to simply 'set the cursor to watch' for any actity lasting up to a few seconds, or a progress bar updated every nth iteration (such as n mod 100 =0) for longer routines. For indeterminate activity length, I use an animated gif such as a barber's pole. Short answer is I haven't used 'busy' in a long time. 2p/2c Hugh Senior FLCo ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: set cursor to busy
Thanks Scott. that helps. On a Window's platform does set cursor to busy look like a spinning watch or is it still a MacOS 8 beach ball? On Wed, Oct 9, 2013 at 7:25 AM, Scott Rossi sc...@tactilemedia.com wrote: I probably added to the confusion here, so I'll try to explain again. The *colored* beachball cursor (drawn by OS X) is the one that means an app is not responding. This is different than the black and white busy cursor that you can use in LiveCode, which can be used to indicate an application is, well, busy doing something. The colored cursor is the one you want to avoid. The difference between the LiveCode watch and busy cursors is the busy cursor has multiple frames which advance each time you set the cursor. See cursor in the dictionary. Hope this clears things up. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 10/9/13 3:27 AM, William Humphrey shoreag...@gmail.com wrote: Can you explain what is different between setting cursor to busy instead of setting cursor to watch? Why does setting cursor to bust eat cycles? This is now a second reason not to use setting cursor to busy. The first being that it tells the user something is seriously wrong (I didn't know this one). I assume that seeing the watch just means wait a moment something is going on that is supposed to take time. (I see the watch cursor all the time when I run windows stuff). Brevity and errors in this email probably the result of being sent by a mobile device. On Oct 9, 2013, at 2:50 AM, FlexibleLearning.com ad...@flexiblelearning.com wrote: Setting the cursor to busy eats cycles and adds a time-overhead. Personal preference is to simply 'set the cursor to watch' for any actity lasting up to a few seconds, or a progress bar updated every nth iteration (such as n mod 100 =0) for longer routines. For indeterminate activity length, I use an animated gif such as a barber's pole. Short answer is I haven't used 'busy' in a long time. 2p/2c Hugh Senior FLCo ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode -- http://www.bluewatermaritime.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: set cursor to busy
On 10/9/13 8:45 AM, william humphrey wrote: Thanks Scott. that helps. On a Window's platform does set cursor to busy look like a spinning watch or is it still a MacOS 8 beach ball? It's the Windows hourglass. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: set cursor to busy
The 'busy' cursor is a BLACK AND WHITE spinning beachball and part of LiveCode so it is cross platform. It is hungry and eats cycles because it has to re-draw every time it changes. The COLORED spinning beachball on a Mac means the app is hanging (i.e. not a good thing). Do not use this cursor on ANY platform. The 'watch' cursor displays from OS system resources I believe, so is platform specific. It looks like a watch on a Mac and an egg-timer on Windows. It eats virtually nothing. Point is, don't use an icon that means the wrong thing. As Scott said, use the documentation (sometimes called RTFM), make sure you know your delivery platform, and Google is your friend. My suggestion stands. Use the watch cursor for short processes; use a progress bar updated every nth iteration for lengthy processes. If you really want to show a change in the cursor for EVERY repeat iteration, use the black and white 'busy' beachball cursor, but be aware that it will slow your routine down. Hope this helps. Hugh Senior FLCo william humphrey wrote: Thanks Scott. that helps. On a Window's platform does set cursor to busy look like a spinning watch or is it still a MacOS 8 beach ball? On Wed, Oct 9, 2013 at 7:25 AM, Scott Rossi sc...@tactilemedia.com wrote: I probably added to the confusion here, so I'll try to explain again. The *colored* beachball cursor (drawn by OS X) is the one that means an app is not responding. This is different than the black and white busy cursor that you can use in LiveCode, which can be used to indicate an application is, well, busy doing something. The colored cursor is the one you want to avoid. The difference between the LiveCode watch and busy cursors is the busy cursor has multiple frames which advance each time you set the cursor. See cursor in the dictionary. Hope this clears things up. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 10/9/13 3:27 AM, William Humphrey shoreag...@gmail.com wrote: Can you explain what is different between setting cursor to busy instead of setting cursor to watch? Why does setting cursor to bust eat cycles? This is now a second reason not to use setting cursor to busy. The first being that it tells the user something is seriously wrong (I didn't know this one). I assume that seeing the watch just means wait a moment something is going on that is supposed to take time. (I see the watch cursor all the time when I run windows stuff). Brevity and errors in this email probably the result of being sent by a mobile device. On Oct 9, 2013, at 2:50 AM, FlexibleLearning.com ad...@flexiblelearning.com wrote: Setting the cursor to busy eats cycles and adds a time-overhead. Personal preference is to simply 'set the cursor to watch' for any actity lasting up to a few seconds, or a progress bar updated every nth iteration (such as n mod 100 =0) for longer routines. For indeterminate activity length, I use an animated gif such as a barber's pole. Short answer is I haven't used 'busy' in a long time. 2p/2c Hugh Senior FLCo ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: set cursor to busy
Thanks Hugh I always wished that there was some LiveCode example stacks which showed proper design and procedure for different platforms. Like you said, a documentation so that people like me wouldn't be doing it wrong for years and years. And I use Parallels and run Windows lots of time so I thought that colored spinning beachball just meant I was running Windows. On Wed, Oct 9, 2013 at 3:08 PM, FlexibleLearning.com ad...@flexiblelearning.com wrote: The 'busy' cursor is a BLACK AND WHITE spinning beachball and part of LiveCode so it is cross platform. It is hungry and eats cycles because it has to re-draw every time it changes. The COLORED spinning beachball on a Mac means the app is hanging (i.e. not a good thing). Do not use this cursor on ANY platform. The 'watch' cursor displays from OS system resources I believe, so is platform specific. It looks like a watch on a Mac and an egg-timer on Windows. It eats virtually nothing. Point is, don't use an icon that means the wrong thing. As Scott said, use the documentation (sometimes called RTFM), make sure you know your delivery platform, and Google is your friend. My suggestion stands. Use the watch cursor for short processes; use a progress bar updated every nth iteration for lengthy processes. If you really want to show a change in the cursor for EVERY repeat iteration, use the black and white 'busy' beachball cursor, but be aware that it will slow your routine down. Hope this helps. Hugh Senior FLCo william humphrey wrote: Thanks Scott. that helps. On a Window's platform does set cursor to busy look like a spinning watch or is it still a MacOS 8 beach ball? On Wed, Oct 9, 2013 at 7:25 AM, Scott Rossi sc...@tactilemedia.com wrote: I probably added to the confusion here, so I'll try to explain again. The *colored* beachball cursor (drawn by OS X) is the one that means an app is not responding. This is different than the black and white busy cursor that you can use in LiveCode, which can be used to indicate an application is, well, busy doing something. The colored cursor is the one you want to avoid. The difference between the LiveCode watch and busy cursors is the busy cursor has multiple frames which advance each time you set the cursor. See cursor in the dictionary. Hope this clears things up. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 10/9/13 3:27 AM, William Humphrey shoreag...@gmail.com wrote: Can you explain what is different between setting cursor to busy instead of setting cursor to watch? Why does setting cursor to bust eat cycles? This is now a second reason not to use setting cursor to busy. The first being that it tells the user something is seriously wrong (I didn't know this one). I assume that seeing the watch just means wait a moment something is going on that is supposed to take time. (I see the watch cursor all the time when I run windows stuff). Brevity and errors in this email probably the result of being sent by a mobile device. On Oct 9, 2013, at 2:50 AM, FlexibleLearning.com ad...@flexiblelearning.com wrote: Setting the cursor to busy eats cycles and adds a time-overhead. Personal preference is to simply 'set the cursor to watch' for any actity lasting up to a few seconds, or a progress bar updated every nth iteration (such as n mod 100 =0) for longer routines. For indeterminate activity length, I use an animated gif such as a barber's pole. Short answer is I haven't used 'busy' in a long time. 2p/2c Hugh Senior FLCo ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode -- http://www.bluewatermaritime.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: set cursor to busy
william humphrey wrote: I always wished that there was some LiveCode example stacks which showed proper design and procedure for different platforms. FWIW, the Human Interface Guidelines for most popular platforms are linked to in the right-hand column on this page: http://www.fourthworld.com/resources/ -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.comhttp://www.FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: set cursor to busy
Hi. If you think your users are skittish that way, why not roll your own? A handful of small images that cycle around? Craig Newman -Original Message- From: william humphrey b...@bluewatermaritime.com To: How to use LiveCode use-livecode@lists.runrev.com Sent: Tue, Oct 8, 2013 11:19 am Subject: set cursor to busy Well I've been wondering about this feature. I have set cursor to busy whenever something takes more than a second and I see that interesting vintage black and white beach ball. That is fine and really a feature because I'm in the LiveCode developing environment so when LiveCode crashes then I see the colourful system beach ball spin and I know that is different than something from my code. But what about when my code is in a stand-alone? Won't users be confused by that vintage beach ball? Is there another way to say set cursor to busy? Perhaps set new system cursor to busy or (for old one) set system 8 cursor to busy? Any ideas? -- http://www.bluewatermaritime.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: set cursor to busy
I was hoping for something that would call the system level busy and thus would work on all platforms. If I roll a pretty rainbow one which looks great on the present Mac OS it would fail on the different flavours of Windows and probably the next MacOS which very likely will feature a flat beach ball. On Tue, Oct 8, 2013 at 11:27 AM, dunb...@aol.com wrote: Hi. If you think your users are skittish that way, why not roll your own? A handful of small images that cycle around? Craig Newman -Original Message- From: william humphrey b...@bluewatermaritime.com To: How to use LiveCode use-livecode@lists.runrev.com Sent: Tue, Oct 8, 2013 11:19 am Subject: set cursor to busy Well I've been wondering about this feature. I have set cursor to busy whenever something takes more than a second and I see that interesting vintage black and white beach ball. That is fine and really a feature because I'm in the LiveCode developing environment so when LiveCode crashes then I see the colourful system beach ball spin and I know that is different than something from my code. But what about when my code is in a stand-alone? Won't users be confused by that vintage beach ball? Is there another way to say set cursor to busy? Perhaps set new system cursor to busy or (for old one) set system 8 cursor to busy? Any ideas? -- http://www.bluewatermaritime.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode -- http://www.bluewatermaritime.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: set cursor to busy
Just a suggestion: you might consider using your own custom busy indicator. This prevents you from having to match any particular OS/version. Just so you know, the beach ball on OS X is usually associated with non-responsive, so probably not the right message to send to your users when things are working but busy. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 10/8/13 10:12 AM, william humphrey b...@bluewatermaritime.com wrote: I was hoping for something that would call the system level busy and thus would work on all platforms. If I roll a pretty rainbow one which looks great on the present Mac OS it would fail on the different flavours of Windows and probably the next MacOS which very likely will feature a flat beach ball. On Tue, Oct 8, 2013 at 11:27 AM, dunb...@aol.com wrote: Hi. If you think your users are skittish that way, why not roll your own? A handful of small images that cycle around? Craig Newman -Original Message- From: william humphrey b...@bluewatermaritime.com To: How to use LiveCode use-livecode@lists.runrev.com Sent: Tue, Oct 8, 2013 11:19 am Subject: set cursor to busy Well I've been wondering about this feature. I have set cursor to busy whenever something takes more than a second and I see that interesting vintage black and white beach ball. That is fine and really a feature because I'm in the LiveCode developing environment so when LiveCode crashes then I see the colourful system beach ball spin and I know that is different than something from my code. But what about when my code is in a stand-alone? Won't users be confused by that vintage beach ball? Is there another way to say set cursor to busy? Perhaps set new system cursor to busy or (for old one) set system 8 cursor to busy? Any ideas? -- http://www.bluewatermaritime.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode -- http://www.bluewatermaritime.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: set cursor to busy
Shoot - I never considered that. I will look on the LiveCode list of example stacks and see if anyone put one there that I can use. On Tue, Oct 8, 2013 at 1:22 PM, Scott Rossi sc...@tactilemedia.com wrote: Just a suggestion: you might consider using your own custom busy indicator. This prevents you from having to match any particular OS/version. Just so you know, the beach ball on OS X is usually associated with non-responsive, so probably not the right message to send to your users when things are working but busy. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design On 10/8/13 10:12 AM, william humphrey b...@bluewatermaritime.com wrote: I was hoping for something that would call the system level busy and thus would work on all platforms. If I roll a pretty rainbow one which looks great on the present Mac OS it would fail on the different flavours of Windows and probably the next MacOS which very likely will feature a flat beach ball. On Tue, Oct 8, 2013 at 11:27 AM, dunb...@aol.com wrote: Hi. If you think your users are skittish that way, why not roll your own? A handful of small images that cycle around? Craig Newman -Original Message- From: william humphrey b...@bluewatermaritime.com To: How to use LiveCode use-livecode@lists.runrev.com Sent: Tue, Oct 8, 2013 11:19 am Subject: set cursor to busy Well I've been wondering about this feature. I have set cursor to busy whenever something takes more than a second and I see that interesting vintage black and white beach ball. That is fine and really a feature because I'm in the LiveCode developing environment so when LiveCode crashes then I see the colourful system beach ball spin and I know that is different than something from my code. But what about when my code is in a stand-alone? Won't users be confused by that vintage beach ball? Is there another way to say set cursor to busy? Perhaps set new system cursor to busy or (for old one) set system 8 cursor to busy? Any ideas? -- http://www.bluewatermaritime.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode -- http://www.bluewatermaritime.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode -- http://www.bluewatermaritime.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: set cursor to busy
On Tue, Oct 8, 2013 at 10:28 AM, william humphrey b...@bluewatermaritime.com wrote: Shoot - I never considered that. I will look on the LiveCode list of example stacks and see if anyone put one there that I can use. Don't animated cursors still work in Livecode? -- Stephen Barncard San Francisco Ca. USA more about sqb http://www.google.com/profiles/sbarncar ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
