Pleco for Android 3.1.2

mikelove

皇帝
Staff member
@Scoox - I moved these here from the 3.1.3 beta thread since they're not really specific to that beta.

Re the icons: those are meant to harmonize with our icon design on iOS; we think they look quite good on that, and if we want to have a consistent branding across platforms - and we do - then frankly it just makes sense to optimize it around the platform where we make 3/4 of our money.

Re the fish icon: it is in fact standard practice, it's codified in Google's own design guidelines for navigation drawers and used in the majority of their apps - Maps is the exception rather than the rule, Drive and Gmail and Photos and Keep all use it just as Play does.

As for the dedicated hardware button: it's used as an actual options menu button in too many other places, using it for the navigation drawer is non-standard - even in Google's own apps on Samsung phones. We have a couple of screens with options menus and we think it's best to maintain the normal behavior on those; using the menu button for some other purpose is confusing.

Wildcard characters are no longer customizable - not sure why we ever brought that option to iOS / Android, actually, it was originally added on Palm OS because certain devices' non-customizable hardware keyboards made it easier to access one punctuation mark or the other. We now use the standard ? for one character and * for multiple characters. Full-text prefix is # as it was before.

With the input bar, that one's a bit befuddling - suggests that tapping on the Done button isn't actually notifying our app that you're finished with input. Which keyboard are you using, the stock Samsung keyboard or another one?

The arrows you're referring to aren't used to move the cursor left / right, they're used to expand / contract the highlighted range. And they should already be at the bottom of the screen - check Settings / Popup Definition, have you turned on "flip bars top/bottom"?
 

mikelove

皇帝
Staff member
Update on the UNI / Edit Entry crashing bug: it's caused by a conflict with the dictionary slider, so as a temporary workaround you can turn that off. Not ideal with Edit Entry but for UNI at least it should only be a minor inconvenience to turn it off, reconfigure your info fields, then turn it on again. (already fixed for 3.1.3, which at this point is mainly waiting for the arrival tomorrow of a test device that we need to sort out one more critical bug)
 
Top