If you start tracing a target and stop after 3 samples, that "session" will get marked to keep.
#PINGPLOTTER AUTO SAVE HOW TO#
There are a few different options for how to recognize a session as one you want to keep around, or one you want to throw away when done. The auto save settings can be configured in PingPlotter by going to either "Edit" -> "Options" -> "Auto-Save" (on Windows) or "PingPlotter" -> "Preferences" -> "Auto-save" (on Mac). Configuring the definition of "short term" sessions This behavior is a direct result of feedback from our users (and us) that prompting to save on close was frustrating.
If you closed a session you really wanted to continue, you can reopen that session within 5 stop/restarts and continue. When a session is marked for deletion, it will be fully deleted after you close and reopen PingPlotter five times. Short term sessions are saved continuously, but if you don't collect data long enough, they are marked for deletion when closed. Closing and restarting will resume those sessions. Long-term sessions (a session is a set of collected data from a trace to a target) are saved continuously, and when you scroll back in history, the data is retrieved from disk. This helps make sure that none of your data is lost at any point (for instance - if there is an unexpected restart, a power failure, or any other event that would put data data at risk). PingPlotter 5 writes all data in real-time to its local data store. In PingPlotter 5, it should "just work", saving what you want, discarding what you don't (if you show it what kind of stuff you don't want). This is something that shouldn't happen to you in V5. In V4, it didn't save automatically, and sometimes important data wasn't available when you needed it (unless you did some configuration that didn't always think the way you do).
0 kommentar(er)
