7.0 Issues

Peter Haworth pete at lcsql.com
Sun Mar 23 13:37:28 EDT 2014


It seems there was a stray "save stack" lurking in my code.  I've removed
it and will put a bug fix release out there after a little more testing to
make sure all is still preserved across launches.

Pete
lcSQL Software <http://www.lcsql.com>
Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html>


On Sun, Mar 23, 2014 at 9:35 AM, Peter Haworth <pete at lcsql.com> wrote:

> Hmmm, I was not aware that lcStackbrowser saved its state to itself.  I
> agree that's a bad idea. It did at a very early release but I had requests
> to change that behavior and, unless I missed something along the way, all
> data that needs to be preserved between launches is saved in external files.
>
> Off to look at the code to see if I can spot what I missed, but there is
> one area that I have no control over.  If a user decides to change the
> plugin settings in some way, LC stores those settings in custom properties
> of the stack and, I think, immediately saves the stack.
>
> Pete
> lcSQL Software <http://www.lcsql.com>
> Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
> SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html>
>
>
> On Sat, Mar 22, 2014 at 6:46 PM, Mark Wieder <mwieder at ahsoftware.net>wrote:
>
>> Bernd-
>>
>> Saturday, March 22, 2014, 11:58:33 AM, you wrote:
>>
>> > That does affect e.g. plug-ins that save their state to themselves, as
>> > lcStackBrowser does.
>>
>> This, by the way, is a very bad idea.
>> Stacks, especially plug-in stacks, should save their state variables
>> into a preferences file and not try to modify themselves. I learned
>> this lesson the hard way some time back and always ended up shooting
>> myself in many feet. Now I only have two.
>>
>> --
>> -Mark Wieder
>>  ahsoftware at gmail.com
>>
>> This communication may be unlawfully collected and stored by the National
>> Security Agency (NSA) in secret. The parties to this email do not
>> consent to the retrieving or storing of this communication and any
>> related metadata, as well as printing, copying, re-transmitting,
>> disseminating, or otherwise using it. If you believe you have received
>> this communication in error, please delete it immediately.
>>
>>
>> _______________________________________________
>> 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