I've taken a record in my bug thread:
http://forum.cakewalk.com/Outstanding-Issues-as-of-X3D-and-general-comments-m2952585.aspx#2952585
 
See post #1.
 
I'm not getting paid either, but if somebody would like to pay me that would be nice!
 
I agree it's totally frustrating...

I talked with tech support and they can reproduce the problem as described. They also confirm the issue goes back to X2. It's interesting that tech support doesn't really know what QA is doing as they run separate systems. Tech support is going to review this in more detail and it may be re-opened as a bug.
 
The good new is that if you add a couple extra clicks you can avoid this problem. Always undock a dockable component like the browser before you change its location. It worked ok in X1 but X2 and X3 requires the extra steps.

Ah, back on page 1. Did anyone else file a report?
 
I find it strange that it was reproducible by tech support in about 5 seconds but they don't want to call it a bug. At this point the problem has been noted and denied at the same time. Now I know how bugs get into shipping product.

Clearly your steps to reproduce weren't followed originally and were just perceived to be a minor issue probably with graphic card drivers (not worth spending the time on).
 
To be honest this isn't the first example I've seen, I have other issues which have obviously been speed read rather than followed which came up with similar (and clearly wrong) conclusions, This isn't just Cakewalks problem, plenty of software companies behave this way as they're always really really busy. Something has to give occasionally.
 
I agree though, a bug is a bug however minor. It is not a "feature" to be able to see one's screen clearly and correctly.

My steps to reproduce were followed and the tech support person confirmed the problem. In fact, he was quickly able to determine that it was also an issue in X2 while we were on the phone. I assume it will still be a problem in X4 because nobody seems to care.

My last comment was in regards to validation via the Cakewalk problem reporter.
Anyway yes indeed it is odd. Thanks.

I did a follow up on this and find that Cakewalk has closed it without explanation. Others could reproduce it here, and support could easily replicate it but Cake isn't doing anything about it. I don't get it.

Apparently this fixed according to John
http://forum.cakewalk.com/Im-in-love-m3009296.aspx#3009748