- 26 Aug, 2015 3 commits
- 25 Aug, 2015 2 commits
- 24 Aug, 2015 1 commit
-
-
mvogt authored
An invalid address should result in a resolution-to-no-contact event.
-
- 20 Aug, 2015 2 commits
- 19 Aug, 2015 4 commits
- 18 Aug, 2015 2 commits
- 06 Aug, 2015 1 commit
-
-
mvogt authored
When resolving an address that does not need the whole contact to be retrieved, the fetch should include any resolvable addresses of the contact, since address resolution is obviously in use in the caller application.
-
- 04 Aug, 2015 3 commits
- 08 Apr, 2015 4 commits
-
-
chriadam authored
-
chriadam authored
[libcontacts] Fix unit tests
-
chriadam authored
Commit 813eafc0 changed how formatted name (FN) properties from vCards are imported, so that now an import involving de-duplication can result in a single contact with multiple nicknames (setNickname() actually adds nicknames if the new nickname does not match a previously set nickname).
-
chriadam authored
The contact cache provided by libcontacts is intended for use by privileged applications only. Its functionality does not make sense for non-privileged clients, and cannot be tested correctly when run in non-privileged mode.
-
- 06 Mar, 2015 3 commits
- 05 Mar, 2015 2 commits
-
-
mvogt authored
[libcontacts] Some scripts imply name token ordering
-
mvogt authored
For a specific set of character scripts, if a contact's first and last names are entirely composed of that script, then that (most likely) implies a cultural ordering for given/family name tokens that should override the device setting.
-
- 19 Feb, 2015 1 commit
-
-
Richard Braakman authored
Fix UI freeze on first start
-
- 17 Feb, 2015 2 commits
- 16 Feb, 2015 1 commit
-
-
chriadam authored
This commit improves the SeasideImport API by allowing clients to specify their own SeasideContactBuilder implementation when converting the list of Versit documents into storage QContacts. The SeasideContactBuilder allows the client to parametrise things like the contact filter used to determine the subset of mergable contacts, the merge strategy to use, and so on.
-
- 12 Feb, 2015 1 commit
-
-
Richard Braakman authored
Parts of commhistory (GroupManager) will send a stream of resolve requests with many duplicates. This used to be tolerable because requests were handled slowly in the event loop, but now that they have higher priority it has become a problem. I went for the simple solution of ignoring requests that are identical to still-active requests (same uids, same listener, same requireComplete flag). It's not optimal (we could combine more requests into the same backend query if we tried), but it solves the problem without adding a lot of bookkeeping.
-
- 04 Feb, 2015 1 commit
-
-
Richard Braakman authored
This QList was not scanned when unregistering a listener, even though it does contain listener pointers.
-
- 01 Dec, 2014 1 commit
-
-
Richard Braakman authored
-
- 06 Nov, 2014 1 commit
-
-
Richard Braakman authored
[libcontacts] Prioritize requests that make app startup more responsive
-
- 04 Nov, 2014 1 commit
-
-
Richard Braakman authored
change suggested in review by mvogt
-
- 29 Oct, 2014 1 commit
-
-
Richard Braakman authored
-
- 21 Oct, 2014 1 commit
-
-
Richard Braakman authored
This change does not affect normal performance but it guards against bad performance when there are many resolve requests. Thanks to Matthew Vogt for the idea.
-
- 17 Oct, 2014 1 commit
-
-
Richard Braakman authored
resolveAddress requests are done with one query at a time, in order to correlate the results with the looked-up addresses. Doing them sequentially via UpdateRequest events added a lot of overhead in the form of coordination between threads. This commit creates a dedicated QContactFetchRequest for each resolveAddress call, so that the events for starting them can arrive all together in the backend thread and the events announcing the results can arrive all together in the UI thread. They will still be processed sequentially, but this change cuts out the delay between finishing one request and starting the next. In tests with 10k contacts and a recent contacts list with limit=20, this reduced the resolve time from 1s to 0.3s.
-
- 15 Oct, 2014 1 commit
-
-
Richard Braakman authored
-