![]() If we want it to remember what we were doing last time (and automatically pick up where we left off), we have to tell it to do this. Using a Workspace to have PingPlotter Automatically Start Tracing on Startupīy default, PingPlotter Pro starts in “adhoc” mode - it’s ready to trace to whatever target you’d like to enter, but it doesn’t remember what you were doing last time you ran the program. For example, if you have a workspace called “Company Network s,” then all the collected data for that workspace would be saved in a folder titled “Company Network Status” in the same directory where the *.pws file resides. When saving data with a workspace - collected data (*.pp2 files) is saved in a directory named the same as the workspace. If needed, workspaces *can* be opened in read-only if opened elsewhere. If you’re using a copy of your PingPlotter Pro workspace, it’s locked - so another instance of PingPlotter Pro cannot open it (we don’t want to get confused about who “owns” the workspace). Once the workspace has been saved, it can then be configured to auto-save or load when PingPlotter Pro opens or closes (see the “automatically start tracing” section below), and auto-save based on a time interval. When PingPlotter is first launched, the workspace it uses is unnamed until you save it (“File” -> “Save Workspace”). Collected data (if you’ve selected that option).Window positions, sizes, tab docking status.Column widths, time graph heights, and timeline graph periods.The configuration that each target is using.(which have a *.pws extension) allow you to save what you’ve got set up in PingPlotter, so if you close/relaunch the program, you can pick up right where you left off.Ī workspace captures the following information: ![]() If you take the time to get everything set up *just* right in PingPlotter Pro, odds are, you won’t want to spend any time setting things up again.
0 Comments
Leave a Reply. |