paste
Peter Haworth
pete at lcsql.com
Mon Nov 25 18:34:03 EST 2013
Hi Jacque,
I originally had the control I wanted to copy (it's a group actually) in a
resources stack within my application. That worked fine in my dev stack
but the released stack is password protected so I can't copy from it. And
of course I didn't figure that out until the last minute after adding
password protection.
Of course I could have created an unprotected stack to contain the group
but I chose to go the cprop route because all my resources would still be
in my resources stack, just seemed tidier that way. And I will admit to
some bloody mindedness since I fail to see why I should not be able to copy
a control from a password protected stack if it has no script attached to
it.... but that's another story.
Pete
lcSQL Software <http://www.lcsql.com>
On Mon, Nov 25, 2013 at 2:50 PM, J. Landman Gay <jacque at hyperactivesw.com>wrote:
> Peter Haworth <pete at lcsql.com> wrote:
>
> A while back, there was a discussion on how to store an control definition
>> in a custom property and create the control from the custom property by
>> copying and pasting the control into and out of the custom property.
>>
>> I have all that working fine but I need the pasted control to end up in a
>> group and the paste command doesn't have an option to paste into a group
>>
>
> I'm working with something similar right now. I store all the template
> objects in an unplaced group in the source stack. When I want to use one I
> just copy it by script, which allows copying either to the card or directly
> into a group. It also has the advantage that it doesn't replace the user's
> clipboard.
>
> --
> Jacqueline Landman Gay | jacque at hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
More information about the use-livecode
mailing list