BTW, we're not talking about creating and deleting new stacks on the fly,
we mean the "delete stack" command that removes an open stack from RAM.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On February 14, 2017 10:51:06 AM "J. Landman Gay via use-livecode"
<use-livecode@lists.runrev.com> wrote:
I frequently delete stacks when memory is an issue, which is the problem
with Swami's stack suite. I also create almost all new stacks with
destroystack set to true for the same reason.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On February 14, 2017 9:44:36 AM Bob Sneidar via use-livecode
<use-livecode@lists.runrev.com> wrote:
Is there any reason to delete the stack? If not, don't. Clearly any CtoD
should be investigated, but I have never seen why an app would be designed
to create and delete stacks when all you have to do is show and hide
existing ones.
Bob S
On Feb 13, 2017, at 22:00 , Sannyasin Brahmanathaswami via use-livecode
<use-livecode@lists.runrev.com> wrote:
This works if we just use "close stack oStackName"
but if I change this to "delete stack oStackName"
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
