1.4.1-46-beta3

[Kostya Vasilyev]

https://www.aqua-mail.com/download/AquaMail-market-1.4.1-46-beta3.apk

https://www.aqua-mail.com/download/AquaMail-market-1.4.1-46-beta3.1.apk

^^^ Updated translations: SK, IT

https://plus.google.com/communities/112921486711044378404

https://play.google.com/apps/testing/org.kman.AquaMail

---

+ Bug fixes in swiping

+ Merged fixes from 1.4.0.46

Published to Google Play as a Beta.

---

+ Исправления в новом коде, жесты в списке сообщений

+ Исправления из "основной" версии 1.4.0.46

Опубликована как Бета в Google Play.

[mattran]

Great work as always.
What ever happened to the auto light/dark theme? Really liked that.

[Fcasoli]

I'm a Beta fan now!
How can I find the xmt file to translate to italian?
thanks

[Kostya Vasilyev]

@Fcasoli - I've updated the Italian forum theme with text from the 1.4.1 beta:

http://www.aqua-mail.com/forum/index.php?topic=2216.msg10785#msg10785

In fact, I also updated German, Portuguese, Japanese, and Polish.

[Scott_Miller]

Testing the Tasker plugin. Limited testing, so far. If I match on sender, it works. If I match on subject, it works. If I match on both sender and subject it does not work. Intentional or oversight? Also, is there any form of wildcard support?

Thank you for supporting Tasker.

Scott

[Kostya Vasilyev]

>> If I match on both sender and subject it does not work. Intentional or oversight?

Oversight, I'll take a look

>> Also, is there any form of wildcard support?

The from / to / cc fields are matched by substring (so that a trigger for "john@smith.com" matches "John Smith <john@smith.com>")

The default for subject is exact match, but you can do "sub*", "*sub" or "*sub*" where "*" indicate wildcards.

[Fcasoli]

Italian is done.


http://www.aqua-mail.com/forum/index.php?topic=2216.msg10793#msg10793

ciao

[Kostya Vasilyev]

WOW!

[Scott_Miller]

>> If I match on both sender and subject it does not work. Intentional or oversight?

Oversight, I'll take a look

>> Also, is there any form of wildcard support?

The from / to / cc fields are matched by substring (so that a trigger for "john@smith.com" matches "John Smith <john@smith.com>")

The default for subject is exact match, but you can do "sub*", "*sub" or "*sub*" where "*" indicate wildcards.

I tested again, this time it worked ok. Everything looked like it was matching the first time, but perhaps there was something else I didn't see. I'll continue trying different combinations. As for the matching, that sounds perfect. :-)

Scott

[Fcasoli]

Waiting beta 4

[Scott_Miller]

The default for subject is exact match, but you can do "sub*", "*sub" or "*sub*" where "*" indicate wildcards.

Is this case sensitive? If so, consider treating this like Tasker. All lower case is a case insensitive match. At least one upper case is an exact match. Probably not super important, but would make it consistent within Tasker.

Scott

[Kostya Vasilyev]

Scott - the matching is in my code, not Tasker's, and it uses a database library (SQLite) to do the actual work. Let's stay with how it is for now, and I can revisit if there are any actual issues.

[Scott_Miller]

Scott - the matching is in my code, not Tasker's, and it uses a database library (SQLite) to do the actual work. Let's stay with how it is for now, and I can revisit if there are any actual issues.

So, I understand this to mean it is case sensitive, correct? At least that is my experience with it so far. I do realize the matching is in your code. I never meant to imply anything else. It was only a suggestion. In my opinion, a case insensitive match would be a better choice. I'm only trying to understand the nuances of the pattern recognition, so that I can use it effectively.

Scott

[Kostya Vasilyev]

Actually it should be case-insensitive, at least for US-ASCII (basic English) characters, and it was in my tests...

So please let me know if you're seeing it work otherwise.

One more thing:

The actual matching of messages to event triggers happens once per mail check, a folder or an account.

This means that if there are 10 new messages, and 5 of them match some trigger's conditions, only one event will be generated (for the newest message).

Pent and I discussed how to generate multiple events for this case, he has some ideas, but it has to go into Tasker itself, and he left it for post-4.4.

[Scott_Miller]

Actually it should be case-insensitive, at least for US-ASCII (basic English) characters, and it was in my tests...

So please let me know if you're seeing it work otherwise.

In fact, I am seeing it as case sensitive for subject matching, hence my inquiry. Other fields appear to be case insensitive, but I haven't tested those as much.

The actual matching of messages to event triggers happens once per mail check...

I suspected as much, good to know it may change in the future.



Scott