Other changes in 7.0 I don't really like

While I'm in this post upgrade funk I find myself not caring for the changes/visuals for debug/run much. The tabs for multiple running contexts are very hard to make out when coloured like the titlebar.

The debug panel feels very cramped now. Its mock-dockable, things can float but not dock? very odd choice. So I can't recreate the minimal 6.0 look and am forced to waste space on all those tabs.. do you all have 22" monitors at Jetbrains? The close icon (X) being moved to the last (second to last) on the control toolbar also irks as its dropping off my screen and its the one I click most often.. Just feels like a step back, the changes add nothing, just detract for me. Would've liked a 6.0 look&feel option on the layouts.

Liked the ability to disable plugins, but still having to restart makes it gimmicky. Also the enabled/disabled states have been reset for me at least once by plugin installs/removals (jetgroovy?) Seems I can order by name by clicking on the table header, but not order by enabled state?

Some of these plug-in selections I'd like to be project preferences, but I guess thats some way down the road.

6 comments

I too thought the debug area had become a little crowded. However, I discovered you can double click any tab to make it fill the entire space or 'hide' a tab (ctrl-alt-backspace) to effectively minimize it within the debug area. This helps in my opinion.

0

I'm not so sure about that. You tend to need at least two controls; frames and variables because the debugger controls are now attached to the frames tab. These used to be globally available to all tabs. To me any layout that hides important functions is wrong. You cant share the space with maximise. Also when you've got a tab maximised "select next view" and "select previous view" don't work.. so you can't navigate maximised tabs either.

The only thing to do is let the debug panel take up to half the screen (1024x768) which means I'm pretty limited to editor real estate and making code changes while debugging and hotswapping.. maybe jetbrains is trying to ween me off that habbit ;)

That or get a bigger monitor. Would still prefer a layout that put console on a separate top level tab behind the debugger controls (as it used to be).

Think I hate it even more than I did yesterday.

Message was edited by:
Richard Osbaldeston

0

Richard Osbaldeston wrote:

I'm not so sure about that. You tend to need at least two controls; frames and variables because the debugger controls are attached to the frames tab. You cant do that with maximise. Also when you've got a tab maximised "select next view" and "select previous view" don't work.. so you can't navigate maximised tabs either.

The only thing to do is let the debug panel take up to half the screen (1024x768) which means I'm pretty limited to editor real estate and making code changes while debugging and hotswapping.. maybe jetbrains is trying to ween me off that habbit ;)

That or get a bigger monitor. Would still prefer a layout that put console on a separate top level tab behind the debugger controls (as it used to be).


As a counterpoint- I like the new layout. Previously I found myself
constantly flipping between the different tabs. Having them all on one
saves me time.

I do have a couple of rather large monitors though, so ymmv.

Cory

0

I like the old v6 debug mode too.

Each of the tabs used to take up full horizontal space, and I was only interested in one at a time anyway.

Now when I want to switch between console log and frame I need to move them up and down to get more space.

Jurn

0

Yeah, the debug mode is really bad. It would be fine if you could dock them together to get back to the 6.0 layout. I find this new layout almost unsusable.

0

Agree, I have the feeling that the Debug panel in 6 was friendlier to use. I e.g. tried to move the console to the right of the panel, but that's not possible.

0

Please sign in to leave a comment.