Re: Protecting Plugin stacks

Thanks for the suggestions everyone. I don't know how or why but this is working OK now. It may have been confusion on my part as to whether I was working on the dev version of the stack (which is not in the plugins folder) or the plugin version. Pete lcSQL Software On T

Re: Protecting Plugin stacks

Got a couple silly thoughts, first, have you tried going into the plugin settings for your plugin, change it to invis, modal, whatever, exit livecode come back in and set it to what you want, then see if the change sticks? Also, you don't have a "toplevel this stack" or anything of that nature bur

Re: Protecting Plugin stacks

Peter Haworth wrote: ...I'm still left with figuring out why the plugin doesn't open as a palette/modeless stack. For reasons I haven't figured out, the LC IDE doesn't use the engine's built-in style property for plugin stacks, instead using a custom property to mirror that built-in property

Re: Protecting Plugin stacks

On 7/10/12 12:49 PM, Peter Haworth wrote: But I'm still left with figuring out why the plugin doesn't open as a palette/modeless stack. Theoretically the plugin manager should handle that, but... did you specifically set the stack style and save it? set the style of this stack to "palette"/

Re: Protecting Plugin stacks

Thanks Jacque. I've pretty much resigned myself to that approach. But I'm still left with figuring out why the plugin doesn't open as a palette/modeless stack. Aside from making it slightly less likley that someone would mess with the properties, that does have the advantage of forcing the brows

Re: Protecting Plugin stacks

Reminds me of an old Excel spreadsheet I created that would automatigically create a radio log that the operators followed the following day, which would randomly choose music based on a series of parameters, along with commercials, public service messages etc. I showed them how to save the te

Re: Protecting Plugin stacks

On 7/10/12 12:17 PM, Peter Haworth wrote: I'm about to make my first plugin stack available and wondering how folks who have released plugins in the past have dealt with protecting them in various ways. If you've protected the scripts and hidden all sensitive property values, that's about all

Protecting Plugin stacks

I'm about to make my first plugin stack available and wondering how folks who have released plugins in the past have dealt with protecting them in various ways. I've password protected the stacks so the scripts can't be modified but as I've posted recently, that doesn't prevent the Inspector palet