Where did Messages go on AndroidStudio 3.2 - android

It's become so second nature that I can't even remember in which window the compile time errors were showing, but I've just updated to Studio 3.2 and I can't seem to find the Messages window or something similar to it.
I'm looking for that panel in which the compile time errors were showing up and you could click on each one and it would jump to that specific file. The only thing I can find is this thing below, on which it's very inefficient to keep expanding the tree and looking at each individual error. Also, clicking on the error items doesn't jump to the file, only if I press Return on my keyboard.
Is this really the replacement of the previous panel? It's very, very inefficient
EDIT
If I click the icon on the left side of the Build panel it displays them as below, but as text ... ! There must be a better way ... isn't there ?

you can see log output in Logcat from tool windows Bar or short key(Alt + 6)
and select Error Filter also i prefer search main word in error filter.
most of time problem appear in top sentences and you can go to location by clicking on link .

Related

What is good way to backtrack a function in your Android app (like a button) to the code that implements it?

I have a project that I did not develop but am trying to fix bugs in. There's a button that I press and then a bug occurs. I want to find out where in the code this button is implemented but its hard to trace it since there are so many classes and layout files. Usually, if there's text associated with the button, then I find the string in my strings.xml file and work my way back. Unfortunately, this button doesn't have any text associated with it.
Hey just connect your actual android phone and run the app on it and also open logcat, when you will click that button logcat should hopefully display all the errors and you can go to the function.
Try this and comment me back if it works
This is a unconvential method, but I used it in the beginning aswell. In Android Studio press CTRL + H to open the Find in Path dialog. This will search the whole project.
For a Button you might want to search e.g. setOnClickListener, Button etc. and navigate it down by this approach. This method will also find dynamically created Views in case it's not in the layout.xml

What's the fastest way to open LogCat view?

Most of the times I run a Project I need to open/maximize LogCat and then minimize it.
Usually it takes a few clicks with the mouse.
Click the LogCat icon on the Debug perspective ctrl+M to maximize it and then click the minimize icon.
Wonder if there is a faster way, hope without the need to click the mouse.
Go to Window -> Preferences.
Then go to General -> Keys.
Find the entry "Show View (View: Logcat)"
Go to Binding and hit a key (such as F10).
Personally, I use two screens for developing. Main Window on the main screen and Logcat, File Explorer and Console on the second one.
Press Shift Twice
Type logcat
Press Enter
If I understand your problem correctly, you already have the LogCat view open. But, when you want to maximize it, its a pain to double click it every time.
Solution:
Use Ctrl+F7 to shift between the views like "LogCat", "Console", "Editor" etc. Then when you are at particular view, just use Ctrl+M to maximize the view in full screen.
I think you will like some of the Shortcuts mentioned here: http://www.rapidsnail.com/Developer/topic/2012/76/27/60320/ask-next-eclipse-the-commonly-used-shortcut-key.aspx
Window -> Show View -> Other -> Android -> LogCat
I personally think Eclipse is not the best place to watch logcat (it is already as heavy as it gets by default, and you put more into it...).
So, I recommend good old command line (Linux):
$ adb logcat -v time
I have created a logcat colorizer to help distinguish the important stuff:
https://bitbucket.org/brunobraga/logcat-colorize

Unable to cmd+click on Java method in Eclipse in Mountain Lion

Yesterday I upgraded from Lion to Mountain Lion and today my productivity went down. I cannot perform "cmd + click" on a method or variable to go its declaration because the popup shown in eclipse contains a horizontal scrollbar which overflows the last option.
Does anyone have a solution how to fix this?
UPDATE: Just to be clear- neither "When Scrolling", nor "Automatically based on mouse or trackpad" options remove the problem for me. Only "Always" does work, but its consequences to the whole system UX are not acceptable
Try doing this. In Mountain Lion, go to Preferences -> General and for Show scroll bars choose Always like so :
That should prevent the scroll bar from covering the last option and allow you to click it. Does this help ?
Update
I just checked that this indeed works. In fact for me it's only the When Scrolling option that creates a problem. With either of the remaining settings, things are peachy :
Unfortunately, I can't post a screen shot since the cmd + click popup disappears as soon as I press the shortcut key for taking a screenshot (Cmd + Shift + 4).
Update 2
I just made this quick screen cast to show the relation between the Mountain Lion Preferences and how it effects eclipse. Take a look at it here.
If you press F3 while the cursor is on a variable or method then Eclipse will 'open declaration'. Fix the problem by removing the mouse-based workflow?

Additional Emulator Command Line Options doesnt appear to be on my Eclipse

Hi I dont have Additional Emulator Command Line Options textbox on my Eclipse and I have to give some parameters from that textbox but it is not there on Run Configuration ->Target is there any other way how can i give those parameters?
Thanx,
I know this is the second similiar post of me, but i thought the previous post i made no one is looking at in.
Are you sure it's not just hidden because your window is too small? There is an outer scroll bar on the very right - try dragging it down, then the text box should appear below disable boot animation

Android avd is off-screen

When I run my Android app in Eclipse I can see the emulator on the toolbar but the window appears to be off the screen. Clicking on the icon in the toolbar makes it flash in or out from the right but I cannot see it.
I have had this problem before but I cannot remember how I resolved it.
You could try this.
or
(Windows 7 only)
Hover over the window icon in the task bar so that the preview appears, right click on the preview and select "move." You should then be able to move the window with the arrow keys. You may have to hold down the arrow key for what seems to be a very long time.
As dell116 said:
Hover over the window icon in the task bar so that the preview
appears, right click on the preview and select "move." You should then
be able to move the window with the arrow keys.
But as soon as you have used one of the arrow keys, then move the mouse, and... voilĂ , the window turns up in front of us, just following the mouse movements. Place the window where you want and click the mouse's left button to release it.
None of the tricks here worked for me. What I had to do was in Windows right click background (desktop) select screen resolution. From there change the resolution to a smaller resolution. The window provided me with the window bar that was cut off, simply drag like normal. After I got it where I got it where I wanted it, I just changed the resolution back.
You can also right click on taskbar->properties change Taskbar location on screen to something else, Apply, and then you can set it back this will put your windows on screen.
Another one is right clicking on the taskbar->Cascade windows - this will put every window together in cascading order which is annoying but it does guarantee all windows will go on the screen.
In Windows 10,I faced the same problem. My solution is like that;
Start Android Studio
Select the Android Studio from ALT+TAB Menu(If'nothing happens,just relax :) )
Now press ALT + Space combination
Click Maximize
Now you may use the ide :)))
I faced the exact same problem. I tried the solutions suggested by Daniel and dell116. At first it did not work as the "Move" option seems to be disabled. However, during my final attempt it worked. I found out that you can only use this method only when the OS is starting up (i.e. when it is showing the android logo).
Good news is that after doing this once, it will stay in the desired position for future runs.

Categories

Resources