LiveCode Forums

dunbarx wrote: ↑

Fri May 10, 2024 2:27 pm

@Jacque. The dictionary states:

Note: If there is no idle handler anywhere in the message path, no idle message is sent.

Ah. I stand corrected. The engine still uses it though.

Did you manually export your certificates from the old Mac to the new one? Using a backup won't work.
https://help.apple.com/xcode/mac/current/#/dev8a2822e0b

You can also use Keychain to export/import.

"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 object from whence it was changed. If in the card script, it will happily roam around all over, until,...

The cursor should remain locked across handlers until one of them unlocks it or an idle occurs. At least that's my current understanding. The fact that it doesn't is a bug.

Jacque thinks this was a bug that was resolved. It does not seem to be. I may be wrong about the fixed version of LC. The team built a custom version for me with the cursor fix because I relied on a constant custom cursor for a client project and defaultCursor wasn't working consistently. I assumed...

I believe they have to be PDF images. No, just standard PNG, black and white, and a third color marked as transparent. I should correct myself, the lock cursor command is supposed to last across handlers until it is unlocked, but a bug broke that until it was fixed recently, I think it was in LC 9....

The cursor resets on idle if "lock cursor" is used. The defaultCursor replaces the arrow throughout -- usually. In a standalone you're pretty safe but in the IDE sometimes the LC cursor takes over again if you focus on an LC stack like the script editor and then go back to the mainstack. There was a...

@stam: Cards receive messages before backgrounds if the group has background behavior set. If not then they behave like other controls and get messages before the card but after the controls the group contains. I am delighted to see that you and Richard are earth lovers. 🙂 Edit: I don't think openca...

Klaus wrote: ↑

Sun May 05, 2024 6:49 pm

Yes, that applies to widgets built with Livecode Builder, but does that also apply to SCRIPT (built with LC scripts) widgets?

Apparently. Who knows.

A long time ago one member referred to us as either sky worshippers or earth somethings. Wish I could remember the exact labels, it was clever. I am firmly bound to the earth but over the years I have learned to flip the vision the sky worshippers cling to. If that fails I use Google translate.

None of the built-in LC widgets respond to common mouse events either, the engine appears to ignore them. That's why each one has its own terminology for mouse clicks. I have no idea why they behave that way.

Having shut down and restarted LC it now appears that I have a stable bold black arrow to navigate with - just what I needed. I'm curious how you solved it. Did you set the defaultCursor? I had a stack that needed to use a custom cursor throughout and I ended up editing the arrow image in the revMa...

Any call to mobilePlaySoundOnChannel will stop the current sound if the sound channel is the same. You can stop the loop by calling mobilePlaySoundOnChannel with empty as the sound. Or you can replace it by calling mobilePlaySoundOnChannel with the same sound and passing "now" as the type.

I think I found a clue: if the main stack to be closed has its cantDelete property set to true, the delete stack command gets stuck. Is this a bug due to the double meaning of delete stack ? Good catch, that would be it. The cantDelete property comes from HyperCard and has been around for decades. ...

Where is the handler that deletes the stack? If it's in stack you're deleting, the problem might be the handler itself, which can't delete itself while its own handler is running.