Fixed
Status Update
No update yet.
Comments
ca...@hdsoundlab.com
Fixed in CL 9735373
uc...@google.com
Should be available in 4.0 canary 5+
rp...@google.com
#1: I am changing the title of the bug to reflect the fact we will use this bug to track the logcat issue only.
rp...@google.com
#1: Could you provide a screenshot for both AS and Netbeans behavior of the Logcat output, so we better understand your concern. Thanks!
rp...@google.com
#1: Also, feel free to add a comment to this bug with a link to the other bug(s) you opened related to the other issues. We appreciate your feedback!
ca...@hdsoundlab.com
The link to the other issue on display of Java Doc: https://issuetracker.google.com/issues/70201338
Attached two screenshots for Android Studio and NetBeans respectively. From memory, I think you have improved a little, but not enough. It is suggested that one tab is sufficient to make the exception clearly visible.
Attached two screenshots for Android Studio and NetBeans respectively. From memory, I think you have improved a little, but not enough. It is suggested that one tab is sufficient to make the exception clearly visible.
ca...@hdsoundlab.com
I just realized that you had not improved after all, as the indent is a function of the number of columns displayed. Here is a screenshot with more columns,
Description
I would like to report a couple of annoying weaknesses in Android Studio, as compared to e.g. Netbeans or Eclipse. These may be related to Intellij, and if so, please redirect this report accordingly.
These are "old" remarks, so please put someone in charge of correcting these things:
1. LOGCAT INDENT
When an exception is reported, it is indented in a "comic" manner with many many tabs, while it should have been 4-8 spaces only. This makes it mandatory to run logcat in fullscreen to avoid annoying wrap around of text. The logcat in Netbeans does not behave in this way.
2. DISPLAY OF JAVA DOC
Several errors:
a. When displaying api methods popup (upon entering a ".") on a class with available api, the Documentation window will not update unless it is NOT pinned. This is severe because it prevents effective study of an api. When window is floating it kind of works, but the delay could be several seconds. I have defined 500ms.
b. However, even if AS is instructed to read the api documentation directly from local harddrive, it will still spend approx 10 seconds fetching the first document. It should work within the 500ms or so.
c. The positioning of the floating method api window and the Documentation window is very cumbersome. There is a tendency to put windows OVER the line containing the code! Please just take a look at Netbeans on how these two windows are always placed correctly, i.e. never on top of current code line. Also see how fast Netbeans is compared to AS.
d. I could find no feature in the AS settings to define use of JavaDoc on local machine. It should be default to start the search there and always use that version, then with second priority to search online. Why? Because the download manager downloads documents if you prefer and therefore these will always be correct. A new version is coming in automatically.
Hope you agree that a cleanup according to these remarks will improve efficiency for the user of AS. If you do not have Netbeans at disposal, please request screenshots from me for comparision.