scook
Are you using a display setting other than the default in the Windows Control Panel > Appearance and Personalization > Personalization > Display Settings?

Yeah, because I was using the default setting, then to me this is a bug. I can only get it to work with 'smaller', but would prefer to stay on default. Having to fudge this by setting 'smaller' then reducing my FULL HD (Cakewalk recommended) to a lower res just to get the sizing back to default is a workaround, and I think this should be fixed.
 
The key to this I believe is acknowledging that the problem lies with certain controllers, i.e those the indicate they have been selected (Four white corners). That within Prochannel only a couple of Cakewalk plugs are affected, whilst none cakewalk plugs are not affected. Surely this should make identifying the problem easier to fix. Look at how the ones that work, work and apply this coding to those that don't.
 
Pro Channels that Work
Boz +10dB and Dog
Breverb and ReMatrix
Saturation knob
Tape Emulator
Console Emulator
 
Pro Channels that don't work (for me) as expected
Quad EQ (This shows a further exception in the right click select, left hold works)
Compressor
Tube
FX Chain
(This is affecting Track and Console view as well, but I wanted to show the inconsistency applies in the same ProChannel veiw, so should be identifiable) 
 
Outside of ProChannel I can use the Scroll wheel, and in Quad EQ (right click and left hold), but leave no options control the Compressor.

Weird, when I posted post 39 at about 3am here, I swear there was a suggestion from Craig asking is Read Automation was affecting this and to try turning off. But I can't see that post. Maybe I made that up, or am crossed threads, but in case that comment has simply vanished.
 
Turning off Re-Automation doesn't help

For me it only works if I go with the smallest text size on a HD 1920 x 1080 brand new laptop!

Feeling fobbed of by Cakwalk's response
 
"On Windows 8, Smaller is equal to 100% and larger is a percentage higher than 100. If reducing this setting makes it difficult to read what’s on your screen, try decreasing your graphic resolution in Control Panel > Display > Adjust Resolution. The minimum recommended resolution for SONAR and Music Creator 6 Touch is 1280x800"
On windows 8, "smaller" is not the Windows recommended setting.

 
I've asked for feedback on why this only affect cakewalk ProChannels and none of the 3rd Party developed stuff. This is a bug to me and the fact they can look at the 3rd part plugs and see why their own are faulty, means this bug can be fixed and I should not be doing a workaround.
 
I PM'd Hanstheman yeatserday and we are both having the same problems running FUll HD (as recommended by Cakewalk) on Normal resolution (as recommended by Windows) on Laptops. These Laptops are becoming more the common, and smaller makes the screen detail very small on a 15.6" screen.

Cakewalk are saying they I should not use this setting, to prevent the bugs on their modules.

 
But non-cakewalk modules work fine on this setting

 
 

there's definitely something unusual/non-standard about the skylight ui... i remember when i first booted x1, it loaded so slowly i could see the new/skylight stuff being drawn over the top of the old/pre-x ui, particularly the previously-known-as "loop explorer" being re-skinned as the browser... maybe it still works this way, and if you're not using the "preferred" cakewalk resolution ui elements get "out of sync" (fwoabw)?
/speculation
good luck!

Kamikaze
Weird, when I posted post 39 at about 3am here, I swear there was a suggestion from Craig asking is Read Automation was affecting this and to try turning off. But I can't see that post. Maybe I made that up, or am crossed threads, but in case that comment has simply vanished.
 
Turning off Re-Automation doesn't help

I deleted it because after reading about the size change aspect, I realized the automation had nothing to do with the issue so didn't want to confuse matters...but no, you weren't imagining things!

Thank Criag.
 
What's the next best step then? I believe I have demonstrated this is a bug, and a fixable one by looking at why non cakewalk stuff is working, and cakewalk stuff is not. And three users can replicate the results.
 
I kind of feel this isn't being taken seriously, because there is a poor workaround and and we are in the minority.

Kamikaze
Thank Criag.
 
What's the next best step then? I believe I have demonstrated this is a bug, and a fixable one by looking at why non cakewalk stuff is working, and cakewalk stuff is not. And three users can replicate the results.

I know nothing about coding. But I highly doubt that it's a bug in the conventional sense of the word. It may be that Cakewalk uses some particular way of implementing graphics that others do not, and the limitations revealed themselves only when Windows implemented the slider for changing size of all items.
 
I've seen this kind of thing happen before, e.g., M-Audio did some plug-ins a long time ago that implemented graphics differently from others and didn't work with certain graphics cards. My gut feeling is that this isn't a trivial change, and the graphics in SONAR work correctly within the context of how SONAR creates its graphics...but maybe someone from Cakewalk can chime in.

Just focusing on the ProChannel, and forgetting the console view and track view (and being mouse wheel works in those views, so provides something more usable), I can' understand how those making ProChannel Modules can make it work in Default sizing, but Cake can't. Surely they are making them to Cakes protocol?