Re: Deleting stacks on the fly

2017-02-17 Thread panagiotis merakos via use-livecode
Hi Brahmanathaswami, What happens if you set the acceleratedRendering of the stack to false? Best, Panos -- On Thu, Feb 16, 2017 at 9:08 PM, Sannyasin Brahmanathaswami via use-livecode wrote: > @ Jacque: I don't think it is ram after all. > > FYI: on my Nexus 5

Re: Deleting stacks on the fly

2017-02-16 Thread Sannyasin Brahmanathaswami via use-livecode
@ Jacque: I don't think it is ram after all. FYI: on my Nexus 5 I have 1.8 GB RAM and our new app + All of Googles "widgets" that come preloaded take up a mere .8 GB and I have a full GB of RAM free. after proceeding (as we discussed off list with our team) to delete stacks when we move from

Re: Deleting stacks on the fly

2017-02-14 Thread J. Landman Gay via use-livecode
On 2/14/17 3:38 PM, Richard Gaskin via use-livecode wrote: J. Landman Gay wrote: My other project is crashing on Android the same way. It also has heavy server/internet use. I'm starting to think that's where the problem lies. I wonder if that may be related to some of the leaks closed

Re: Deleting stacks on the fly

2017-02-14 Thread Richard Gaskin via use-livecode
J. Landman Gay wrote: My other project is crashing on Android the same way. It also has heavy server/internet use. I'm starting to think that's where the problem lies. I wonder if that may be related to some of the leaks closed recently. -- Richard Gaskin Fourth World Systems Software

Re: Deleting stacks on the fly

2017-02-14 Thread J. Landman Gay via use-livecode
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 F

Re: Deleting stacks on the fly

2017-02-14 Thread J. Landman Gay via use-livecode
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 |

Re: Deleting stacks on the fly

2017-02-14 Thread Bob Sneidar via use-livecode
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

Re: Deleting stacks on the fly

2017-02-13 Thread J. Landman Gay via use-livecode
On 2/14/17 12:00 AM, Sannyasin Brahmanathaswami via use-livecode wrote: Deleting stacks isn't helping. My Nexus 5 has 1 GB free RAM even with all of Google's widgets and my app open and going from Stack B back to stack A then deleting StackcB in 10 milliseconds is "nothing" in terms of memory

Re: Deleting stacks on the fly

2017-02-13 Thread Sannyasin Brahmanathaswami via use-livecode
FWIW, tested on an android device with plenty of memory Deleting stacks isn't helping. My Nexus 5 has 1 GB free RAM even with all of Google's widgets and my app open and going from Stack B back to stack A then deleting StackcB in 10 milliseconds is "nothing" in terms of memory requirement,

Deleting stacks on the fly

2017-02-11 Thread Sannyasin Brahmanathaswami via use-livecode
I'm trying to optimize for minimal RAM usage on mobile. The app is modular with many stacks that are opened from the mainstack. I had this before in a global library: command portal_GoStack stackName -- goes to the new stack -- closes the current stack # But we want to delete it to clear RAM --