This sort of thing is happening too much. A file name only needs just an extra character in order to make it different from the original. So why does livecode present me with these messages despite making the file name always different from the original? The thing is It Is Not The Same is it?
Chris
What is wrong with Livecodes understanding of File names?
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, asayd
-
dave.kilroy
- VIP Livecode Opensource Backer

- Posts: 858
- Joined: Wed Jun 24, 2009 1:17 pm
- Contact:
Re: What is wrong with Livecodes understanding of File names
Hi Chris
A stack name is not the same as the stack's file name. The IDE is complaining it already has a stack with the same name (even though the file names are different). There are various ways forward for you but one is to simply change the stack's name (in the inspector).
Dave
A stack name is not the same as the stack's file name. The IDE is complaining it already has a stack with the same name (even though the file names are different). There are various ways forward for you but one is to simply change the stack's name (in the inspector).
Dave
"...this is not the code you are looking for..."
-
FourthWorld
- VIP Livecode Opensource Backer

- Posts: 10066
- Joined: Sat Apr 08, 2006 7:05 am
- Contact:
Re: What is wrong with Livecodes understanding of File names
It's not the file name, it's the stack name. LC is able to allow references to stacks by their short name by requiring that each open stack have a unique name.
Do you need the one in your temp directory? What are you aiming to do?
Do you need the one in your temp directory? What are you aiming to do?
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
-
dave.kilroy
- VIP Livecode Opensource Backer

- Posts: 858
- Joined: Wed Jun 24, 2009 1:17 pm
- Contact:
Re: What is wrong with Livecodes understanding of File names
Of course the other option for you is to close and re-open LiveCode - and then because neither of your stacks with the same name will be in memory you can open whichever one you wish without conflicts...
"...this is not the code you are looking for..."
Re: What is wrong with Livecodes understanding of File names
Thankyou gentlemen, I understand it now. Thanks Dave. FouthWorld, When I go back after a little while to re-do the same exercise (so as to cement the learning) I just want my original (in case I forget something) to be alongside the newly opened identical stack as I work on it.