Dachannien
October 16th, 2007, 03:59
There are some cases where the combat tracker does not save, even when it is supposed to.
One: both autosaves and manual /saves. Neither of these cases will cause the combat tracker to save its current state. AFAIK, there is no way to hook the save function and cause the tracker to save, so it may be useful to sprinkle the tracker code liberally with calls to the storeToRegistry function.
Two: exiting the program without first closing the combat tracker. Exiting the program apparently does not trigger the onClose event for the combat tracker window. If you exit the program without closing the combat tracker, the tracker's current state will not save.
The combination of these two problems means that there are multiple situations where you can lose the results of a combat in the middle of said combat. Specifically, if you exit without closing the combat tracker, or if FG crashes, you will lose all changes made to the combat tracker during the current session.
The recent ruleset customization made by rh4300 might come in handy, providing a manual way to minimize the chances of having problems occur, until SmiteWorks can patch the program itself to resolve the issue with the onClose event not firing.
One: both autosaves and manual /saves. Neither of these cases will cause the combat tracker to save its current state. AFAIK, there is no way to hook the save function and cause the tracker to save, so it may be useful to sprinkle the tracker code liberally with calls to the storeToRegistry function.
Two: exiting the program without first closing the combat tracker. Exiting the program apparently does not trigger the onClose event for the combat tracker window. If you exit the program without closing the combat tracker, the tracker's current state will not save.
The combination of these two problems means that there are multiple situations where you can lose the results of a combat in the middle of said combat. Specifically, if you exit without closing the combat tracker, or if FG crashes, you will lose all changes made to the combat tracker during the current session.
The recent ruleset customization made by rh4300 might come in handy, providing a manual way to minimize the chances of having problems occur, until SmiteWorks can patch the program itself to resolve the issue with the onClose event not firing.