| Age | Commit message (Collapse) | Author |
|
an actual list view now.
|
|
|
|
Forgot a period at the end. Thanks for pointing that out pauldachz
|
|
settings. Makes the binding description more informative.
|
|
|
|
|
|
SIGABRT however.
|
|
|
|
|
|
In a menu named "Settings" (which is shown in the top left) we have the categories, "CPU Settings" and "Video Settings" - but the fact they are settings pages is already established at this point so it's redundant. Just made them "CPU" and "Video" instead.
Also changed the description for dual-core
They now look like this: http://i.imgur.com/qieaKmL.png
|
|
|
|
there's no need to check if a file is valid or not since they're all valid now.
|
|
|
|
|
|
appropriate packages to make things cleaner.
|
|
|
|
need to be here since the things they were used for took very, very little time to load.
|
|
being a single view with settings from all components being displayed, I have broken it into sections. This future-proofs the settings menu in the sense that it won't get cluttered before people start asking "Hey, shouldn't this be broken into sections?".
As of this commit, it is broken into CPU Settings and Video Settings.
I also simplified the code that is responsible for setting the valid CPU cores and video backends by simply making UI string arrays that get chosen, based on the platform the Android device is running on.
|
|
Added an example translation (Japanese). So now the Android version can both display in English and Japanese, depending on what the Android device's system language is set to.
Also did a tiny clean-up of InputConfigItem.java so that the parameters are slightly more descriptive.
Now, to do a translation in [x] language, all you have to do is take the normal English strings.xml and translate the XML entries into said language, and simply make a folder in the /res/ sub-directory in the form of values-[region code]. IE) With the Japanese translation, it is in the folder /res/values-ja
No configuration other than that is needed. After doing the above, the language should load fine on any device when set to that specific system language.
By default, if a translation file does not exist for a given system language. The app will automatically fall back to using the English translation.
This *should* be bug-free since I did check everything multiple times. But if any issues occur, please report them so that I can fix them.
|
|
library for their navigation drawer support. Overall cleanup.
|
|
|