FJ Software

FJ
hey! really - what about this problem in post above? you should agree - this IS the problem, tightly related with an end result of sync operation.

Lets' try to analyze current situation.
1.8.6 released version do support at least one additional field:
"Alias". So now MPE syncs 16 fields....
It's a good news - but the bad news are:
When sync process is carrying out - well-known window's form is showing up: named "Confirmation for sync".
And ...

I think there is should a time to analyze what was done and what should be done.
I mean - it would be a really great to know that in your current plans exists a milestone "to add support of the NICKNAME field".

I understand that the timeframe till the ability of final version may be long
BUT my post said that I have some expectation about the concrete steps of the realization of this feature (see words "to suggest next thing").
So as I understand - you can or agree or disagree. If you agree - I am fine ...

ok - maybe we can try to add as an initial point the next thing:
in vCard object nickname should be coded like this:
X-ANDROID-CUSTOM:vnd.android.cursor.item/nickname;NicknameOfTheContact;1;;;;;;;;;;;;;

1 is a enum:
public static final int TYPE_DEFAULT = 1;
public static final int TYPE_OTHER_NAME ...

any comments?

no more actions - no more replies?
is someone DO the support of this forum?
can we expect to get an answer from the dear author?

Hi
I am talking about the support of NickName field of outlook contact.
We for 100% sure know that nickname field IS supporting from android 2.3.x
but your program for some abnormally unbelievable reason is not supporting this field during the sync operation.
WHY? And how long we should wait till ...