In Chrome's developer tools, the console displays clickable links pointing to specific lines in JavaScript source files, such as where an exception was thrown.
Upon clicking such a link, the respective file is automatically opened and the line in question is scrolled into view. Furthermore, this line is highlighted with a yellow background ... for a moment. This highlighting quickly fades away. I am working with huge bundled files, and by the time the bundled file is displayed, the highlight sometimes has already completely disappeared.
How can I prevent this fade-out effect, in order to gain more time to do something with the line while it's still conveniently highlighted?
Related
Recently, I wrote a block of code, and tried to copy and paste some functions around the code. But when highlighting the block of code I am trying to select, it exhibits strange behaviour. The first picture is the faulty case, and the second picture is the normal case.
First of all, I can click anywhere on my script even though I dont have spaces there.. if that makes sense (sorry I cant explain it any other way). Second, when I drag my mouse up, it drags up for only that section. Looking at the faulty screen shot, if I were to copy that block, it would only copy the parts in blue... Normally when I drag my mouse up, it automatically highlights the whole line as seen in the normal picture. Also, notice the giant white line on the faulty highlighting compared to the normal highlighting. I am wondering how I can go back to my old normal highlighting...
I think I was able to reproduce the problem by enabling column selection mode.
Try going to Edit-->Column Selection Mode. Uncheck it. If this was the problem, perhaps it was a finger flub which performed a shortkey operation.
So when using Qt to build user interfaces, you all know that .ui files (forms) open in Designer mode by default, and that if you manually switch back to the Editor, then this message appears "This file can only be edited in Designer-mode".
Well, for some reason, and at some point, my file now opens BY DEFAULT in the editor, and the message does not show up. Worse, when manually switching to Designer mode, the main editing field is gray and empty and none of my stuff shows up ... Also no scroll bars or anything.
EDIT : actually, it is whichever form was loaded last that appears. And it is editable and all ... only the drop-down menu with the file name clearly indicates that it is MY file that is opened. When I perform an edit, then the edit is performed to this same last-opened form, and is reflected upon compiling. My display remains unchanged to the state that it had the last time that I was able to open it in the Designer.
EDIT : Also, along with the fact that my .ui file now opens by default in the Editor, it is also editable there like any other source file. But edits don't seem to bother, I modified some stuff or added gibberish, and it never showed after compiling nor did the compiler ever complaine ...
What's going on ? What did I do ? I have no crash nor any recent weird events to report ... It just suddenly started happening.
Thanks in advance for any clues,
Charles
how can I change the color of a single line in Eclipse to be able to find it fast while scrolling ? many people are suggesting to download eclipse themes but I am interested in changing the color of a single line to be able to re-find it faster
You can leave this little comment in that line:
// TODO
A small blue rectangle will be shown next to the scrollbar (the same way as your errors and warnings), and you will be able to instanlty find that line by clicking on it.
There was a library issue in a file and after fixing it, the red error mark in the line disappears. But the file, package and the project shows with red error mark.
I refreshed but still get the red mark. How to get those marks removed.
Thanks.
There are two different mechanisms for displaying problems in Eclipse. Annotations are a lightweight mechanism that are bound to an editor, and markers are used for displaying the problems anywhere else (e.g. Package explorer).
If the in-line annotation disappears, but the project error mark does not, it means, the annotations and markers became inconsistent. First you should try to save the files (sometimes the annotations gets removed during editing, while markers are only refreshed on save). Of course, you have already saved (else the refresh would not make any sense), so I guess, some markers got stuck.
To remove that marker, open the Problems view (Window/Open view), and find there the corresponding error marker, then remove it (Delete in the pop-up menu).
When I scroll to the bottom of an open document in the Eclipse editor, the last line is at the bottom of the file. This is a tad annoying when editing code at the bottom of the file / screen.
How can I enable Eclipse to scroll (much like Vim or VS) down far enough that the last line of code reaches the top of the editor window?
I'm asking for the reverse of this question, in Eclipse: How to make Visual Studio editor stop scrolling past bottom of a file?
Considering the current implementation of a Scrollbar, this is not possible.
(See org.eclipse.swt.widgets.ScrollBar.java)
At any given moment, a given scroll bar will have a single 'selection' that is considered to be its value, which is constrained to be within the range of values the scroll bar represents (that is, between its minimum and maximum values).
In the JDT (Java Editor) realm, the range is strongly linked to the number of lines a source file has.
Adding artificial "logical lines" to allows scrolling past the last line would have unintended consequences on many other parts of the JDT, related to displaying informations based on the line number of a source file (like a compilation error red underline).
This is also why there is no soft wrapping in those editors, despite
a 7-years old bug 35779 (one of the most upvoted).
Allowing word/soft wrap in the editor while typing is easy but not enough, a mapping between the model lines and the visual lines must be introduced to e.g. correctly show annotations.
It also introduces various problems that need to be solved, e.g. 'Go to Line': tools like a debugger, compiler etc. will report the model line but a user it will look strange that a different line will be selected than the one entered into the 'Go to Line' dialog
So for now, the SWT scrollbar example is still limited by the bottom of the window: