LiveCode Forums

The app opens different sub-stacks each of them is a copy of the main stack I use as matrix. The group of menu buttons is in that stack, so each window has the group of menu buttons. When the menu don't work you can choose the menu item which it become selected but no action is followed and this is ...

Done in that way, unfortunately some times it don't work. on preOpenStack if the environment is "standalone application" then set the defaultMenubar to "AppMenubar" -- set the defaultMenubar to the long ID of group "AppMenubar" of this stack -- set the menubar of this stack to "AppMenubar" end if en...

Thank you Jacqueline!

Is the file being saved a user document file, or something that your program uses internally? If the former guess you can always prepend something to the stack name when it's loaded and then remove it when the stack is being saved.. If the latter are you saving it to the Application Support folder ...

My problem is with documents that the user creates (which can be open it with a double click on the Finder)... :oops: The file name of a stack file need not be the same as the names of the mainstack and any substacks within it. If you need to ensure unique names for stack objects within a stack fil...

My problem is with documents that the user creates (which can be open it with a double click on the Finder)...

The script can check the name the user enters and if it is a single integer, put up a second dialog telling them that the name must include at least one alphabetic character. A second method would be for the script to add its own identifier. So if the user enters 2, the script would name the stack ...

I created the menubar item with Menu Builder. Currently I use this code to install it: if the environment is "standalone application" then set the menubar of this stack to "AppMenubar" end if All works well, but, sometimes, maybe after I move to another stack, I choose a menu item and it don't wok.

Hi Mag, why not use a (invisible) Livecode stack? Gazillion of storing possibilities with its custom properties and custom property sets! :D Best Klaus I tried this approach and it's great, thank you for the suggestion. My only problem now is when user choose an integer as name for the file (or cha...

Hi Mag, store an "alias" (= just the pathname!): ... set the cAlias2File of this stack to "/Users/klaus/Desktop/fingers.jpg" ... Store an actual file: ... set the cActualFile of this stack to url("binfile:" & specialfolderpath("desktop") & "/fingers.jpg") ... "Spit" it out again: ... put the cActua...

Thank you for the info. Anyway I'm using stack files ad app documents (they only store properties and I open them invisible when user double click them on the Finder only for read and write properties), so users have to have them available on the disk as icon to open them, share, delete and so on...

Thank you Craig. The name entered by the user is used for naming a file saved on disk, so I haven't the possibility to use a different name from the one assigned to the user. What's more the user can change the name of the stack in the Finder. Having not control over the name of the stack file, is t...

I noticed that If i assign to a new stack a number, for example 2, then I have problems to handle it because LC thinks that I'm talking of the stack 2, not the stack with the short name "2". create invisible stack "2" If is it a limit of LC, is there a way to avoid this? I can't choice the name beca...

When you have more than one copy of an app in your disk, can happen to open two of them. How to know if there is an (LiveCode made) app already open and avoid to open a new one?

Thank you so much Craig, I will go with the use of "there is a" operator