NC 2.6 aborts if Exit after loading a Template file

[jss]

Hi,
Interesting -although it was kind of getting at the point that there *could* possibly be some underlying problem in NC that is causing such a serious error at the graphics api layers - and not to fix it just for Windowblinds users as such. fyi I have just finished trying over 30 (major graphic-intense) applications on this PC with WB and NC is the only one that crashes with it.
I of course understand there are other priorities.
regards,
-jss

[Mark W]

Hello Josh,

I have tried to reproduce this bug but could not. I was using the debugger so that any unusual problem would be likely by revealed, even without WindowsBlind in the picture. But no problem was revealed.

Josh, there is simply no way I can diagnose this problem without being able to reproduce it. The only way I can reproduce the problem would be to run WindowsBlind at the same time. But it probably not wise to devote development time on a rare set of conditions like these involving WindowsBlind.

Sincerely,
Mark

[jss]

Hi Mark,
The problem -only- arises when WB is running. I just turn WB off now that I found there is a problem running with NC and it then works fine. I just thought it may be useful to trace in case some lurking thing bites later - that was all I was getting at. I mention it not because I am WB user but see that WB makes intensive use of low-level graphic layers api etc so maybe a useful "testbed" of some kind.

Mentioned in case was useful.
regards
-jss

[Mark W]

Hello Josh,

Yes, WindowsBlind does serve as a "stress test", to use computer programming lingo. I don't intend to install it on my clean development and testing machines, because sometimes "Windows layer" software can behave sort of like a virus, that is difficult to uninstall. But, I might set up WindowsBlind in a "virtual machine" (a second copy of Windows running within Windows) so that I can just completely destroy the virtual machine after I'm done testing Composer with WindowsBlind.

This is a good insight you have as to how this rare circumstance problem could indeed expose a bug that might unknowing to me reveal itself with symptoms elsewhere-- probably also at the time of exiting Composer.

End of geek talk.

Cheers
-- Mark