John
One issue that the keybindings dialog has had and still is that unless you know that a keybinding is is in different areas you may have it only half done. Case in point is the clip reset keybinding. For it to work for both CV and TV you need to go to both places and keybind in both. I can't think of any reason for it being in two places.
Maybe some people want the CV to reset and the TV not to. Who knows?
Actually, I think I can understand the multiple-places methodology, John. And it may be partly related to your comment a day or two ago about how X1 is somewhat more "menu driven". That is, menu driven but not really menu driven. :)
I get the distinct impression that with X1, the developers have taken a direction toward
object oriented programming more than for any prior version of Sonar. If I'm right, then these so-called "menus" can be thought of as more than just mere menus. They are actual "objects", each with their own definitions and properties. Or "contexts," if you will.
I know that even with Sonar 8.5, there were many ways to accomplish a given task. The same is true in X1. But now with Skylight, the UI has a different mode of thinking. You have the different contexts that can each contain a path to the same internal function...for example, the Record Arm button exists on the Inspector, the Track View, and the Console View. They all go to the same place, but now a common button is used. And not just in look and feel;
it's the same button because the button itself may also be an object included in each "bigger object" (CV, TV, Inspector), but let's not go there or peple will be dropping like flies...
Assume for the moment that the Inspector, TV, and CV are "objects" now; that each one contains its own properties; it's own version of Record Arm, which goes to the same place internally. Incidentally, the same would be true of Mute, Automation R/W, and even the volume sliders in the TV, Inspector, and CV....and much much more.
It's heady stuff that will kill brain cells if you let it. It's complicated to implement. I'll bet that's why a lot of bugs could not be fixed in X1. The base functions are still there, but a major part of the application has been rewired.
The benefit is that in the long run, object oriented design/programming (especially for a DAW) would open up a multitude of possibilities and future capabilities. And hopefully the fixing of some of the bugs that folks have been reporting.