LiveCode Forums.

I'm running LiveCode Community 9.6.1.15522 on MacOS 11.1 Big Sur. (I almost always wait for a stable version.)

Thanks to jacque. That explains a lot.

While we're on the subject of dialogs that can't be dismissed, I also encountered this one:




I could not get it to respond to any mouse or keyboard inputs.

Thanks to all the responders. I think one of my misunderstandings is the concept of "purge". Searching for that term in the Dictionary and the Tutorials produced no hits. But apparently, opening and closing a document (stack file) has some hidden behavior unlike that of most other applications. The ...

During development work, at significant milestones, I close my stack, duplicate the stack file, rename it with an incremented version number, and then open that new stack. However, as a LiveCode beginner, I'm apparently omitting a step, because this process results in a dialog like this: Dialog.png ...

My project has a long-running task (60-90 seconds typically) than uses scripted paint tools to create a large graphic. Those tools only work in an image graphic that is in the top visual layer, so there is considerable visual clutter on the screen while the painting happens. To clean up this mess, I...

Thanks for the quick replies. As a LiveCode beginner, I was unaware of the relayering capabilities of a group. It also never occurred to me that moving the contents of an image to another image could be scripted just like moving the contents of a field to another field. Sometimes the obvious has to ...

In my stack, I use scripted painting tools to create the contents of three nonoverlapping image objects. This works, but there are some complications that raise some questions. 1. LiveCode will only allow painting into the image that is in the top layer. So to control which of my image objects gets ...

The problem has been resolved. First, in response to Klaus, here is my mouseMove handler: on mouseMove pNewH, pNewV showFloater pNewH, pNewV end mouseMove The showFloater script is in a front script for the stack. It converts the location parameters to row and column, and then displays them in a flo...

Thanks to all who replied. One responder asked, "Have you logged the mouseDown events to obtain precise timings? It may be useful to know the exact interval between those messages." There are no mouseDown events. I'm using only mouseMove events. My interactions with the graphic are solely based on w...

I have a stack that displays an image graphic, and I want the user to be able to interact with that image using the mouse. Somewhat simplified, I have a 100 x 100 grid of cells, each 10 pixels square. I want to use a mouseMove handler to display the row and column numbers of the cell the mouse is ov...

I have an array variable with a range of different kinds of data in the array elements. One element, call it myArray["identity"] , contains a text string. To access a particular character in that string, I would write code like this: if char 5 of myArray["identity"] is "X" then ... However, as a Liv...

Jacque: thanks for your reply. As a LiveCode beginner, it had not occurred to me that the script editor was just a stack. As an aside, that explains another issue that I had noticed about the script editor—its text scrolling does not reflect MacOS platform behavior with regard to the System Preferen...

Thanks for the reply. Actually, I upgraded to Big Sur only six days ago. The problem with the debugger has been around much longer. I'm seeing it more now because for the last two weeks, I've been spending several hours every day on a new project. I'm still running LiveCode 9.6.1.15522 from August 1...

Today I'm having a curious problem using the LiveCode debugger. I'd appreciate help tracking down the solution. It happens when I set breakpoints in a script. Upon reaching that breakpoint, I begin stepping through the code by clicking the "step over" button at the upper left. That's this button: St...