Forum Archive

i'm wondering if anybody can tell me specifically why it is when i jump from editorial to another app and then back, editorial often feels a need to refresh itself?

it's maddening sometimes!

i am processing lots of information and often have to switch out to safari, etc to look things up and find information i want to copy and paste back into my current document.

waiting for the document to refresh itself is a huge time waster when you type a lot in the iterative process i describe above. not only that but it doesn't remember the place you were at in the file when it reloads. so you have navigate back to where you last were which is usually where you want to paste what you just copied! in the case of working in the console editor, you lose the place i in the code where you just left off to go look something up in safari!!!!

lot of extra time and unnecessary scrolling. the 'refresh behavior' upon returning after app switches is not limited to editorial so it must be an iOS thing. i just want to know what it is. maybe if i upgrade my handheld it might go away, for instance i had more ram???

thoughts welcome

thx

What happens is most likely that iOS decides to quit Editorial while it's in the background to free up some RAM. This tends to be much less of a problem with more recent devices.

that's pretty much what i thought.. the less i have open and the less data the apps that are open seem to have or simply require on their own (ie the less ram they are using is my guess), the less refresh i get between app switches.

i just assumed it wasn't so much shutting down other apps as it was simply caching apps out of ram to disk or somethign so that they had to be paged back in memory

fwiw, i just found out my device only has 512M ram :) my guess is developers are all writing with much more memory at their disposal that generally comes with newer devices and forgetting about the older devices such as mine ;)

i'd be curious to see how much 1-2G of ram on a newer device would speed up my workflow.

thx for the input

On my iPad mini (512 MB of RAM) Pythonista is also "kicked out" regularly by iOS after I open a few other apps. On my iPhone SE (2 GB of RAM) Pythonista basically always stays running in the background even when I use it normally.

hey dg thx for that update. sounds like refresh is completely tied to ram and some new hardware would fix the problem.