On 8/12/11 8:57 PM, Chip Thomas wrote:
Oh my gosh! Thank you so much!
It's always the obvious solutions, isn't it? :)
I'm glad it's fixed, but it doesn't explain why you were able to get the
watch cursor sometimes. The watch is in the cursors stack too. Odd.
Maybe it's buried in the OS some
Oh my gosh! Thank you so much!
It's always the obvious solutions, isn't it? :)
On Fri, Aug 12, 2011 at 10:59 AM, J. Landman Gay
wrote:
> On 8/11/11 7:19 PM, Chip Thomas wrote:
>
> One project is a launcher system where the standalone just launches a
>> separate main stack file. The cursor scr
On 8/11/11 7:19 PM, Chip Thomas wrote:
One project is a launcher system where the standalone just launches a
separate main stack file. The cursor script is on the card of this stack
file. In this project, I don't get any cursor changes except when in the
development environment.
The second pr
I much prefer never to lock the cursor -- it tends to stay locked at odd
moments. Instead try setting "the defaultcursor."
The problem of your cursor changes not happening as expected probably comes
down to where the script is -- it may not be in the message path for some
reason, maybe you are
Looks like 2 issues here. First getting the cursor to stick; second getting
the correct cursor display.
Lock/Unlock cursor should resolve the first; importing and using your own
cursor image should resolve the second.
local cHand=999100
local cArrow=999101
on mouseEnter
if "button" is word 1 o
