On master (4633199cc8a466b8a2cfa14ba9d7793dd4c469f4) there are no means to return from the Node window to the main one on Android.
This PR assigns this functionality to the Android back key:
On master (4633199cc8a466b8a2cfa14ba9d7793dd4c469f4) there are no means to return from the Node window to the main one on Android.
This PR assigns this functionality to the Android back key:
909@@ -910,8 +910,14 @@ void RPCConsole::clear(bool keep_prompt)
910
911 void RPCConsole::keyPressEvent(QKeyEvent *event)
912 {
913- if(windowType() != Qt::Widget && event->key() == Qt::Key_Escape)
914- {
915+ const auto close_key =
916+#ifdef Q_OS_ANDROID
#ifdef
. Any way to remap this globally?
One point is that this should be done globally rather than just in rpcconsole
. In our case Qt::Key_Back
and Qt::Key_Escape
will always serve the same purpose.
It also should not be an either-or because Android phones can have keyboards hooked up to them and ChromeOS can run APKs as well.
I guess my suggestion would be something like a global macro/function that checks if its escape or back button. If this is truly the only place where we need to check for the back button then if (event->key == Qt::Key_Escape || event->key == Qt::Key_Back)
is also cool.
Updated fe035a5fd95944f8c654ee46ba3a4aae245560b3 -> a56a1049380b0acb532681484fbb675c3b2ff365 (pr493.01 -> pr493.02). @icota
I guess my suggestion would be something like a global macro/function that checks if its escape or back button.
Done.
I didn’t find other cases when Android back button does not work as expected, but maybe I just missed them.