LiveCode Forums

Aha. In the previous setup, if I do not lock the cursor, it barely ever changes as I move around within the button. It has fleeting instances where it does, but they are really fleeting. So locking the cursor does indeed have an effect, but you have to work hard to find it. And it proves even more s...

Jacque. I made a new card with a new button and a field, with the following in the card script: on mouseMove put random(999) into fld 1 if the mouseLoc is within the rect of btn 1 then set the cursor to watch lock cursor end if end mouseMove Moving the cursor loads numbers into the field. When I ent...

Jacque. The cursor should remain locked across handlers until one of them unlocks it or an idle occurs "Idle" is not sent unless there is an actual idle handler somewhere. Thank heavens. Didn't HC sent them always? Anyway, it seems that the cursor only stays locked based on its remaining within the ...

This stack shows that one may change and lock a cursor under script control. When that handler ends, the new cursor sticks, as shown by the action of a mouseMove handler that loads a field with numbers. But ONLY while the cursor is within the rect of the object within which it was changed. Once it l...

I take much back. Richmond, your latest stack changes and locks the cursor upon mouseEnter into a field. But the cursor reverts once one leaves the rect of the field. What were you trying to show here? And I just played with the two "Curses" stacks, and neither exhibits any permanence to a cursor. S...

Richmond is using an old version of LC to demonstrate that the "lock Cursor" command once worked as advertised. The "defaultCursor" property has been around since LC v.2.

None of this is helpful, but we do have "defaultCursor".

Craig

Richmond, are you in LC 9.6.9?

Craig

Jacque thinks this was a bug that was resolved. It does not seem to be. I cannot imagine how Richmond made his work. He uses an image, whereas I only changed the cursor to one of the available standard offerings. That should not matter. But then what is the point of the "defaultCursor"? The issue is...

Jacque. I do not think so. My test stack has a button with: on mouseup set the cursor to watch lock cursor --wait until the mouseClick-- with messages end mouseUp Clicking on the button changes the cursor. But moving that cursor out of the rect of the button reverts to the standard arrow. I am in LC...

Richmond.

Are on linux? For me, only the global "defaultCursor" will allow me to keep whatever cursor I chose using the browse tool.

Surely the platform cannot have that sort of difference.

Craig

Richmond. Just downloaded your second stack. Nope. Again, the issue is that the cursor property cannot be used if one expects it to stick as the user navigates around the card. Richard really points out that, counterintuitively (at least to me) the "cursor" property, along with "lock cursor", is not...

Richmond.

Your "paw" changes as soon as the cursor leaves that image. That is what I wrote about initially.

Craig

Richard.

Yep, that does it, thanks. Do not remember that at all. The dictionary ought to at least mention it in related "cursor" entries.

Craig

It seems that changing the cursor is meant for running handlers, not just general cursor "styles".

But is there no way to simply have ones own cursor for general use?

Craig

This derived from a thread about cursors. I almost never use the "cursor" property. But I do not understand why, in a new stack with a single button, in the button script: on mouseUp set the cursor to watch lock cursor end mouseUp The cursor only is watch while within the rect of the button itself. ...