We just received a most unusual crash report.
This is with the latest OpenDCL, Bricscad 11.4.5, and Windows 7.64.
The dialog box in question has a Picture Box and a Slide View.
Upon initialization, a slide from an SLB is loaded into the Slide View, and the PictureBox has a SetBackColor call to a medium grey.
One user has reported that in some instances, the dialog does not appear, and Windows reports Bricscad has stopped responding, waiting for splwow64.exe
As that is a print spooler process, I'm baffled! Is there something in OpenDCL that causes this process to start, and if so, can we disable printing support or something as a way of getting around the issue?
Or if you have any other ideas!
Thanks as always!
--J
OpenDCL would not have anything to do with the print spooler process. Is it possible you're introducing some kind of infinite loop that is using up all the CPU cycles? That would be my best guess if it really is related to your dialog. You could try disabling things one-at-a-time in your dialog to see if the problem disappears.
Well, there's certainly no infinite loops going on.
But I do see that splwow64.exe starts with Windows, I just don't see how it's related to our dialog or OpenDCL at all.
Thanks!
--J