I do not want to use the mouse but only the keyboard.
I use a lot the action shortcut to do that, and I remember a number of shortcuts. But when I do a run and get some errors, I find frustrating I have to use the mouse to gain the focus of the Window Tool Build ( the one that is on default without a shortcut into the bottom bar of Android Studio. How can I without the mouse, see the runtime errors, scrolling into the Build tool window?
By the way I experience the same problem with Logcat, I gain via tab the access to the above bar functions of Logcat, but I cannot scroll Logcat
I tried a lot of commands, even giving a shortcut to Build but does not work
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
I am using Android Studio on Ubuntu 16.04. The AVD emulator starts fine, and I can install apks on it. However, if I change to a different workspace, minimise the emulator, or even click on another window, backrounding the emulator, it appears to minimise(only visible in the task bar), and from then on, it will not maximise again. Clicking on it in the bottom task bar makes it appear for a split second before minimising again. I haven't had this problem with any other window. Anyone know how to fix it?
So far I have tried:
Setting the emulator window to always stay on top
answer to install various libs that have helped people with similar AVD problems
Starting the emulator from the command line
For Windows use:
If a window won’t maximize, press Shift+Ctrl and then right-click its icon on the taskbar and select Restore or Maximize, instead of double-clicking on the icon.
I have found a workaround. By clicking into the window menu from the very top left of the emulator window, I set the emulator to both 'always be on bottom' AND always appear in all workspaces. This way, switching workspaces doesn't have any effect on the emulator, and keeping it to the bottom layer means I can open other programs in other workspaces and not have the emulator in the way. I just can't ever minimise it. It's not ideal, but at least I can do my work!
In the bottom left corner of Android studio, there is a squared icon that allows you to see all Panles. it includes also Emulator. By selecting it, I was able to have my Emulator back on screen (view mode: float).
I installed Android Studio 0.8.2
I am not able to get it working with two monitors.
If I have the main application in the left monitor, I want to be able to have the other windows like Event Log,Messages, etc.. docked together in the right monitor.
I can get the windows over to the right, but only if I check floating on the window. And when I do get the window over there to the right, when I click anywhere back on the left monitor, the windows in the right monitor disappear.
I am also not able to figure out how to dock multiple windows together in the right monitor.
I was able to do all of this very easily with Eclipse.
Should I just go back to Eclipse?
Have a look at the official documentation for Tool Windows.
In particular, you may want to refer to the Viewing Modes's Fixed / floating mode section on how to disable transparency for floating windows. Tool windows should not disappear when they lose focus, but they can become semi-transparent.
Additionally, you can have a read through this article which provides a lot of useful information for Eclipse users when switching to IntelliJ IDEA / Android Studio.
If you intent to have dual monitors run android studio.
Open the main screen of AS in your primary monitor.
Select the bar which you want to drag to secondary monitor.
Hit Right click and you should get the following options: Floating Mode, Docked Mode etc..
Select Windowed Mode & you should have a your desired in windows mode
Drag the window to secondary monitor.
Drag the debug window to another monitor, maximize and select Pinned from the settings (gear button top right).
So Pinned mode and Floating mode should be enabled.
With 3.5.0
Just drag the editor tab to the new monitor.
It should turn into a window.
Then you have the main window that holds the docked tool window(s) and a separate editor window.
For Android Studio 3.4.2
Click Window/Active Tool Window/Floating Mode
Now you can drag windows to the second monitor.
This is, by far, the most missed feature for me.
When using eclipse, in the devices view I was able to enable debug for specific app without relaunching.
I can't find such a feature in Android Studio. Relaunching the app all over in the debug mode is real pain. Is there a way to enable it in the middle of the process like it is possible in eclipse?
There is an icon for that on the main toolbar which is called Attach debugger to Android process (highlighted in red in the image below):
The same option can also be found on the Run menu.
Once you click this, a list of processes from attached devices will be displayed. Simply choose the one you want to debug and you're set :)
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.