referring to other stacks: include .livecode extension
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller
referring to other stacks: include .livecode extension
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?
Is this a known issue? And how to resolve this?
Re: referring to other stacks: include .livecode extension
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
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
Re: referring to other stacks: include .livecode extension
Perhaps you need to provide a full file path rather than a relative one? The extension does not matter…
Re: referring to other stacks: include .livecode extension
Stam.
That still would mean a change somewhere in Windows, since v.10 does not care.
Craig
That still would mean a change somewhere in Windows, since v.10 does not care.
Craig
Re: referring to other stacks: include .livecode extension
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.
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.
Re: referring to other stacks: include .livecode extension
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
HyperActive Software | http://www.hyperactivesw.com
-
- VIP Livecode Opensource Backer
- Posts: 10043
- Joined: Sat Apr 08, 2006 7:05 am
- Contact:
Re: referring to other stacks: include .livecode extension
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
LiveCode development, training, and consulting services: Fourth World Systems
LiveCode Group on Facebook
LiveCode Group on LinkedIn