Good question. Unless there are stress-testing tools for this, maybe
open the app in the morning, use a lot of apps throughout day while
never re-opening yours, and in the evening finally bring yours to the
front any see if it evidences time-dependent behavior.
--
Richard Gaskin
Fourth
Haven't noticed any problems but the honest answer is that I don't know. How
would you go about testing for issues?
Terry...
On 4/3/19, 5:28 am, "use-livecode on behalf of Richard Gaskin via use-livecode"
wrote:
Terry Judd wrote:
> While there don't appear to be suspend or
Terry Judd wrote:
> While there don't appear to be suspend or resume messages on mobile
> you can sort of script your own resume message using a timer.
I had thought both iOS and Android would reclaim memory by closing
backgrounded apps if needed.
Is that no longer the case?
Does the use of
Wow, that's cool we could put a button in the game that passed.
"Keep Puzzle"
(# for as long as the app is open)
on MouseUp
updateSessionTimer "reset"
end mouseup
though I wonder if the app would crash after a while, if the user forgot about
it?
Worth a try, because there a very
While there don't appear to be suspend or resume messages on mobile you can
sort of script your own resume message using a timer. If the timer is updated
regularly using a send in time approach then the send will be delayed while the
app is in the background. If the interval between the current
On Android, if you leave the app, the OS will remove it from RAM if it
needs the memory. It sounds like iOS is doing the same thing. Since
SivaSiva is so big, memory may be tight enough to drop the puzzle stack
when you come back to the app. It would depend on the RAM in the device.
I don't
Good morning Richard
"But just to clarify, the stack in question is a separate stack file, and
not a substack of the one you're going to, yes?"
@ Peter & Ralph
"inspectors still open for closed stack" -- that would be only desktop.
But this is on mobile. In a standalone.
That's one of my annoyances. Say you are inspecting a field and then delete the
field the inspector does not close. One would think that if a control is
deleted while an inspector for that object is open the inspector would close.
This makes me wonder if the card retains some artifacts of the
I’ve found that if an inspector is open for something in that stack, purging is
incomplete.
Peter
> On Mar 1, 2019, at 7:37 AM, Richard Gaskin via use-livecode
> wrote:
>
> Sannyasin Brahmanathaswami wrote:
>
> >... although all my modules/stacks have both "purge stack/window" set
> > to
Sannyasin Brahmanathaswami wrote:
>... although all my modules/stacks have both "purge stack/window" set
> to true, I am seeing change on stacks that are "closed" when you
> reopen them again.
>
> Thus, it means that Purge stack/window is not implemented on
>
> Go [new-stack] in window of
Good news!
Go [new-stack] in window of stack [old-stack]
Is working on mobile! I was revamping the navigation of SivaSiva, and thought
I would try it. (did not work on a few version ago). Now works great. Even
moving from portrait to landscope, as a long you have to
11 matches
Mail list logo
