Useful links
Source code of the game - Contribution guide - ATCS Editor - Translate the game on Weblate - Example walkthrough - Andor's Trail Directory - Join the Discord
Get the game (v0.8.12.1) from Google, F-Droid, our server, or itch.io
Source code of the game - Contribution guide - ATCS Editor - Translate the game on Weblate - Example walkthrough - Andor's Trail Directory - Join the Discord
Get the game (v0.8.12.1) from Google, F-Droid, our server, or itch.io
Dialog options behaviour
-
sdevaney
- Site Admin
- Posts: 1187
- Joined: Fri Jan 28, 2011 10:17 pm
- android_version: 14 - Android 14
- Contact:
Re: Dialog options behaviour
Interesting fringe use case issue, but I wouldn't call it a bug. We can not guarantee the functionality of the game when playing through 3rd party services like Bluestacks or by using other input methods not native to the Android OS.
-
Mayweed
- VIP
- Posts: 231
- Joined: Tue Jul 31, 2012 12:12 am
- android_version: 2.1 - Eclair
Re: Dialog options behaviour
I did several tests now and agree with you that this is no bug in Andor's Trail.
The radio button lists worked fine on both native android devices I tested,
regardless of the input method. I even plugged a mouse into that tablet - no problem.
When I said above, that I noticed that behaviour several times, that was apparently
an "out-of-memory-error". Well, almost: the one time I remembered correctly was
an installation of Android-X86 2.2 on virtual box.
I did a test then with a 4.0x version of Android-X86 in a VBox and the behaviour was
the same. Bluiestacks also works with Android-X86 internally. The kernel info of my
dual-boot netbook gives no clue about that, but because it has an Intel CPU I assume
that the Android OS of it is also derived from this source. So I'd say that the bug is
located within Android-X86.
The radio button lists worked fine on both native android devices I tested,
regardless of the input method. I even plugged a mouse into that tablet - no problem.
When I said above, that I noticed that behaviour several times, that was apparently
an "out-of-memory-error". Well, almost: the one time I remembered correctly was
an installation of Android-X86 2.2 on virtual box.
I did a test then with a 4.0x version of Android-X86 in a VBox and the behaviour was
the same. Bluiestacks also works with Android-X86 internally. The kernel info of my
dual-boot netbook gives no clue about that, but because it has an Intel CPU I assume
that the Android OS of it is also derived from this source. So I'd say that the bug is
located within Android-X86.