[ANN] New plugin AAG|LayerComps

[Pete Haworth]

Thanks Andre, I just purchased it and so far it's working great!

Pete



On Fri, Jul 22, 2011 at 3:51 PM, Andre Garzia <andre at andregarzia.com> wrote:

> On Fri, Jul 22, 2011 at 7:45 PM, Pete Haworth <lists.pete at haworths.org
> >wrote:
>
> > OK, thanks for that info, that will definitely help.  I tend to be wary
> of
> > setting anything with "destroy" in its name to true!
> >
> > However Andre's plugin is still a hugely useful tool.  I just watched the
> > video on his web site and it appears that you can revert to previous
> > layouts
> > of any stack at any time.  So I can make layout changes to multiple
> stacks
> > (saving them in his plugin), save the whole stack file and when I open it
> > again, I can back out changes to any individual stack.  It seems that he
> > has
> > provided layout version control on a stack by (sub)stack basis.
> >
>
> yes you can use it to backup different layouts provided that you create new
> layer comps for each backup. The objective is to be able to switch layouts
> and/or layout elements on the fly. It also has an API that allows you to
> active those recorded layouts by code.
>
> :-)
>
>
>
>
> >
> > Pete
> >
> >
> >
> > On Fri, Jul 22, 2011 at 2:26 PM, J. Landman Gay <
> jacque at hyperactivesw.com
> > >wrote:
> >
> > > On 7/22/11 4:04 PM, Pete Haworth wrote:
> > >
> > >> That sounds great!  If I'm understanding it correctly, it will get
> round
> > >> one
> > >> of my pet peeves about changing card layouts in the IDE - many of the
> > >> changes cannot be undone and even if you close the card and say you
> > don't
> > >> want to save, the changes are already saved.
> > >>
> > >
> > > The changes aren't really saved, LiveCode never does that. Probably
> your
> > > stacks are using the default setting of the destroyStack property,
> which
> > is
> > > not to remove the stack from RAM when it closes. In that case, closing
> > the
> > > stack removes it from the message path and from view, but keeps the
> > current
> > > copy in memory. The next time you open it, it opens the copy in RAM
> which
> > > does still contain your changes. It hasn't been saved to disk though,
> and
> > if
> > > you quit LiveCode, or choose "Close and remove from memory" from the
> file
> > > menu, then you'll see it revert to its last-saved state.
> > >
> > > One of the first things I do when setting up preferences is to set the
> > > default behavior of destroystack to true, so that the situation never
> > > occurs. When I click the close box, the stack is removed completely so
> > that
> > > when it re-opens, its actual last-saved state is active.
> > >
> > > Destroystack was intended to speed up the display 15 years ago when
> > > machines were much slower. It isn't really needed any more. The one
> > > advantage it does have is if you don't save a stack and then you're
> > sorry,
> > > you can get your unsaved changes back by re-opening the stack before
> you
> > > quit LiveCode. So it's a trade-off.
> > >
> > > You can set the destroystack property for newly-created stacks in the
> > Files
> > > and Memory section of prefs. This won't change stacks you already have
> > > created. For that, use the stack property inspector.
> > >
> > > --
> > > 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<
> > http://lists.runrev.com/mailman/listinfo/use-livecode>
> > >
> > _______________________________________________
> > 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
> >
>
>
>
> --
> http://www.andregarzia.com All We Do Is Code.
> _______________________________________________
> 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
>