Re: some, but not all, custom properties survive paste to new stack

2017-02-08 Thread Dr. Hawkins via use-livecode
On Wed, Feb 8, 2017 at 1:34 PM, Paul Dupuis via use-livecode < use-livecode@lists.runrev.com> wrote: > All properties and > values were copied. > They had been for me until recently. At this point, I have it cleared, but I'm suspecting a deeper bug is behind it. I had set the properties for a

Re: some, but not all, custom properties survive paste to new stack

2017-02-08 Thread J. Landman Gay via use-livecode
On 2/8/17 3:34 PM, Paul Dupuis via use-livecode wrote: Now I was reminded the the custom property tab in the Project Browser is wacky - I would click the add new element "plus", select the default "1" for the key, rename it, click in the value box and enter a value and then click on the plus for

Re: some, but not all, custom properties survive paste to new stack

2017-02-08 Thread panagiotis merakos via use-livecode
> >>I have not yet checked 8.1.3 to see if that bug of the Project > Browser is one of the many things fixed in 8.1.3. > @Paul I guess you mean "Property Inspector", and yes, it is fixed :) http://quality.livecode.com/show_bug.cgi?id=18302 @Richard Could you please file a bug, including a

Re: some, but not all, custom properties survive paste to new stack

2017-02-08 Thread Paul Dupuis via use-livecode
On 2/8/2017 2:03 PM, Dr. Hawkins via use-livecode wrote: > more hair-pulling time . . . > > I paste a group from a source stack to an output stack in a script. > > Some, but not all, of the custom properties that I set survive this pasting. > > For example, my source field has properties mrgns,