LiveCode Forums.

One. A disk image for LC v. 5.0 keeps appearing on my desktop after a few hours. Certainly when I walk in each morning. It started a couple of weeks ago. I keep throwing it into the trash.

Two. All of a sudden, when building a new version of a standalone that I have done for years, I get a huge dialog telling me that a file belonging to the build was not found. In that same dialog, I see a note that the standalone was built successfully. Should I care?

Craig

dunbarx wrote: ↑

Tue Oct 18, 2022 10:50 pm

One. A disk image for LC v. 5.0 keeps appearing on my desktop after a few hours. Certainly when I walk in each morning. It started a couple of weeks ago. I keep throwing it into the trash.

The ghost in the machine? The ghost of LC past?

1. Not sure about the dmg but I'd do a search for it and find out where it's coming from. If it's decompressed when you see it, (it's a window) right click on it and unmount it. The Mac thinks it's a volume in that case.

2. I had a similar problem with building an old stack recently. In my case the unfound item wasn't necessary for the build so it didn't matter. Later I noticed that the missing item was an image in Copy Files that was no longer used. You might check there and remove it.

Jacque.

Thanks.

I will check out that disk image the next time I see it. It looks normal, in that if I opened it, I could install v. 5.0.

The #2 thing indeed only started when I added a couple of lines of code that used the "revCopyFile" command, and a file path for it. But there is only a single pdf file in that folder, the one that I use for development.

Craig

Now I'm confused. Do you mean the DMG is expanded and you see a window with the arrow indicating you should drag the app into the applications folder? Or do you just see the file with the dmg extension? If you only see the file itself then you have gremlins.

Adding code to get a file isn't the same as including it in the Copy Files pane of the standalone settings. That tells me that your stack is running an open* or preOpen* handler during the build. If so, you'll have to block that handler if the builder is active. LC no longer locks messages during a build.

There's a handler to do that but I'm not at my Mac right now to look it up.

Jacque.

It looks normal, in that if I opened it, I could install v. 5.0.

Just the disk image is what I meant. I am used to gremlins.

As for the other, I do include the folder in the "Copy Files" pane of the "Applications Settings".

It occurs to me that I do not actually need to do that if I specify in the handler an explicit pathname to that folder. Or am I wrong about that?

Craig

dunbarx wrote: ↑

Thu Oct 20, 2022 7:10 pm

As for the other, I do include the folder in the "Copy Files" pane of the "Applications Settings".

It occurs to me that I do not actually need to do that if I specify in the handler an explicit pathname to that folder. Or am I wrong about that?

You're right, you don't need both. It's a little easier to leave it in Copy Files if the path won't change. I usually only script dynamic paths, just for convenience. Since you're getting an error during the build, the path in Copy Files might be incorrect if the file has moved.

Jacque.

Ha. My first time including and external folder. I had changed the name of the folder afterwards, without thinking of the ramifications. Notice went away.

So one can do that, and the builder will see the discrepancy, but still build a viable standalone.

Thank you

Craig

Jacque.

AHA. The disk image just appeared. "LiveCode Community 9.5.0". I was mistaken when I first reported that it was version 5.

Anyway, it is just an ordinary disk image. If I double click it, it opens the dialog suggesting I drag the LC icon to my Applications folder.

I am currently developing in Community 9.6.1, though I do pay for "ordinary" 9.6.8. I just never upgraded.

Craig

dunbarx wrote: ↑

Thu Oct 20, 2022 9:42 pm

So one can do that, and the builder will see the discrepancy, but still build a viable standalone.

Yup, you'll get a viable standalone but if files are missing it won't work right. I'm glad it warns us but it took me a long time to figure out where the file was that LC was looking for.

The disk image just appeared

Have you tried restarting Finder? It sounds like its confused. Or try running Disk Utility.