I've recently upgraded to Android Studio 3.3.1 and I have noticed the documentation panel now appears whenever I start typing something or do ctrl-space completion. I can't find a way to stop it doing this; I've undocked it, unpinned it, and specified "remove from sidebar" but it just keeps coming back.
What is the point of "remove from sidebar" if it just reinserts itself as soon as I start typing in the editor?
This would be slightly less annoying if it didn't frequently lock up AS while it attempts to get documentation when I'm editing XML files. It's really annoying and driving me mad.
In case anyone else has this trouble, I found the best solution was to grab the left hand edge of the panel and close it right up against the right hand side of the main window, effectively hiding it.
Untick this, I occasionally enable it via a keyboard shortcut (I think) and the panel pops open when I hover over a method or class.
In Settings > Editor > Code Editing > Quick Documentation
Related
I am losing my mind ...wondering how could the following behaviour be the shipped default user experience in Visual Studio where all technologies involved are Microsoft-made:
use microsoft visual studio (2019)
use microsoft Xamarin.Forms to make an app
run the app in debug mode to see updates in the VS Output window
every new line that comes in through logcat from my phone to VS, force auto-scrolls Visual Studio's builtin Output window to the bottom and there's no way to stop it?!
I have to either: 1. stop running the app and read the output. Or 2. futilely wrestle with the damn scrollbar and fight Visual Studio to try to maintain the output window's scroll on a specific position enough moments to read anything.
How did this get past any internal QA for Xamarin? Did they ever try to, you know, make an app? Am I blind? Is there an easy way to stop auto scrolling? Why isn't it enabled by default? The default behavior should be: if the scrollbar is all the way to the bottom, then auto-scroll, sure. But if the scrollbar has been moved by the user, then stop auto-scrolling for the love of god! (this is common sense in many other software)
Also, there's no button on the Output window that locks the scrolling.
This is a hack not a solution, but it works:
Just Ctrl+F anything in the Output window. As long as and while this is active / has found something, the auto-scrolling will be locked/stopped. (and you can still use the scrollbar manually)
So the functionality IS already in VS. Just MS didn't bother to add a scroll lock button for it, or have a manual scrolling override. Microsoft has this lovely track record of insistently not using their own products in a way that actual human beings (read: not imaginary simple target personas) will definitely need to use them.
Release a Microsoft dev environment that can't have a pausable (readable) Output window? Microsoft: Sure, why not? We don't see the problem here. Why would you ever want to read the output of your application? What an edge case!
Try placing the caret (in the Output window) somewhere other than at the bottom.
If I click somewhere in the output other than at the very end, Visual Studio will stop scrolling to the bottom.
I haven't tried it with an Android/Xamarin project, but I assume the output window behaves the same for all project types.
Place your cursor in output window then
autoscroll on Ctrl+End
autoscroll off Ctrl+Home
When the Android Studio linter warns you about an error (either highlighting it in yellow or underlining in red) you can read about the error by hovering your mouse over the highlight. You can then expand the explanation with ⌘+F1 (on a Mac). Is there a shortcut like ⌘+F1 but for making the linter hint show up in the first place? I'd really like to avoid having one hand jump to the mouse (and hover there for a second, waiting) and jump back every time Android Studio wants to say something.
You can see warning message in the Status bar of Android Studio. See below
Actually, it turns out ⌘+F1 makes the smaller version of the hint pop up, as well. I guess I should've tried that first.
I'm using Android Studio 0.7 and while i normally find it quite pleasant to work with, its logcat support is intermittent at best. Now i've somehow gotten myself into a bit of an interface conundrum. Something i did inadvertently with the Android DDMS window at the bottom has meant that "Devices" and "logcat", which are normally in a two-paned window together (e.g. "Devices | logcat"), have become separate. As a result i can no longer view the filter box and the logcat output without switching panes, which as you can imagine is a real PAIN! (pun unintended but welcomed)
Here are some screenshots - at the top you see two shots of the two panes in their current separated form in v0.7, and below you see what it normally looks like (from v0.8). It's like i've somehow lost the whole header for the individual panes...
I've looked at all the buttons nearby, looked through all the settings, and googled as best i can, and i just can't figure it out. Can anybody help me? At the moment i can only hope that google fixes their developer L preview so i can actually start using 0.8 but who knows how long that will be....
In Intellij IDEA 13.1.5 for Mac, press Fn in keyboard, drag 'Devices' window to 'logcat' window, done!
Click and drag the part I highlighted in Red. When it becomes a separate box, just close it by clicking on the X on the top right.
When doing Android development in Eclipse and running an application, my perspective stays in 'Java' but the LogCat view still opens in the sidebar (the one on the right where the Outline view is).
I don't want LogCat to open, it's annoying. If I want to look at it I can switch perspectives to DDMS.
Go to the Android > LogCat section of Eclipse's Prefereneces window and try adjusting settings in there:
In particular, the bottom two checkboxes look promising for adjusting this behavior.
UPDATE: This turned out to be a bug in R14 of the SDK tools. It has been fixed in R15 which was released on Oct/27/2013. Updating to the latest release solves the problem as suggested in the accepted answer.
I use the LogCat window in the Debug view in Eclipse to diagnose and fix crashes in my code. I've noticed that the LogCat output will automatically scroll down anytime new lines are added (but only after you scroll to the bottom yourself).
This is great if I'm waiting for an exception stacktrace to come up, but extremely annoying if I'm trying to read something in the log and more lines are continuing to be added at the bottom (it keeps jumping to the bottom, so I scroll back to the error, then it jumps to the bottom again).
Is there any way to make it stay where I've placed it, when I place it, but continue to scroll automatically when I reach the bottom?
EDIT: Please note, I'm aware of filters and I don't consider this a solution to the problem.
ANOTHER EDIT: If I scroll up "far enough" from the bottom, it stops scrolling automatically. Far enough might be 5 lines or it might be 500 lines, it seems to be related to how many lines are in the log. Ideally, it would stop scrolling as long as I was at least 1 line away from the bottom.
In the LogCat tab on the upper far right there is a down pointing arrow with a line under it to enable
"Scroll Lock"
On older versions it's a pause button to
"Pause receiving new logcat messages"
That should do the trick!
update to the latest version. the new logcat automatically filters your logs into the app-specific crash logs when you build-launch your app via eclipse.
I stopped having problems disable the option: Automatically enable / disable scroll lock based on the scrollbar position.
Window> Preferences> Android> Logcat> uncheck the option above.
In my case, I'm using Eclipse + Android Developer Tools (Build: v22.6.2-1085508)
I suggest that if I want to use eclipse, download the full package from this link:
http://developer.android.com/sdk/index.html
After downloading, download all available updates, less NDK.
That's not what happens to me. If I scroll up it won't scroll down automatically when new lines come to the logcat until I scroll it to the bottom.
Maybe it's because of the Eclipse or the Android SDK version. I'm using the latest right now.
You can do adb logcat in a shell, and use your terminal app's scroll buffer and scrolling features to manage the logcat output.
Window => Preferences => Android => Logcat
Uncheck the box called:
Display logcat view when there are messages from
an application into the workspace
If you're only debugging crashes, click on the red (E) (error) filter for your main logcat, and keep your filter tab set to default to view all lines that are being reported by your application.
What ends up happening, when your application crashes it stays closed unless requested to restart by your choosing. So, the last lines in the logcat will be the crash report. This is one of the ways of how I debug crashes.
I also think it is "more aggressive" since the latest update! And it actually stops auto-scrolling when I scroll 10 or more lines up.
The best solution I have is clicking in the line you are interested in. If the logcat scrolls down too far and you don't see your line any more just press ArrowUp or ArrowDown to jump back to the line you were looking at.
If you write pid:pidofyourapp (which is written under online column in Device tab) in the search box,it will show the logs you wrote in your application.