Yes, the windows behaviour has changed and is also inconsistent. Some open hidden windows now need two presses to reveal them - the mixer, VST instruments, VST connections, etc., whereas others behave as before - Mediabay, Mini Browser.
just wanted to give you all some feedback on this… Strangely the crashing is a lot less or just about like before with 7.04. My system is dedicated for Audio use only, no internet. The last time I updated Windows was about a week before I installed C7.05. So now I’ve been working without any (or few) crashes for about a week.
Anyway its OK now. I’m happy and I can work. Ich guess Cubase needs some time “adjust” itself to the environment 
A lot of plugins that I use require an internet connection in order to activate. I’m curious to know, how do you activate yours? Or is it a case of ‘disable network device’ once activated?
all is good…
Is it just me or is it us MAC users that are having the most issues?
On a non internet machine you need to transfer activation files (like challenge and response files), to an internet connected machine and back, for example, using a thumb drive.
In my case, I have a dual boot setup so all I need to do is move the activation files between the OSs.
And yes, you can also use the ‘disable network device’ once activated’ idea, as you wrote.
Mauri.
Right! 
You got it right. As checking just on this forum it seem been a lot of Apple MAC users that experience all the problems.
Myself have very little problems, some tiny tiny small bugs not even worth to talk about. No show stoppers.
I use the mixer 4 by the way instead of 3.
Note: I have never ever experience a single crash yet with Cubase 7. Not even once or any kind of error message or anything. I use a CMC all controllers too + VST Performer almost everyday up on the internet. No problems, No crashes.
I use and work with Cubase 7 x64, approximately 8 hours daily, almost every day.
What can I say I’m very pleased with Steinberg and Cubase 7. Best release ever and I have never experience any more stable DAW release thru all my years since the mid 80ths. Its stable like CUBASE on ATARI, perhaps even stable.
I have used over the years LOGIC, CUBASE, PRO TOOLS HD, SONAR, DP, SAMPLITUDE, so I have vast experience with DAWs
I’m on own build Machine, Full Tower COOLER MASTER COSMOS case, PC Windows 7 x64 Ultimate, ASUS motherboard deluxe, INTEL CPU, INTEL SSD, SAMSUNG HD’s, NVIDIA GT 640, Seasonic 750 gold PSU, Corsair DDR3 16GB RAM.
Cubase 7 just WORK!!! 
Best Regards
Freddie
All of my license stuff is on a CMstick, an ilock and a Syncrosoft Dongle. I always disable the NIC from BIOS/UEFI. So if I need to update or activate, I enable the NIC, update all which has to be upated and shut down the NIC when finished. The plugins, Cubase and Samp run perfectly without an internet connection.
This isn’t confined to just 7.0.5. I posted on this when C7 first came out. It really annoys me how Steinberg keeps changing things which worked fine in Cubase 6 (and before) and that nobody asked to have changed. Please stop doing this, Steinberg.
The problem is not with the marker track or window, but with window focus in C7 generally, which has changed behavior in C7. (I would say broken)
The Marker track window now has to be frontmost for this to work. In C6, if that window was set to always on top it would automatically be brought forward with the field selected for editing.
While the devs might or might not know about it, it should be posted to the Issues Report forum so it can be confirmed by users and get into the bug fix queue.
Hi all!
This is a wild but probably right guess. It has something to do with Apple- Mac API calls inside OSX Cocoa frameworks.
Apple has very restrict based of codes match only specific apple hardware GPU vendors.
https://developer.apple.com/technologies/mac/cocoa.html
Overall the new graphic are more or less in Steinberg- Cubase 7 directed to use the direct API-calls-; direct from core-level of Windows and OS-X. GPU based coding has many benefits and you find same code in example Windows 7 & 8 AERO.
All graphic you see in Cubase 7 or Nuendo 6 are directed to use the direct API calls to the GPU on the graphic card. It means that all graphic you see, Mixer, meters etc… are NOT using the CPU at all.
That means that it is even more important to not disable any Graphic or disable AERO on Windows 7 /8.
If you do in many cases you will crash any applications and Cubase 7 will not work correctly. Same story on OS-X.
So I think you all should contact Apple and let them know that you experience wide of problems with their cocoa API call’s and Cubase 7.
Hope it help!
Best Regards
Freddie
I’m getting really annoyed over the huge font in the mixer channels.
I’m also getting really frustrated about the problem with opening a VST GUI interface since the update.
It should take ONE easy click. You have to double click to get it open - and sometimes click in the wrong area because of the invisible buttons. Please re-think this. This can be done in a much more intuitive way (E-button!).
Please Steinberg, give us a quickfix soon!
Yeah, I prefer single click to open plugs.
And +1 for removing all hover things, just display them all the time pls!
Mike.
I prefer no clicks… tab/arrow key through the panel, hit enter to open. Or better yet “Select Track Insert 1->x” hot keys. Or better yet a container that cycles the selected plug as you arrow down the insert chain … sigh …
Actually, I’m still waiting for that feature where Cb remembers the plugs opened for each channel and closes and re-opens them as you edit different channels!! But key commands, enter key, arrow keys, yep.
Mike.
+Plus!
Exactly
I just wander why they didnt fix the clicky problem with the latest updates. !!! hope they consider it as a problem and issue !!!
My take is that they have always had a poorly implemented MDI capability. They have now made similar weird choices in how to implement a more modern UI. Now we have the worst of both worlds, with few of the benefits. We have horrible focus control. We have a seemingly bastardized coble between the project and the mixer. It’s almost as if they are independent applications. Even when they finish integrating the new UI, I think all the screwy underpinnings are going to once again limit the functionality of the interface and continue to make simple things overly complex.
Plus I think they all code on and use laptops all day … So, the experience is going to continue to skew that way.
All my opinion of course.
Haha, don’t get me started on MIDI