NC 2.6 aborts if Exit after loading a Template file

[jss]

Hi,
It does it with all the templates - the distribution ones and my own.
It's as if the handler code for File>Exit is not the same as the X button (which may well be the case I guess).
regards
-jss

[jss]

Hi again Sherry,
I should have tried a bit further... but just to report that the crash happens as well if I try to Save any work done that was started by selecting a Template (via File>New as described above).

I did this (to see if would correct the problem):-
Copied ...\Templates folder to some other place
Re-installed NC2.6.3 from the link you supplied
Copied the Template folder back to correct place

The problem persists though.
The only way I can use NC now is to open a Template via File>Open as can't use File New at all.

I seem to remember there was something like this happened a long time ago (?).
Appreciate your help.
regard
-jss

[Sherry C]

Hi,

One real quick thought - check the Channel assignments (Staff/Setup) and see if any in the templates you're trying to use have "Auto" listed. Notation no longer uses an "auto" assignment (it was causing problems on a number of devices, having "cross talk" between instruments) and now only uses "hard" numbers. This is just a guess, but it's easy and worth a shot.

I've asked Mark to take a look at this thread to see if anything strikes him as a quick fix, else I'll write this up for fixing in the next maintenance release.

ttfn,
Sherry

[jss]

Hi
Think have found the problem.
There seems to be a conflict of some kind between NC and a product called Windowblinds (theme setter for Xp/Visa/V7 etc). If stop Windowblinds then NC works as it should.
regards
-jss
http://www.stardock.com/products/windowblinds/

[Sherry C]

Hi,

YES - glad you figured it out! We've had another customer a while back (couple of years?) who had a problem with Windowblinds (among other software, too). But the problem was different, so it didn't even cross my mind to ask about it.

Glad you're good to go now

Merry Christmas!
Sherry

[jss]

Hi
Just a thought but could it be worth investigating why NC does this? Maybe there are some benefits in doing so in that it can look even better? It may be non-trivial I guess.
regards and
Happy Christmas
-jss

[Sherry C]

Hi,

Well, given the low percentage of our users who use Windowblinds (we've only had two folks that we know of), the fact that Windowblinds is known to often conflict with any software that has it's own "skinning" capability (you can change the color scheme of Notation products), and that there are other tweaks/features of Notation products that would benefit a greater number of users, we have pretty much had to put this on the "won't do" list simply because our people-hours are limited (only so many people work here, and there are only so many hours in a day ) It's certainly not that we don't care about it - we'd love to be able to take the time to cover any and every situation so that every user has a pristine experience with our software. We just have to prioritize tasks based on many factors.

Merry Christmas (nonetheless )
Sherry