On Eclipse's Debug perspective, if I pin the Display and Expressions views on the panels, they just disappear some time after the debugging - apparently when Eclipse switches the perspectives again from Java/Java EE to Debug.
Is this really a Bug (or a Feature I didn't get it) or is it some configuration issue? Is there any directions or workaround to make it work? Pinning them again everytime I get into debug is annoying.
I've been having this issue from quite some time on different distributions of Eclipse (right now on JBoss Developer Studio 4.0.0.GA) and on different machines (Windows).
You can save a perspective. I would open debug perspective and pin Expressions and Display views to it and save it(Windows->Save Perspective as) as MyDebug .
And it would get added to the perspective's list and if you use it often you should be able to see it on the top right corner all the time.
Related
How to I remove non-current Eclipse C++ launch configuration?
What I expect is, the RUN directly related to myproject.exe, not pointing to otherproject.exe sometimes. this is misleading and bring up error. So why not let the closed project with its launching configuration, i.e. closedproject.exe be invisible. And It should be automatically visible if I am editing that C++ code?
Yes I did check the menu setting (De-/Selected both tried):
Windows->Preference->Run/Debug->Launching->Launch Configurations:
Filter configuration in closed projects
Filter configuration inc deleted or missing projects
But the closedproject.exe still in the drop down list or sometime even link to current project build.
What did I wrong or what is the correct/clear setting for this? Or maybe pls. help me to understand why multiple project.exe are listed there?
Or it is a Eclipse improve point?
Thanks to #howlger I have found more insights on the toolbar settings of Eclipse.
In general, Eclipse default toolbar lineup are overdone for beginners like me. It should be more concise and turn-up only needed thus more intuitive.
The "Launch Bar" makes it explicit and standing out. But those build/debug functions/buttons are already in basic toolbar set, thus would be redundant or even misleading if people click on the drop-down menu of "Launch configuration", which is also not clean & clear in principal.
For that reason, the Launch Bar could be disable (for beginners):
Preference=>Launching=>Launch bar | right panel=> uncheck
Enable the Launch Bar
The red-squared button of terminate could be useful while debugging and re-build, because the previous malfunctioning RUN & program could still resident in task manager thus prevent further build and turn-up permission error, There helps this "Terminate" button instead of restart Eclipse. BUT as said, this button also in basic toolbar set. But it is often shadowed by the out-standing Launching Bar :-).
It is also possible to fully customize the toolbar (and lock it):
Windows=>Perspective=>Customize Perceptive
Then choose the tool bar items to display.
For the issue of multiple historical "launching configurations", I will report to Eclipse.
I use Eclipse Neon under Windows 10.
I installed a plugin (MonjaDB) using Eclipse Market Place. As I didn't find the plugin to be very useful I uninstalled it using Help->About->Installation Details->Installed Software->Uninstall. Sadly, however, this didn't seem to fully remove the plugin.
I now have a small red square on the right hand side of my workspace in the shortcut toolbar. This cannot be removed using the close option. I went so far as to remove my installation of Eclipse and the .eclipse directory in my home area but after a reinstall the square is still there.
Presumably this means that it is somehow associated with the project in my workspace?? Does anyone have any ideas how to remove this annoying square?
EDIT:
I have noticed two things
The MonjaDB perspective is hanging around somehow and
If I press the little red square on the right it opens an empty tab in the tab set to the right (where mylyn sits) with the title of DB Tree but I cannot remove it.
I have added three screen shots
MonjaDb perspective Partly Active
It seems like your current perspective is the one that was uninstalled. Just try opening a new one via the Open Perspective toolbar button that's close to thevred square, and then you can try right-click > Close on the red square.
At least a part of this is intentional...when the implementation class of a view no longer exists we leave the view 'open' but are supposed to show an "Error Part'. The reason to leave it up is to handle cases where a user has installed a new eclipse and opens his old workspace before installing the extensions. If we were to remove the views the user would have to set up their perspectives again once they had installed the extension.
Note that resetting the perspective won't work because the class implementing IPespectiveFactory no longer exists.
Closing the perspective and opening a new, different, one should work. If the perspective you open has visible views that are no longer available you should just close them.
I started to use the Eclipse Kepler this week and there is a new feature which is annoying me a lot.
When I'm in a Debug Perspective with the source screen maximized, some times, the Debug Screen opens over the source code. This behaviour bother me because the Debug Screen covers the code making it impossible to see.
Anybody knows what do I need to do to disable this feature?
I agree that it's annoying but the behavior as been in eclipse for many years...
You have two options; restore the Debug stack (just hit the restore button on the element in the Trim) or drag the trim element to the right side trim. If you do the latter then even though the Debug view will still open it's less likely to obscure the code.
I often end up with lots of empty panes in Eclipse that can only be minimized but not destroyed. How do I close these?
Update:
In this screenshot you can see two minimized on the upper left and several on the right hand side. In the center are four more. They only seem to be restorable in the Debug mode.
http://img406.imageshack.us/img406/9900/eclipse1.png
this happened to me, too. What worked for me (based on FilmJ and douncon's comments) was to open a class file, then drag that tab over the top of the empty pane.
Select Window -> Reset Perspective. That should reset the current perspective (what you call "mode") to its' initial state, (hopefully) closing all irrelevant views.
Something seems terribly wrong with your Eclipse. Maybe you should reinstall it. It is possible that you installed a buggy plugin.
First of all, what do you mean by pane? Eclipse has:
Windows (Eclipse itself, e.g. instance)
Documents (tabs)
Views (properties, tasks, explorer, etc)
If by 'pane' you mean document editors, you have problems either with your Eclipse version or most likely one of the installed plugins.
Each View also can be closed (except maybe some project types (perspectives) of which I'm not aware). For CDT (C/C++) you can close practically everything.
I'll recommend you download latest Eclipse version with no plugins, extract it to different folder, and check if that happens again. If yes, please explain more in details (like Eclipse version, perspective you are using, any side plugins, etc).
Also a good places are Eclipse community forum, mailing list and bugz :-)
I had the same problem. For me it helped to go into the right perspective and activate the functionality that caused the window in the first place. Once I reactivated the functionality, in my case "QNX Memory Analysis perspective", I was able to close all the windows one by one.
The conclusion is you have to refill the empty windows with content and then you will be able to close them properly.
So, it's really very easy for this to happen, if you open an editor that's incompatible with the existing editor, you can often end up having to place it outside of the tab list in one of your editor panes, then you might clear or copy that, typically while trying to add that view to a tab list.
In any case, what it's done is create a new editor, and all you need to do is drag some file to that empty editor window giving it some form of context, then close it.
I had the same issue. I followed #zvikico, but instead of just resetting, I first reset and then closed all the perspectives. Please follow the following to fix the problem. It worked for me:
Window -> Perspective -> Reset perspective..
After resetting follow below:
Window -> Perspective -> Close All Perspectives
Sometimes when I jump into source code, e.g. from search or when looking up the declaration of something, the Eclipse text editor tries to display nearby long lines by horizontal scrolling. This happens even if the item I jumped to is well within the display without scrolling. I find this rather annoying, so:
Is there a way to disable this? I have searched in vain through all the editor settings.
Specifically, this is about Eclipse CDT, but I suppose the behaviour is the same in JDT.
This seems to happen in other eclipse editors too (like PDT for PHP)
It could have been related with the ScrolledFormText, but the Plugin Spy tells us a WorkbenchWindow class is concerned, as well as an AbstractDecoratedTextEditor, that is in essence an org.eclipse.ui.texteditor.AbstractTextEditor.
The source of that AbstractTextEditor indicates having:
a ScrollLinesAction for vertical scrolling
a TextNavigationAction for settings the cursor and potentially triggering horizontal scrolling
I am not sure how to change that behavior, except by contributing somehow to the active editor identifier (for instance, for java, "org.eclipse.jdt.ui.ClassFileEditor"), and modifying that Action.
I was having the same issue and found these open bugs for it on the Eclipse Bugs:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=314208
https://bugs.eclipse.org/bugs/show_bug.cgi?id=321189
You can prevent it from happening when you switch the Code Folding off and reload the file.
grtz,
T
right click on your eclipse shortcut and choose properties. in compatibility tab choose "windows xp(servicepack 3). http://www.vistax64.com/vista-general/133849-disable-dynamic-horizontal-scrolling-vista.html