Ah no already logged a bug, because right now the behaviour cannot be as intended, we don't even know what the intended behaviour should be either, we know what not to do, but we don't know what should happen should we  do it ... Cheers :)

Yeah... I can confirm the behavior... I never would have found it as I don't use auto-zoom... for every thing it's good at, it stops so many other things that it just isn't working for me...
 
I've turned it off on all my templates and continue to disable it whenever I stumble on it along with smart grid... ;-)
 
Keni
 

So I logged CWBRN-22660... like this:
 
Autozoom seems to interfere with a LOT of zoom functionality. If certain functionality with autozoom isn't supposed to work "by design" because it is incompatible with autozoom then it should not work at all, maybe instead have a popup (like engine stopped) saying the feature is disabled. Right now it gives the perception that Sonar is buggy when zooming because it does something (and does what is perceived to be the wrong thing generally). On the other hand, if it could work with autozoom enabled it should be fixed.
 
Here is just one example (maybe QA can go through all the scenarios):
 
STEPS Firstly you need to turn on autozoom. If I SHIFT+double-click a clip it is supposed to "Maximize track height":
 
EXPECTED http://www.cakewalk.com/D...q=Introduction.24.html ACTUAL It just shows the track on its own but does not fill the screen as advertised. Is this the documented behaviour in this scenario? Discussion here: http://forum.cakewalk.com/Zoom-shortcut-issue-m2954349.aspx
 
This got withdrawn:
 
Hello,
 There are many ways to zoom in SONAR, auto-zoom being but one of them.We really need more info to investigate an actual scenario here. This report is lacking details and is a bit subjective.
 
I am not surprised as I didn't give clear steps to reproduce, however I was hoping Cakewalk QA department to test out these issues as there are pretty obvious (no I'm not going to write test cases for every scenario here, and nor it seems is Cake QA!  ). So let's all run away from the issue!