Is this a bug or my graphics driver? Anyone else experience this?
 
1. New Project
2. Chose Normal
3. Right-click Control Bar and select "Dock Control Bar at Bottom"
4. Add an Audio Track
5. Select Console View and Undock the window
6. Click on Pan for that track and move mouse wheel back and forth to adjust Pan - it works fine
7. Move the Console window so the Pan control is over the docked Control Bar
8. Selecting the Pan and moving mouse wheel now adjusts the Control Bar in the window underneath not the Pan
9. Right-click the Control Bar and select "Collapse the Control Bar"
10. Now moving the mouse wheel to adjust the Pan does nothing when the Pan control is over the collapsed Control Bar
11. Move the console window up a tad so Pan is above the collapsed control bar and it now works
 
Note - there can be several layers of windows between the Console View and the docked or collapsed Control Bar, also other Views have the same behavior, I chose Console View as an easy example.

Is anyone else experiencing this? Another way to check:
 
1. Dock the Control Bar at the bottom
2. Set All Modules Visible in the Control Bar
3. Click in the Control Bar and mouse wheel back and forth - the modules scroll as they should
4. Overlay another View such as Console View
5. Line up a Fader on the Console View at the same position as the docked Control Bar
6. Clicking the Fader and then scrolling back and forth with the mouse wheel scrolls the docked Control Bar instead of moving the Fader even though Console View is the current active (highlighted) window
7. Move the mouse cursor up slightly above the where the Control Bar is docked and then scrolling with the mouse wheel moves the Fader on the Console View as expected 

Not positive how to upload the pic but here goes:
http://tinypic.com/r/6f1efk/8
 
Click right above the Fader and scroll with the mouse wheel - the Control Bar moves instead of the Fader.
Move the mouse cursor up to around 0 DB and scroll with the mouse wheel - the Fader moves as it should. 

That is called "clickthru" where you click a window and it actually controls the window underneath. Generally this is useful when the foreground window is somewhat transparent.
 
It must be a flaw in the instance you have described.
That's my 2cents.
 
I'll get my coat.
 
 

I appreciate that someone is taking a look...
Here is some more info:
 
1) It does NOT happen on X3e on the same system
2) It happens with X-Ray turned ON or OFF in Preferences
3) I can confirm the same behavior in the following Views:
Console View, Piano Roll View, Browser, Staff View, Event List, Lyrics, Video, Big Time, Markers, Tempo, Meter/Key, Sys/Ex, Navigator, Surround Panner
4) In every case you open a View and overlay over the docked Control Bar. When the mouse cursor is in the current View and above the position where the Control Bar is it scrolls the Control Bar. Move it cursor up it scrolls the current window you are working with. In all cases the current view is active (highlighted blue) and X-Ray if off.
 
A clear example of this is open the Sys/Ex window and click in the Sys/Ex window where the docked Control Bar is located and scroll the mouse wheel. Then click on a sys/ex value above the control bar position. Why would we pass thru or "clickthru" in this case? 
 

Almost 250 views and no one else having this issue? Here is a link to a vid showing the issue with a new blank project and just opening the sys/ex window and scrolling with my mouse wheel:
 
http://tinypic.com/r/35lf213/8
 
The quality is not the best but you get the idea...
 
Notice that I can scroll up and down in the sys/ex window but when I place it over the docked control bar it scrolls the control bar instead of sys/ex when I click a sys/ex value in row 1-3 up at the top.
 
At the end of the video I hide the docked control bar and the nothing happens when I click row 1-3 in the sys/ex window where the control bar used to be and then it starts working again when I click farther down in the window.
When I show the control bar again it then scrolls the control bar instead of the sys/ex values.
 
I also tried 2 different Logitech mice with the Logitech drivers and then uninstalled those and used standard Windows 8.1 drivers and always get the same result.
 
Any feedback would help...
 

You could hit C to close the control bar. I don't see this as a big problem.  I has two monitors anyway. 

Hi John,
 
When I hit C to close the control bar or select View in the Track Window and close the Control Bar the scroll wheel input is disabled where the Control Bar used to be in the top Sys/Ex window when it has focus. Click farther down in that same window and it starts to work again. That is what I was trying to demonstrate at the end of the video.  To me that is a big issue especially if it is a view where I am scrolling my mouse to adjust a knob or something.

Ok - I am now convinced this is a major bug unless one of the bakers or someone smarter than me can explain to me why this possibly would be normal behavior.
 
To eliminate my main DAW and it's components, I downloaded Command Center and just Sonar Platinum to a laptop with a Microsoft mouse. The laptop is running Win7 Home Premium 64 bit. I took care to only install Sonar Platinum with none of it's components. This machine had never had any installs of Cakewalk products in the past.
There is no audio interface so that would eliminate any audio driver.
 
I opened a blank project and just brought up Sys/Ex View to test. Nothing else in the project.
 
I still get the exact same behavior. Whenever I overlay a View over a docked control bar the mouse wheel movements are passed through to the Control Bar underneath whenever I am in that area of the overlaid window. I can mouse click to my hearts content in the same are and those mouse clicks are applied to the View I am working with. If I then move my mouse wheel the wheel movements are applied to the Control Bar not the window I am in. Worse, when I hide the Control Bar or press C in the Track View and then click back in the View I am working with NOTHING HAPPENS when I scroll my mouse wheel until I show the Control Bar again and then the mouse wheel scrolls are applied to the Control Bar again not the View or screen component that has current focus.
 
As another test, I opened the Console and added an audio track. I then opened ProChannel for that track. I then moved up to where there was a blank space in ProChannel and moved my mouse wheel. As expected the Components in ProChannel scrolled up and down UNTIL I attempted to scroll in area where the Control Bar was docked underneath. The wheel movements were passed through to the Control Bar even when the Console was full screen.  
 
No one sees this as an issue????

It sounds like it may indeed be a bug. One not many will come across.  None the less, it will still need to be fixed. I would submit a problem report for it.