Whenever I hover my mouse over a variable when debugging, I get this extraordinarily useful expression window that lets me see the quantities associated with the object as a whole and/or its sub-objects.
However when I click on any other window outside Eclipse, it immediately disappears and I have to hover back again on the same variable to bring it back.
This is very inconvenient and annoying. Is there a way to prevent this from happening? Basically I want it to go away ONLY if I click on some other area inside of eclipse IDE. Till then I want it to stay put.
Try Window -> Perspective -> OpenPerspective -> Debug.
In the debug perspective you should see a variables tab that shows all current variable values, and it will continue to show even when you click off of the application.
Related
On Mac, in Debug perspective, in Java editor, when I select an expression, for example i < 5 to display the value of the selected expression, the Display pop-up window is supposed to appear and stay. Instead, most of the time it appears and then goes away quickly.
While debugging in eclipse, I find myself using the move hover over variables for a quick snapshot on a variable, which pops up a quick variable view window. When these are structs, there are many members and the window Eclipse puts showing the data is too small to see more than a couple of them.
Is it possible to change the size of this window to make it larger by default? I constantly have to stop and enlarge it to see everything, which defeats the purpose of using it versus the watch window. I've looked at Eclipse settings and searched in google but no luck.
Instead of hovering the variable, I suggest you to double click the variable (or expression) and press Ctrl+Shift+I, it will bring the Inspect Variable popup which you can resize (and it will remember the size the next time you reopen it). Press Esc to close it (or click outside the popup).
Is not as simple as hovering over the variable, but the next time you do this combination to a variable (or an expression) the popup will open with the new size.
I am using Eclipse Juno. I was working in Java perspective and suddenly I minimized the console. I don't know where it went but I am unable to get it back. I even tried to get it from Windows>Show View>Console but I didn't get my console back.
It happened the same thing to me. Just click Window->Reset Perspective and everything will be back as it was when you installed eclipse.
Sure you'll have to customize it back to how you like it, but at least you'll have the console back.
If console is not visible, just search for "Console" in QuickAccess box on the right hand top of menu bar. you can get it back!
Stupid Eclipse. Are there no interface designers volunteering on this project? Why minimize something and make it hard to see where to bring it back? Probably all you have to do is hit Shift-Control-Tab-F9 with one hand while right-double-clicking the lower left hand corner. Hmm, how about a popup when you click a minimized Console that says "We see you've minimized your Console and you are clearly trying to switch to it. Would you like us to restore that so you can actually see it?" followed by "Are you really sure? Cuz ya know, you may be using this click path by accident."
The reset perspective works. Also, you can "Save Perspective" so it's not so hard to go back to your preferred Perspective.
Thanks for the tip.
Bring console to the front from Window -> Show View -> Console. Apparently the console remains invisible (that was the issue indeed), but it is virtually active in the foreground.
Close the current view (i.e. the invisible console) by going to the "Quick Access" box at the toolbar, typing "Close Part", and selecting the respective option on the drop-down.
Reopen console form Window -> Show View -> Console and voilà, it will appear. Drag it to your preferred location on the workbench.
This works for me under the following situation:
I had been previously playing with detaching several views (console included) and editors to a separate window on a different monitor; I have updated my workspace from Neon to Oxygen and I have had a hard reset at my computer. (So, not sure which among those was the reason that made it go wrong).
I wanted to avoid resetting my perspective, as it is highly customised, so I discarded that solution.
Other solutions herein proposed had not worked.
The console was working and the view became visible if I chose a different perspective (e.g. Debug) or a duplicate Eclipse window (which effectively provides a duplicate of a factory-reset perspective).
you could click the small icon on the bottom left and choose console. it will appear.
Whenever the Eclipse quick fix dialogue pops up, all options are visible, but as soon as the mouse is moved to the dialogue the bottom option is hidden by a button saying "Configure Annotation Preferences". To see the bottom option again I will need to scroll down in the dialogue. This happens even if there is only one option in the pop up.
I find this very annoying, since I'm more likely to select a quick fix option than to change some preferences. (Am I the only one?:))
How can I get rid of the button, or at least get the dialogue to resize itself so no options are hidden?
I'm runnig Juno on Ubuntu_64, v12.04.
Change the preference Window -> Preferences -> General -> Editor -> Text Editors -> When mouse moved into hover to "Enrich on click" to work around the issue. Works fine for me on the same Ubuntu setup.
Be warned that this only works for hovers which don't need to be scrolled. If scrolling is necessary to see the content at the bottom, then either clicking into the popup or scrolling with the mouse wheel will still bring up that configuration button. To make this less of a problem, you may want to configure your Java, Lint or other plugins contributing quick fixes to ignore certain types of problems (which you never fix).
Suppose I make a method signature change that breaks several callers, and I want to review the call sites manually to update them.
Once I change the signature, my "Problems" view shows, say, a dozen errors.
What keys can I hit to navigate through them while leaving the keyboard focus in the editor for fast fixups?
(It's been a while, but I think the Visual Studio equivalent is F8.)
Note that this question does not duplicate Eclipse: How to go to a error using only the keyboard (keyboard-shortcut)?, as that one seeks to navigate only between markers in the current file. In this case, I want to go to the next error regardless of which file it's in.
("Marker" is the general Eclipse term for errors, warnings, etc.)
The best I've come up with so far is Ctrl + F7 to flip to the Problems view, then ↓ to pick the topmost error, then Enter to go to it (which returns focus to the editor).
Here's a way to move to the next error, regardless of editor, in one keystroke. It's not perfect, but it works until it's fixed in Eclipse.
Open a "Markers" view. Click the down arrow at the top right, and choose "Configure Contents". Uncheck the show all box, and create the view to show only the problems you want to see. You'll probably want to deselect "warnings" and "errors" as well. Save it.
Click the same "Markers" down arrow, and choose "Group By". Select "None". This is important because you don't want the parent tree level nodes to show, otherwise some of your "next" actions will take you to those, which don't represent an error.
In Eclipse -> preferences -> keys, search for "Markers". If there is not a keystroke bound to the Markers view, create one. I use Ctrl + Shift + M
Get a keyboard hotkey tool like AutoHotKey (for PC's) or iKey for the Mac. I'm using iKey, but there are plenty of other Mac tools you can use. In your hotkey tool, define an action for the keystroke you want to use for "next error". I chose the standard CMD + .
For that keystroke/action in your hotkey tool, generate 3 keystrokes in the following order:
Ctrl + Shift + M
Down arrow
Enter
Of course, you'll want to change the first one to whatever you picked for yours. You'll probably want to restrict that action to be executed only when Eclipse is the current application.
Save that, create some compile errors, and test it.
Try Ctrl + 3 for Quick access popup window.
If the "Markers view" is not already visible, then type in "markers", in the searchbox on the popup window. Once you have selected it, it should stay available, when you press Ctrl + 3 the next time around.
I just had the same problem, after refactoring some parts of code. I had a lot of errors in different files and i had to go through all of those.
I used the following solution:
Mark all (relevant) entries in the Problems view.
To do this switch to the Problems view using Ctrl+F7 and select the entries with Shift+↓/↑
You can also select all entries using Ctrl+A
Open the marked errors by pressing ↵.
Every file containing at least one marked error will be opened.
The cursor will automatically select one error/file, as if you open only this specific entry
Fix the errors in the opened file.
Here you can use Ctrl+. to navigate to next error inside this file
Close the file using Ctrl+W when your done.
Eclipse will automatically focus the next file and you can go back to step 3
In my case this solution was much faster then switching to the Problems view each time.
There's an Eclipse bug entered for this that has an attachment that looks like it does what you want.
You could use AutoHotkey:
save the mouse position, send a mouse event to click on the arrow in CDT console and then return the mouse back to it's original location. Record the mouse coords with window spy or use autohotkey's search by image function (first capture the images of two arrows with printscreen into bitmaps).