dynamically setting standalone setttings

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
magice
Posts: 457
Joined: Wed Mar 18, 2009 12:57 am

dynamically setting standalone setttings

Post by magice » Fri Feb 27, 2015 2:40 pm

This is a long shot, but is there a way to set standalone settings in a dynamically created stack? I find myself creating a certain style of stack repetitively. So, like all repetitive tasks I decided to create an app to automate the process. The app works perfectly in that all I have to do is open the created stack in LC to save it as a standalone. However, I still have to choose the windows platform, and navigate to my .ico file for the app icon. I have tried setting the standalone settings in the template stack, but they do not carry over when cloned. Is this possible?

Klaus
Posts: 14199
Joined: Sat Apr 08, 2006 8:41 am
Contact:

Re: dynamically setting standalone setttings

Post by Klaus » Fri Feb 27, 2015 2:47 pm

Hi Magice,

all these infos are stored in a custom property set of the "standalone" stack named: cRevStandaloneSettings
I think the standalone buiding process will use this info!

1. Create a stack
2. Set some standalone settings for it
3. Check the custom property set "cRevStandaloneSettings" and its keys/values
You may need to check "LiveCode UI elements in lists" in menu "View" to see this CPSet.


Best

Klaus

magice
Posts: 457
Joined: Wed Mar 18, 2009 12:57 am

Re: dynamically setting standalone setttings

Post by magice » Fri Feb 27, 2015 3:09 pm

Thank you Klaus. I believe I can work with that.

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

Re: dynamically setting standalone setttings

Post by dunbarx » Fri Feb 27, 2015 4:43 pm

And this is one of the most endearing aspects of LC.

Everything in LC is a stack. So though it was a very pleasant surprise to me that a custom property set contained all the pertinent information that Magice wished for, it should not have been a surprise at all. If that gadget is a stack, where else could such information be held except in some intrinsic and familiar feature of a stack.

Craig

Post Reply