[CONFIRMED] MINOR bug: Snap resolution switches to 1/4 after opening saved project?

No biggie but I know sometimes these things can point to larger bugs so figured maybe it should be tested. I've noticed this pretty consistently due to the nature of the project I'm working on.
 
First off I am still on Dorchester so maybe it has been fixed.
 
Step 1) Open project (an existing/populated project might be best... not a new one but IDK)
 
Step 2) Disable Smart Grid in the Snap settings
 
Step 3) Turn on Snap and Set your Snap resolution to 1/64 (not sure the exact setting matters but I'm using 1/64)
 
Step 4) Turn off Snap then Save and close the project (I am using Save As for versioning... not sure if that makes a difference)
 
Step 5) Reopen the newly saved project
 
Expected: The project retains the last snap settings after reopening, turning on Snap and beginning work.
 
Reality: Upon opening the project it seems to retain the 1/64 Snap res at first but as soon as I turn Snap back on it changes to 1/4 which, if I don't notice it, screws up my first Snap edit. Easy to correct but I doubt that is intended behavior.
 
This may not be an exact recipe because I have not thoroughly tested it using all possible variations. It just seems to be happening every time I open and due to the repetitive nature of the work I'm doing I can take a good guess this is what should reproduce it if there is a problem.
 
This project is exposing a couple other, not so minor, quirks as well but they are intermittent so I'll explain those another day.
 
Back to work... and if this does get comfirmed perhaps the hosts can just go ahead and tag/move to the Problem Reports area because I never get around to it.
 
Cheers.

Can you test the recipe though, please? Best to confirm this specifically.
 
And remember that Smart Grid needs to be turned off. That can seriously skew this test. I never use that thing anyway. I have a feeling though that the Smart Grid code may be what is causing this... as in when the project opens it gets confused and thinks SG is on because it is the default so sets the Snap res to what it THINKS it should be. Until I realized something wasn't right I kept actually checking to make sure Smart Grid was disabled.
 
I honestly don't like that feature... at least not as default. I can see how it's useful though... to some... maybe... kind of. ;-)

Thanks, Brundle... and yeah I'm a bad Beeps for not keeping up on reports. I just get so freaking distracted/busy. This is why I would suck as a Beta tester even though I am now using the program 8 hours a day.
 
If it's been reported though then that's cool and I'll try to get a better process going for such things. Maybe what I'll do is keep a notepad log of stuff I encounter then just do a bulk dump every now and again. I run into so few consistently reproduceable problems these days it hardly seems worth it and with the new update scheme most of this crap will likely be dealt with before I even get a chance.
 
Most of my REAL issues are more about efficient data flow I think which I would have no idea how to diagnose/describe properly... and seems to be getting worked on line by line in the bakery these days anyway.

Thanks for checking Jonesey.
 
Since this has been confirmed mayhaps the thread could get hustled on down to problem reports?
 
PS: Jonesey... I have not ignored that other clip color thread. Just haven't had time to try out some stuff and have been plodding on as is. I think I'm going to have to come up with a special color scheme that works for me and my eyeballs. I'll update it if I figure out a good workaround.
 
Cheeeers!

I'm pretty sure I reported this in X1 but was told that it was intended behaviour. IIRC it is a per project setting that's involved so you have to check it with every project as you go.

beepster - please report this via the problem reporter and post the CWBRN in the title.
 
http://www.cakewalk.com/Support/ProblemReporter/