Quote:
Originally Posted by ThatOneGuy
There may be some purposes though where someone may want the object to remain even if their plugin crashes. Though I don't have anything in mind myself, perhaps they would want it saved for other plugins interacting with theirs, and for those to function while the crashed one reloads. Just a thought...perhaps there could be a bool setting for each plugin that defaults to clean it up on unloading or fail state, but can be set not to do so?
|
I completely agree. I'm tossing up between a persistent flag per object or a persistent flag per plugin.
Per object is the way I'm leaning. It's easier to implement and let's a plugin have an assortment of persistent and non-persistent objects.
Quote:
Originally Posted by Chief149
I seem to be getting the following error when trying to call this.GetMemberOffset in one of my dynamic classes:
[SM] Exception reported: Unable to access dynamic handle 5767256
I've traced back through the stack trace and have confirmed for certain that I was acting on a valid dynamic object.
|
Would you kindly provide the stack trace?
__________________