For those using different snaps per screenset - help testing a bug(?) please.

*********************************************************************************************************************
WARNING. This is crashing Sonar for me consistently and may have even rendered one of my screensets in the project inaccesible so don't try this on anything important
*********************************************************************************************************************

Can anyone who is using different snap settings per screenset please try something for me.

1. Start in a screenset with a beat value such as 1/4 - not that it seems to matter
2. Switch to a different screenset and change your snap to settings to a tick value, doesn't seem to matter which value.
3. Now switch back to the screenset in step 1

Do you see the beat value displayed as a tick value? Albeit the correct tick value i.e. 960 ticks as opposed to 1/4 beat

*****Now the bit that crashes Sonar for me******

Switch screensets to the screenset in step 2.

Did it crash?

I can consistently crash it. I've only had one crash that I can remember in all the time I've been running X1 but I've ramped that count up to about 6 trying to pin this bug down.

Thanks in advance for anyone brave enough to try it.

A quick bump and also to add that the crash only seems to affect my x64 system. The x32 just resets the snap to a beat value when changing back to that screenset.

The screenset I thought was inaccesible I can get to but I have to change one of the screensets with a beat value to a tick value first. If I don't do that - crash down she goes.

No crash here on x64 system

The tick bug has been confirmed by CW. It seems the crashing may be unique to the way I have my screensets set up. They now have a copy of my normal template and a dmp file for further investigation.

If anyone else is seeing this problem and can't switch to a screenset because of it, all you need to do is change the initial screensets snap resolution to ticks and then you can swap without the crash.

Ok thanks for that. I also see the beat value selected when clicking on the pop up even though ticks is the display value. The crash for me happens if I change the first screen back to beat and then swap back to the second screenset but as I said it seems it may be something to do with my screensets.

Time and CW will tell. Thanks again.

brundlefly

LANEY


It stays in whatever was last selected unless clicked on
1.set 1 = 1/4
2.set  2 =240 tick
3. go back to 1 and says 960 ticks but when clicked on, jumps back to 1/4 and 1/4 is still selected

every time but no crashes.  did this with a buch of sets and different tick values and always the same

Strange. i did another test with the Normal template (mine's default - I never use it for real projects). And when I go back to the first screenset, it shows the same tick value as screenset 2. 
This is different from both your result, and from my first test result in another project, so it seems the behavior is project-dependent to some extent.

Hi Brundlefly

remember though you said you aren't using per screenset snaps, so the behaviour you are seeing is to be expected. If you want to use per screenset snaps you need to set the variable IncludeSnapInScreenset=1 in your ini file. The default is to have one global snap value.

CWBRN-5824, Snap displays inconsistently when changing screensets (Different snap per SS)

Now "Submitted to Development", the crash seems to be specific to my screensets, although CW haven't said as such yet.

Thanks for the help confirming it.