AquaMail Forum
English - Android => Development builds => Topic started by: Kostya Vasilyev on February 27, 2018, 09:24:24 pm
-
https://www.aqua-mail.com/download/AquaMail-market-1.14.0-802-dev-94e20ef6db19.apk
---
+ All translations are completed
+ Updated the design of "( ... )" on the compose screen when replying / forwarding
---
+ Завершены все переводы
+ Обновили дизайн "( ... )" на экране написания при ответе / пересылке
-
+ Updated the design of "( ... )" on the compose screen when replying / forwarding
Thanks, enabled new editor for testing.
Problem with inserted blank first row in mail body when expanding quoted text, unfortunately persists.
-
Re: Problem with inserted blank first row in mail body when expanding quoted text, unfortunately persists
A newline inserted above the "original" when expanding the "( ... )"?
It "persists" because it's not a "problem" :)
-
Hi
Is there a way of changing the default background and font colours for the new editor? Is there a way of preventing the new editor having a grey background and black text when settings are to use dark theme?
Many thanks.
PS still on 0-780 but will install this release today...
-
Re: Problem with inserted blank first row in mail body when expanding quoted text, unfortunately persists
A newline inserted above the "original" when expanding the "( ... )"?
No, this is not what I wrote ;).
A new line above the "original" when expanding the (...) > This is fine. No problem.
After expanding the (...) automatically putting the cursor in 2nd line while at the same time inserting a new line above the cursor > This is the problem.
User have to manually put cursor back in first line. Every time. This is the problem.
-
Here a screenshot to show what I mean.
-
Yes we insert a blank line above where the "( ... )" was when you tap to expand the "( ... )".
And set the cursor on that blank line.
-
And set the cursor on that blank line.
Why? Users should not write into the first line? :)
It might be "old school", but we like to start to write a message in the first line.
-
Re: Why? Users should not write into the first line?
Not true - you can write anything into the first line, anything at all, in any language you wish.
-
Right. But as I said before: Users habe to manually put the cursor in first line.
I don't understand, why the cursor is positioned in second line by default.
Do users like this default behavior?
-
Re: why
I did post "why" at least twice on this forum and at least once in this very topic.
-
Right. But as I said before: Users habe to manually put the cursor in first line.
I don't understand, why the cursor is positioned in second line by default.
Do users like this default behavior?
No, users (definitely 8) ) don't like to put the cursor back on the first line manually.
-
@mike there is no cursor at all in your screenshots :)
-
@mike there is no cursor at all in your screenshots :)
Unfortunately...
Nevertheless, the cursor is positioned in the "text lines":
first screenshot: in the first (top) line
second screenshot (after tap on the square
) in the second line: the user has to (re)position the cursor back into the first line... mmh 🤔
-
I'll use my imagination :)
-
I certainly hope I'm not going to be forced to reposition to the 1st line prior to typing.
It makes no sense.
Sent from my XT1635-01 using Tapatalk
-
Re: I certainly hope I'm not going to be forced to reposition to the 1st line prior to typing.
No you absolutely are not being forced to do that.
When forwarding (not replying), the cursor goes into the "To" input, you'll have to tap in the "body text" area anyway. This part has not changed compared to earlier app versions.
When replying you can start typing and that's it (the original message will be shown as "( ... )" but will be inserted into your reply). This - that you can just start typing when replying - has not changed either compared to earlier app versions.
That "original" message is shown as "( ... )" is a change.
There are (some) people who absolutely must expand the "( ... )" every time they reply. Yes in this case we put the cursor on a new blank line which we insert just above the now expanded original message.
In earlier app versions (from 2012 to just now) this worked completely differently and there have always been complaints that the original could not be edited without losing its formatting and images.
This (editing original + keeping its formatting and images) is now possible. Lists (bulleted / numbered) and paragraph alignment (left / right / center / justify) too, which were much requested as well.
-
I've been following this "controversy" since its beginning and simply don't understand the problem.
If the cursor does indeed start on the second line of a reply, what's the big deal with having the reply start with a blank line? Or, if you really are adverse to having a blank line at the top of the reply, what's so difficult about tapping one line up? Doesn't seem to me like something worth getting one's panties in a bunch.
Understand that I'm not taking sides here. I'm just trying to understand why it's so important to some folks.
-
There are (some) people who absolutely must expand the "( ... )" every time they reply. Yes in this case we put the cursor on a new blank line which we insert just above the now expanded original message.
Yes, and the question was and still is for this case:
Why do you put the cursor in the new blank line instead putting it in first line at at start?
I can not find the reason here, please tell us.
-
There are (some) people who absolutely must expand the "( ... )" every time they reply. Yes in this case we put the cursor on a new blank line which we insert just above the now expanded original message.
Yes, and the question was and still is for this case:
Why do you put the cursor in the new blank line instead putting it in first line at at start?
I can not find the reason here, please tell us.
Justin, you can find the reason in this post from Kostya:
https://www.aqua-mail.com/forum/index.php?topic=6400.msg38723#msg38723
I believe the way it works right now (again, 778 and newer) is the best middle ground which serves two most common scenarios.
1 - if you just need to look something up, keeping the cursor essentially at the old position, where the "(...)" was, avoids excessive scrolling which might have moved the original now expanded text out of sight (esp. if your signature is "tall");
2 - if your intent with expanding the original message is to add "inline style" reply snippets, you'll have to re-position the cursor anyway so your reply snippets can go into the right places in the original message.
... and in the end, I think it's just a minor issue.
-
1 - if you just need to look something up, keeping the cursor essentially at the old position, where the "(...)" was, avoids excessive scrolling which might have moved the original now expanded text out of sight (esp. if your signature is "tall");
Thanks. This is the case, if somebody already wrote some text. I was writing about a different case, which occurs more frequently, I assume: Expanding before starting to write.
But I see, a change is not wanted.
-
Justin - you are creating confusion (not everyone here realizes that your comments are for a specific narrow case).
For clarify, normal reply "flow" with the new editor (screenshots below).
1 - Before hitting Reply
2 - Right after hitting Reply - the cursor is in first line (not second!) already positioned for you.
3 - Just start typing. When done just tap Send.
4 - To respond inline - you will have to tap to position the cursor and then Enter to break up the original. This has to be a "manual" step - we can't know at what point(s) exactly you'll want to add your inline response(s).
PS - Yay! It's now possible to add / edit text inside the original without losing formatting or images.
-
Justin - you are creating confusion (not everyone here realizes that your comments are for a specific narrow case).
This is why I always wrote about "first line" und "second line" and why I added a screenshot which shows exactly what I mean.
And I think, it's not a specific narrow case. In 99% of my conversations people always write only on top of the quoted message. This is what I do, too (though sometimes I rather would like to reply inline).
I think, many users are working this way (of course not all) after reading a message:
1. Tap on reply ( and see cursor in first line)
2. Expand (...) quoted message to see the original message again
3. Start to write, but hey: Cursor moved in second line, so user has to move it back to start in first line before writing.
-
Re: In 99% of my conversations people always write only on top of the quoted message.
Yes and you can totally do that, please see my screenshots above.
It's not necessary to expand the "( ... )" to make sure that the original (quoted) text is sent. It will be, unless yo delete the "( ... )".
Now yes I understand sometimes you (and others) would like to expand the "( ... )" to look something up.
Yes in this case we make a new line to have a predictable place where we can put the cursor.
I already wrote this maybe a week ago, and @mikeone linked (above) to and quoted from my responses.
Yes it's somewhat unfortunate that we aren't able to keep the cursor position exactly where it was before you tapped the "( ... )".
But at the same time - I really don't think that everyone needs to expand the "( ... )" (to look something up) every single time, with every single reply that he/she ever writes.
When Gmail / web (which I use a lot) started doing the "..." (maybe a year or two ago), it took some getting used to. Now I love it because it keeps the reply's compose area clean and simple.
---
BTW - Gmail (for Android) moves the cursor to the very top of your message, which can be quite far from where you intended to be, farther than you end up in Aqua Mail.
-
Thanks for your effort.
You know what I mean, and I understand your intentions of this behavior. So let it end up here the discussion.
-
https://www.aqua-mail.com/download/AquaMail-market-1.14.0-802-dev-94e20ef6db19.apk
---
+ All translations are completed
+ Updated the design of "( ... )" on the compose screen when replying / forwarding
---
+ Завершены все переводы
+ Обновили дизайн "( ... )" на экране написания при ответе / пересылке
:)
Sent from my XT1032 using Tapatalk