AquaMail Forum
English - Android => Development builds => Topic started by: Kostya Vasilyev on August 27, 2014, 01:40:28 am
-
"It's time to admit you love me / The flush of your cheek betrays"...
Oh wait, those lyrics aren't quite right.
"It's time for 1.4.1 to turn into 1.5.0" (Cinderella, hello... hope the 1.5.0 isn't like a pumpkin...).
http://www.aqua-mail.com/download/AquaMail-market-1.5.0-pre1.apk
---
Formerly known as the "1.4.1" branch, this is starting to head towards a "real" release.
But not yet: going to post this build to Play as a "beta".
If no issues, I'll start a staged non-beta rollout of 1.5.0 in a few days.
+ Case-insensitive sort in contact picker and auto-complete drop-down (compose screen).
+ Fixed issue with long recipient list and auto-complete drop-down (compose screen).
+ Fixed issue with message swiping on Android 4.1.
---
Настал момент ветке 1.4.1 называться своим полным именем - 1.5.0.
Скоро будет общий (для всех) выпуск в Google Play.
Но еще не сейчас. Эту версию сейчас выпущу в Play как "бета" версию.
Если не будет найдено ничего серьезного, то через несколько дней начну "выкатывать" (постепенно) версию 1.5.0 для всех.
+ Исправление сортировки контактов в окне выбора и выпадающем списке авто-дополнения (написание сообщений).
+ Исправление проблемы с длинным списком получателей и выпадающем списком авто-дополнения (написание сообщений).
+ Исправление проблемы с пролистыванием сообщений на Андроиде 4.1.
-
I love and appreciate you! You make my life easier with efficient and beautiful handling of my 300 emails or so per day. Thank you sir for the continual updates and improvements...
-
300 a day? Oh my :) And - thanks!
-
This is the AM version I now have installed. (not easy to find out in the settings).
When I start to write a new message, the text is tiny. This is new (this version?) and I can't find where to change it in the settings.
-
And just to clarify:
Adjusting font size with the volume buttons affects the app's UI only.
In other words, it affects how *you* see the message you're writing.
Setting (or not setting) a default font size under "composing and sending" affects what actually gets sent.
In other words, it affects how *others* see your messages.
-
Aha. That's the way it was originally before I tried to correct by setting the font size.
I must have inadvertently hit the down volume bar without noticing. Now all is well. Thanks.
-
If you find this (adjusting font size with volume keys) annoying --- there is a way to turn it off in settings under "look and feel".
-
It's not annoying. I just forgot all about its existence and therefore did not look in its direction to figure out why the font had gotten tiny. It's actually a great idea to have.
Aquamail is terrific. (My memory of its settings is what is deficient).
-
Ah, it's not your memory -- it's the sheer number of settings :)
-
You are correct. Great app.
-
Hey, I really appreciate a number of improvements, particularly file lists and swiping.
However, a contact picker change has caused me significant problems, might be a side-effect of contact case-insensitivity.
that is, when I start typing in a contact name string, it matches not the beginning of a name, but it matches any parts of names, even if the match is in the middle or end of a contact.
For example, "ed" used to produce a list of contacts the began with "ed". Now, it first matches with names like "tom edwards" or addresses that end with ".edu".
This is a major problem for me, since 1) more work to find the right contact, and 2) higher probability I'll pick the wrong name.
Am I missing something obvious (again)?
thanks!
-
As far as I know, the *matching* has not changed in any way, just the result sorting. Especially if we're discussing the drop-down that's right there in the compose window.
-
I just tried reverting the change -- the only difference is sort order.
Matching (filtering) is the same.
On my Nexus 5, there is no subtoken matching when filtering either way (with or without the sort order change) -- but Aqua will highlight matches in the middle of tokens. Doesn't mean that those are matched on (btw, it's the system doing it, not me).
To clarify:
Melinda Elegant
melinda.elegant@gmail.com
Will match if you type "el" (or "El") because "Elegant" (in the name) and "elegant" (in the address) are both tokens that start with "el".
Aqua will highlight like this:
Melinda Elegant
melinda.elegant@gmail.com
But the match is on the last name, not the "el" in "Melinda".
-
Folks, thanks! However, as a certainty, this has changed dramatically.
My hypothesis could be wrong, could be sort order, how would one change that?
(Sorry for delay in response, I thought I'd get an email, when you responded, that an option? )
New question...is there a way to get a new motivation per each new message? (And should I open a new question for that? )
Thanks!
-
The only change was the sort order, from case sensitive, to case insensitive.
I got more than a dozen messages from one user, who made it his life's purpose to prove that sorting all uppercase first (A-Z) and then all lowercase (a-z) is *so terribly wrong*... that I needed to fix it *immediately*.
So here we are. It's now "by number of times contacted in the past, first" + "name, case insensitive, next" (to break the ties).
Hope he is happy now (actually, he then switched to one other thing... but I've been able to ignore that).
Are you saying that sorting Aa-Zz (upper+lower intermixed) is also *terribly wrong*?
So what is *the one true way* to sort contacts?
Not sure what you mean by "get a new motivation per each new message". What is "a new motivation"?
-
I was wrong. My apologies.
The "sort by number of times contacted first" part was indeed broken up to now, since when I made the change for case-insensitive sort.
Should I post a photo of myself beating my head against the wall -- or jumping from a tall building?
If anyone is still reading this, can you try the version below?
http://www.aqua-mail.com/download/AquaMail-market-1.5.0.16.3.apk
-
It's how it was intended to be:
"by number of times contacted in the past, first" + "name, case insensitive, next" (to break the ties).
But it was really -- my mistake late in the 1.5 cycle -- and released now -- like this:
"name, case insensitive"
which is of course really really wrong.
Before the change for "case insensitive", it was:
"by number of times contacted in the past, first" + "name, case sensitive, next" (to break the ties).
-
Correct, eek will not match Greek. It's "starts at token" type of thing.
You have to remember though that it's system code doing the filtering.
-
All works, all appreciated, and thanks!
-
All works, all appreciated, and thanks!
Thanks a lot for your feedback.