Am 11.04.2012 21:51, schrieb Arne Berglund:
On 04/11/2012 12:46, Michael Heydekamp wrote:
Am 11.04.2012 00:36, schrieb Arne Berglund:
On 04/10/2012 15:23, Cor Bosman wrote:
See my response to Cor's message. We may have combined incompatible versions (compose_addressbook 4.0 with RC 0.7.2).
We'll see how it will work with compose_addressbook 0.5b3.
[...]
It was my impression from the beginning that the problem is more at our end...
Keep us posted, Michael. I think we can get this worked out.
Ok, here is an update:
Afer installation of compose_addressbook 5.0b3, item 2) of my initial post in this thread is solved.
The only issue with this plugin still is: It does not honor the "Sorting column" setting under Settings/Address Book - it is always sorting by first name, no matter what.
But that's a minor issue I can live with for the moment. Should be solved some day, though.
OTOH, what is pretty convenient with this plugin: That it DOES honor the fact whether a contact has more than just one mail address (then the entry gets listed as many times as mail addresses do exist for a specific contact).
With regards to item 1) of my initial post, this is solved as well, after we had updated the compose_newwindow plugin from 2.05 to 3.0. Now neither the mail address does get lost nor are upper case chars of the real name converted to lower chars anymore.
Nonetheless there are still two issues with this core function:
- If a contact has more than just one mail address, clicking the "Compose
mail to" button does not allow me to choose between these several addresses. In my case, it takes the "Work" one ("Other" being the, well, other one of two in total).
- To avoid 1), I can click on one of the address links in the "Properties"
tab, but then the real name does not get transferred to the To: field in the compose window (just the address itself).
This is also the case if I disable the setting "compose in new window". It totally escapes me BTW, why I should NOT want to compose a new mail in a new window, as I would otherwise have no access to my entire message base during composing, so this should really become a core function at some stage.
Anyway, comments and help still welcome and appreciated.
Michael Heydekamp Co-Admin freexp.de Düsseldorf/Germany