-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash in PlasmaMax's GUIDialogComponent #165
Comments
I noticed a debug assertion being thrown in Max 2012 when navigating to/from GUIDialog components. Unfortunately, VS is not letting me debug them. Furthermore, those asserts don't actually crash max at all. I don't think there's much I can do at this point :/ |
I know it's been a while, but did you by chance note which assertion was triggering? |
I seem to recall that it was something internal to Max? That was a long time ago. I guess I could look again... |
Bah, if it's a Max error I don't think I have the will to fight with it anyway, at least not right now. |
@Deledrius @Hoikas I just test this with 3dsMax 7 and can't seem to duplicate it. Could it be caused by later versions? |
Oh, it seems to have been fixed. I'll do some testing and then close this if true. |
Indeed, this appears to have been fixed at some point. |
Yay for random fixage??? (Random fixing is not really a good thing, but this plugin is highly evil, so I'll take it...) |
To duplicate: create a GUI Dialog Component in PlasmaMax, attach it to one or more items, then view the details in the Component Util panel. Navigating away from the component's panel in any way will crash Max. It appears to happen while tearing down the dialog, leaving only the Color Scheme sub-panel visible during the mandatory program close.
Debugger reports an unhandled System.AccessViolationException.
The text was updated successfully, but these errors were encountered: