In VS Code, if I Ctl+click or press F12 on an object defined elsewhere in the file, the focus is moved to that object, but additionally a window opens up showing me exactly what I'm already trying to look at except in a smaller window than I would normally be viewing the object definition. If I instead press Alt+F12, this object definition window opens without moving my focus to the object.
In the case of pressing Alt+F12, this functionality could potentially be useful since it saves me from having to navigate from the code I'm working with. However, in the case of Ctl+click or F12, both navigating away from the code I'm working with and displaying the object definition in a smaller window is not helpful and I want to disable it.
Here is an image of what I'm trying to describe when using Ctl+click or F12:
How do I disable this? I would prefer to only disable the functionality that both shows the window and navigates away, but would settle for disabling showing the window entirely.
This issue has been addressed in version 1.26.1 of VS Code.
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.
How can I tell MATLAB to open a variable (double click, CTRL+D) in the same window as the variable I am already inspecting? Currently, my MATLAB always opens a new inspection window when openening a variable, which gets confusing quickly.
I can send all variables to the same window (with multiple tabs) using "Dock All in Variables", which gives me the desired behavior until I undock one variable. Also, I lose my (maybe intended) separation of variable-inspection-windows.
So I want to be able to have multiple "Variables" windows, where an opened variable of a window is displayed using a tab in this specific window.
I don't know how I accidentally did this but the methods menu in my Eclipse window is too big and I want to resize it back. The menu I'm talking about is the one that pops up when you type a "." after an object and it brings down a list of methods you can use on it. I must have accidentally dragged the menu to large and now I can't drag it back. Does anyone know the name of this menu? Or better yet, how I can resize it back to normal?
This menu can be re-sized like a classic window by putting the mouse pointer at the bottom right of the menu and dragging the mouse to expand or reduce it.
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).