I have Adobe Illustrator CS6 loaded on two machines, XP and Win7 Home 64. Both have the properties set to open as a MAXIMIZED window. When we open a file for the first time, it opens maximized. However, when we open any subsequent files, they open NON-MAXIMIZED. This only occurs when you double click a file to open it and does not occur if we select FILE/OPEN.
Sounds perfectly normal to me. This is related to how workspaces are handled and differentiate between different document window modes. By double-clicking you bypass the workspace context and it opens a *** - just another panel to retain whatever is your current default workspace. Of course this could still be a bug, but if memory serves, it has always been this way ever since CS4 and to me it makes perfect sense. given the limitations both in AI's workspaces and how Windows handles such stuff under the hood...
This has been the case with all Illustrator versions that I can recall and is extremely annoying. If Illustrator is a maximised window then double-clicking any AI/EPS file causes the application to revert to the "normal" window state (whatever size/positon you last set the application window to when it wasnt' maximized/minimized). This does not happen with Photoshop, InDesign, Flash or Dreamweaver if a file associated with those apps is opened by double clicking. The only way to avoid this is using "file->open" which is ain't gonna happen brother. Hasn't anyone at Adobe used Illustrator under Windows?
I never had this happen to me in CS 3, 4 or 5, but all of a sudden it started in CS 6... I have reverted back to CS 5 though for other reasons, but I never did figure out how to stop this from happening.
IT's not possible to enter the maximized state (excuse American spelling) simply by resizing the window - this can only be done by hitting the "maximize" button in the title bar and is quite a differnet thing.
true, Maximized "state" can only be achieved by using the maximize button...is there any difference for your workflow having a window in a maximized "state" as opposed to having it resized manually to fill your screen?
The difference is one way is how it's supposed to work, and the other is not
Having a window pulled into max state I often accidentially grab the program window top and drag it out of position, which you can't do in real maxed state.
It's just one in a long line of CS6 bugs.
Sorry for the late response, I came here by Google searching for the same problem. However, I think the problem is not that one of the document windows resizes, but the application windows resizes (including all open document windows). I have this problem with CS6 and Win7/64. Even worse, after several sessions , the application window opens at a location lower on my screen. I wonder when it runs off-screen. Definitely a bug in my opinion.