This may seem dumb, but why is this property available to set?
closeStack means close stack, so under what circumstances would I want to leave it in memory?
Also, I save my projects to a local folder which is also a cloud folder (Dropbox) and I will usually be very careful to "quit" (close) projects or the entire LC app on one machine if I know I might be opening that project on my other Mac -- for obvious reasons: mostly to avoid the nightmare scenario of making changes to the wrong copy of my stacks.
Would I be smart to make destroyStack true as a rule?
And what's a compelling example of why the LC engine makes this property optional in the first place? I understand the memory-saving reason stated in the Dictionary, but who does this apply practically?
And, one last thing, why on earth has this property been named to terrifyingly? It's always scared the hell out of me!!
closeStack means close stack, so under what circumstances would I want to leave it in memory?
Also, I save my projects to a local folder which is also a cloud folder (Dropbox) and I will usually be very careful to "quit" (close) projects or the entire LC app on one machine if I know I might be opening that project on my other Mac -- for obvious reasons: mostly to avoid the nightmare scenario of making changes to the wrong copy of my stacks.
Would I be smart to make destroyStack true as a rule?
And what's a compelling example of why the LC engine makes this property optional in the first place? I understand the memory-saving reason stated in the Dictionary, but who does this apply practically?
And, one last thing, why on earth has this property been named to terrifyingly? It's always scared the hell out of me!!
Statistics: Posted by mbossiere — Sat Jan 25, 2025 1:07 am