-
Notifications
You must be signed in to change notification settings - Fork 29.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Page Up / Page Down in Debug Console #4326
Comments
Fyi I can use page up/down when the debug console contents has focus to navigate up and down. We have commands for the tree and list that cover page up/ page down. |
Still not working for me, this time on build 1.12.2 on Windows 7 (ugh). |
@leegee are you sure that the debug console contents have focus in your case. Namely, the debug console always auto focuses the input. I think we should improve this experience but the point is just to see if this solves the issue for you. |
Does it get focus if I click in it with the mouse?
…On Mon, 29 May 2017, 12:43 Isidor Nikolic, ***@***.***> wrote:
@leegee <https://github.com/leegee> are you sure that the debug console
contents have focus in your case. Namely, the debug console always auto
focuses the input.
In order to focus the tree you need to F1 > Tab Key Moves Focus
Then go to the debug conosle and press shift + Tab -> now pg up, pg down
should be working
I think we should improve this experience but the point is just to see if
this solves the issue for you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4326 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAfTMC54L1aGL3qBzqY5hrvq-6uMrc5Uks5r-qFIgaJpZM4HyJSa>
.
|
@leegee no. It always auto moves focus to the input to make it more convenient in th 90% use case |
Now works for me! Thank you. |
Steps to Reproduce:
Try using page up, page down in the debug console, and instead waste time and patience using using cursor keys or mouse :)
The text was updated successfully, but these errors were encountered: