@@ -226,3 +226,34 @@ Note: This has currently only been tested using [PyQt5](https://pypi.org/project
226226
227227To load the plugins append the path to [preditor/gui/qtdesigner](/preditor/gui/qtdesigner)
228228to the `PYQTDESIGNERPATH` environment variable.
229+
230+ # Change Log
231+
232+ * **2.0.0:** OutputConsole, link files to workboxe tabs and Workbox editing history
233+ * New reusable [`OutputConsole`](/examples/output_console.py) widget that optionally shows stdout, stderr, logging messages, and tracebacks
234+ * Workbox tabs can be linked to files and edited externally
235+ * Workbox content change history is versioned and you can quickly switch between the versions.
236+ * Recently closed workbox tabs can be be re-opened
237+ * Workbox preference saving has been re-worked. It will automatically migrate
238+ to the new setup so you won't loose your current workbox tab contents. However
239+ after upgrading if you want to switch back to the v1.X release see details.
240+
241+ <details>
242+ In the rare case that you must revert to older Preditor (v1.X), you will only
243+ see the workboxes you had when you updated to PrEditor v2.0. When you switch
244+ back to v2.0 again, you still may only see those same workboxes. This can be
245+ fixed with these steps, which in summary is to replace `preditor_pref.json`
246+ with one of the backups of that file.
247+
248+ * Options Menu > Preferences
249+ * In the `Prefs files on disk` section, click Browse. An Explorer window opens.
250+ * Close PrEditor
251+ * Go into the `prefs_bak` folder
252+ * Sort by name or by date, so most recent files are at the top
253+ * Look for a backup that is at least slightly larger than recent ones. If they are all the same size, go with the latest one.
254+ * Copy that into the parent directory (ie PrEditor)
255+ * Remove `preditor_pref.json`
256+ * Rename the `preditor_pref<timestamp>.json` file you copied, so it is `preditor_pref.json`
257+ * Restart PrEditor. Check if it has all your workboxes.
258+ * If it still isn't correct, do a little sleuthing or trial and error to find the correct backup to use.
259+ </details>
0 commit comments