Files changed (6)
<application android:label="@string/app_name" android:icon="@drawable/icon" android:theme="@android:style/Theme.NoTitleBar.Fullscreen" android:debuggable="true">
For those without a real keyboard, the "move tapping layer" allows play of the game through touch and gestures.
* Back key: Mapped to the escape key. This will allow you to exit menus, requests to input file names and more.
The Android operating system does not allow an application to quit. It should simply minimise, pause and when it's resources are needed, it will be killed automatically. This means that when you Quit from the main menu, it does not kill the application, but minimises it instead.
+Why haven't I addressed a play store comment? Play store comments are a nuisance. Some low rated comments are from people who emailed me, had their problems addressed and never modified the comments. Others are vague on what I should do, and should I manage to work it out and do it, there's little likelihood the comment would be modified. I reply to all emails, and there I can clarify what a user needs fixed.
+Why did you tell me something worked differently in email? I don't have a good memory. This document is the definitive place for correct information.
+Why is this a paid application? Because I have seen the irrelevant and angry comments on free applications in the play store, and I do not wish to waste my time on them. If it were possible to make a free application with no comments, I would make this one immediately. Remember you can compile this yourself for free.
+Why move tapping mode? It was a quick fix for a user complaint before the chance to make a transparent directional arrow overlay came up.
+Why no transparent directional arrow overlay? Because anyone who has asked for one has either been happy with the move tapping mode given further discussion, or with minor additional changes that I have made. No-one has insisted the game needs one. Yes, it should have one, and it will get one, but there's been no demand for it in my email correspondence.
+Why does double tapping not do anything? Because it prevents a number of quick single taps. It just makes single taps, whether on zoomed in tiles, or on the move tapping layer, annoyingly unusable.
+Why doesn't the map area zoom in, while the status bar stay zoomed out? The original Brogue code treats the whole screen as one space for the purpose of building the data to render. There is no clean way, last I looked, to always copy the status bar from the left hand side, and then to zoom in the map separately. This will be revisited as the BrogueX code base evolves over time.
* Bad reviews do not contain enough information about complaints and problems. So email (as well) please!
- If you have a smaller screen and the display appears corrupt, see the Play store page bug list for an explanation/workaround.
-- New "move tapping options" submenu. This allows the user to selectively enable different move tapping layer controls.
-- Added "move tapping" ability to flick in a compass direction as a way to do the corresponding key press.
- Log.i("BrogueX",String.format("setLastKeyboardDevice id=%d name='%s' keyboardType=%d", deviceID, device.getName(), device.getKeyboardType()));
public static native void nativeGestureFling(int touchDevId, float x0, float y0, float x1, float y1);
+ /* http://stackoverflow.com/questions/6599329/can-one-ongesturelistener-object-deal-with-two-gesturedetector-objects */