I've upgraded from X6 and Tabs are driving me insane. I drag in any number of images to view and work on them side by side. What do I need? - auto-resizing, floating windows and all the real estate I can muster.
1) Sure, open images using Open or Open Recent... and if the Option is set to "Open documents in floating window" they will open in floating windows, but drag them in from Windows Explorer and they tab. Can we have consistency here? Better still, can we get rid of tabs?
2) Tabs should be optional. They take up real estate and get in the way of working with multiple images.
3) The snap feature which opens the image to full workspace should also be an option. Why should I have to use Ctrl just to dock windows across the top? Lunacy.
4) no auto-resize of the floating window? Seriously? I mean, seriously? Corel clearly wants me to use tabs, but seriously, no auto-resize of the windows? Really? How many lines of coding must that have saved?
Here's where I'm coming from. I use SolidEdge CAD and when they introduced a revolutionary non-history-based method of creating 3D objects they had the good sense to maintain the old history-based method for those who preferred it. Everybody was happy. Cannot the same be done here and allow floating windows exactly as they were in X6, just for those of us who prefer/need that way of working?
Really, it was an idea from Microsoft, about the compatibilty with Windows 10 capabilities. And yes, at first, it's annoying, but after a while you get used to it and it's familiar. I don't believe they will be back to version 16.0, since we're currently on the version 20.0
Anyway you can undock documents, and leave it floating. Or enlarge to use the entire window.
I agree with Ariel. The tab design was in Microsoft's design specs and is common with most all Multiple Document Interfaces. Corel did the MDI in I believe CorelDRAW 6. You can get it somewhat back the way it was in prior versions along with sizeable windows by setting the windows to Cascade. The tab scenario is used and quite handy when you are working with multiple monitors
I think you make a great point about them having to make some changes to do MDI. Once they've done that, they're not going to go back.
Do you think they could make it possible for the user to have the document window (when using Cascade) automatically sized to fit the content when a document is opened? Or to have a one-click "fit window to content?" capability?
For users who edit lots of small assets, I can imagine that it's really tedious to open a file, then manually resize the document window, then open a file, then manually resize the document window, ...
It's not just tedious to "open a file, then manually resize the document window, then open a file, then manually resize the document window,", but if your mouse moves a bit wrong one of those files snaps to a tab, sometimes tabbed with one of those you've already arranged and then you have to start the whole process over.
I agree that the snap-to-dock thing is also a problem. It's rather aggressive in how far it reaches out to "help" you dock a window when dragging it.
Irrespective of the argument over tabbing, there's no reason why we shouldn't have the option to turn on/off auto-docking and reintroduce auto-resizing. That would help so much. Gargoyle describes what some of us currently have to put up with. It's crazy and so unproductive now as a professional graphics tool.
Question - do developers at Corel ever read these comments? If so, I'd like one of them to decloak and argue these points, show us they at least listen.
aliisa said:Question - do developers at Corel ever read these comments? If so, I'd like one of them to decloak and argue these points, show us they at least listen.
Not as part of their job. Some people will read it as any other user. Not sure if they're allowed to discuss publically about their job.
aliisa said:Irrespective of the argument over tabbing, there's no reason why we shouldn't have the option to turn on/off auto-docking and reintroduce auto-resizing. That would help so much.
You totally understand what I was trying to express!
The developers might have very good reasons for not wanting to go back to "old code" - but perhaps it is not out of reach for them to deliver the most important functionality that you have lost.