referring to other stacks: include .livecode extension

Got a LiveCode personal license? Are you a beginner, hobbyist or educator that's new to LiveCode? This forum is the place to go for help getting started. Welcome!

Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller

Post Reply
Martin-HC
Posts: 11
Joined: Fri Jan 31, 2025 5:27 pm

referring to other stacks: include .livecode extension

Post by Martin-HC » Wed Jun 11, 2025 4:31 pm

I work on different locations with different OS systems. I experience a lot of troubles when I try to (pre) load stacks under Win10 or Win11. Under Win10 I get away with "start using stack xxx" but under Win11 I have to use "start using stack xxx.livecode"
Is this a known issue? And how to resolve this?

dunbarx
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 10305
Joined: Wed May 06, 2009 2:28 pm

Re: referring to other stacks: include .livecode extension

Post by dunbarx » Wed Jun 11, 2025 6:40 pm

Hi.

I don't see anything in the dictionary that requires the extra ".livecode". The syntax says "any stack reference". Perhaps something in Windows 11? You may need to ask Scotland.

Craig

stam
Posts: 3061
Joined: Sun Jun 04, 2006 9:39 pm

Re: referring to other stacks: include .livecode extension

Post by stam » Wed Jun 11, 2025 7:30 pm

Perhaps you need to provide a full file path rather than a relative one? The extension does not matter…

dunbarx
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 10305
Joined: Wed May 06, 2009 2:28 pm

Re: referring to other stacks: include .livecode extension

Post by dunbarx » Wed Jun 11, 2025 8:18 pm

Stam.

That still would mean a change somewhere in Windows, since v.10 does not care.

Craig

stam
Posts: 3061
Joined: Sun Jun 04, 2006 9:39 pm

Re: referring to other stacks: include .livecode extension

Post by stam » Wed Jun 11, 2025 10:27 pm

OR it could mean that an incorrect file name/path was passed. Or that the Win version of LC is now more finicky. Since we both know extensions aren’t the issue, it’s worth a try.

The last thing I would do is assign this to a change in Windows - while that’s not impossible, user error is the commonest culprit in errors that don’t make sense. And enforcing full file paths may eliminate an issue.

jacque
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 7389
Joined: Sat Apr 08, 2006 8:31 pm
Contact:

Re: referring to other stacks: include .livecode extension

Post by jacque » Thu Jun 12, 2025 6:09 pm

One solution that might help for both conditions is to set up the stackfiles property in the mainstack. That allows you to use the short stack name while the engine uses the long file name.
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com

FourthWorld
VIP Livecode Opensource Backer
VIP Livecode Opensource Backer
Posts: 10043
Joined: Sat Apr 08, 2006 7:05 am
Contact:

Re: referring to other stacks: include .livecode extension

Post by FourthWorld » Sat Jun 14, 2025 5:45 pm

Without seeing the code in question we can only guess.
Richard Gaskin
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn

Post Reply