Re: hunting a bug on scripted custom properties not being saved

2015-12-02 Thread Dr. Hawkins
On Wed, Dec 2, 2015 at 3:44 AM, [-hh] wrote: > Up to LC 8-dp9, the properties are there, but NOT displayed in the new PI. > That's not the same bug, then. Here it would retrieve the old value, and open the older file. -- Dr. Richard E. Hawkins, Esq. (702) 508-8462

Re: hunting a bug on scripted custom properties not being saved

2015-12-02 Thread [-hh]
Yes, I got it now. Didn't read exact enough, sorry. Perhaps your's is somehow connected to the new option "Preserve stack file version on stacks saved in legacy format" of the 'Files & Memory' tab of the prefrences? Would be interesting how your technique and this option interfere? To know at

Re: hunting a bug on scripted custom properties not being saved

2015-12-02 Thread [-hh]
> Richard E.H. wrote: > I have a routine to bump the versions of stacks and save ... Read your first post again. I misunderstood what you are doing. By "the versions of stacks" you mean your development version of stacks, not using 'the stackFileVersion' of LC. Sorry. Hope you get this solved.

Re: hunting a bug on scripted custom properties not being saved

2015-12-02 Thread [-hh]
I had similar behaviour, connected to that, with the new property inspector. I set and saved properties in LC 7, reopened the stack in LC. The LC 7 PI shows the properties, also after reopening. Up to LC 8-dp9, the properties are there, but NOT displayed in the new PI. This bug is removed in

Re: hunting a bug on scripted custom properties not being saved

2015-12-01 Thread Peter Haworth
I've run into this as well, don't remember if I entered a bug report or not. Pete lcSQL Software Home of lcStackBrowser and SQLiteAdmin On Tue, Dec 1, 2015 at 5:55 PM, Dr. Hawkins

hunting a bug on scripted custom properties not being saved

2015-12-01 Thread Dr. Hawkins
This has been taunting me all day. I have a routine to bump the versions of stacks and save them, and to set the new name as a custom property of the control stack. That main stack, at the moment, typically has not changes made to it until this happens. It appears that if the only change to the

Re: hunting a bug on scripted custom properties not being saved

2015-12-01 Thread Dr. Hawkins
On Tue, Dec 1, 2015 at 6:12 PM, Peter Haworth wrote: > I've run into this as well, don't remember if I entered a bug report or > not. > I just filed one. No number, as I had to pick up another computer to do it. -- Dr. Richard E. Hawkins, Esq. (702) 508-8462