Fixed
Status Update
Comments
ke...@google.com <ke...@google.com> #2
It's been almost a month now. Is it really that hard to fix? Or has it already been fixed?
du...@google.com <du...@google.com> #3
Unfortunately, this is not as trivial as it may seem.
Logcat tool has a memory-saving feature that kicks in when you close the Logcat tool. When the tool is closed, we disconnect from the device, save the contents of the panel to a disk file and clear the panel. When you open the panel again, we reload the contents from the file and reconnect to the device.
The code right now doesn't handle the state of the scroll-to-end
toggle.
It's possible to do but it's tricky.
In the meantime, if you care more about preserving the scroll-to-end
state than memory usage, you can disable the feature by adding this to your custom VM options:
-Dlogcat.panel.memory.saver=false
du...@google.com <du...@google.com>
an...@google.com <an...@google.com> #4
My computer has had 64GB of RAM for a long time. You should put this setting in the Logcat settings.
And fix this bug! Don't tell me programming is hard for you! You are programmers and should solve any problem!
And fix this bug! Don't tell me programming is hard for you! You are programmers and should solve any problem!
Description
-For leaf nodes, please make clicking on the node trigger this action
-add a shortcut key for non-leaf nodes