| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Change-Id: I96513e8b6f09e76998a18edb5411ae06f52cba7c
Reviewed-by: Akseli Salovaara <akseli.salovaara@digia.com>
Reviewed-by: Sergio Ahumada <sergio.ahumada@digia.com>
|
| |
|
|
|
|
|
| |
Also fixing some left overs from 8de152a9e1deb533070663cccf6a98e0d374b1d6
Change-Id: I28a91ca233dd835e6e53efbbd7ebd649461f5c04
Reviewed-by: Lars Knoll <lars.knoll@digia.com>
|
| |
|
|
|
|
|
| |
Change copyrights and license headers from Nokia to Digia
Change-Id: Ie3b9224b2b6a32b417fa0b6643350d45046381e6
Reviewed-by: Lars Knoll <lars.knoll@digia.com>
|
| |
|
|
|
|
| |
Fix license in files having old license.
Reviewed-by: Trust Me
|
| |
|
|
| |
Task-number:QTMOBILITY-1232
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
In particular start expanding on importing and exporting
|
| | |
|
| |
|
|
|
| |
For landmarks sort orders are unlikely to be used since the
most important use case would be to show landmarks on a map
|
| |
|
|
|
|
|
|
| |
The distance sort was deemed to have too much of a performance impact.
While a convenient and useful class, its utility is limited
if it will not be performant. Even if we do says such sort order
has emulated functionality, people may try to use it and be severely
disappointed, which is what we don't want.
|
| |
|
|
|
|
|
|
|
|
|
| |
The QLandmarkFetchHint wasn't really a good place to put the limit
and offset since it implies they can be ignored. The original
intention of the fetch hint was to have a place to put hints
for partial landmark retrieval. This wasn't and explicit
use case placed upon us so we technically don't need it.
If we need to have partial landmark retrieval we could always
add it to the QLandmarkFetchRequest later.
|
| |\
| |
| |
| |
| |
| | |
Conflicts:
plugins/landmarks/sqlite/qlandmarkmanagerengine_sqlite.cpp
tests/auto/qlandmarkmanagerengine_sqlite/tst_qlandmarkmanagerengine_sqlite.cpp
|
| | | |
|
| |/
|
|
|
| |
Also refactor category saving so that category names
must be unique. Expand unit tests to allow for this too.
|
| |
|
|
| |
With regard to naming street is much more clearer than thoroughfare.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit e38ebf00c0b539a7756b21946693e201269b976a.
Conflicts:
examples/telephony/dialer/dialer.pro
src/s60installs/bwins/QtMultimediaKitu.def
src/s60installs/bwins/QtServiceFrameworku.def
src/s60installs/bwins/QtSystemInfou.def
src/s60installs/eabi/QtSystemInfou.def
|
| |
|
|
|
| |
This reverts commit 448d4a4301b7abeb9065aca13b62c70422239b94, reversing
changes made to 815d646dc485b6d15fbddc2814201a5b50be4a85.
|
| | |
|
| |
|
|
| |
The longer names are more readable.
|
| |
|
|
|
| |
This is to be a more accurate description of what those
functions do.
|
| |
|
|
|
| |
Also fix the constructor of qlandmarkcategory to explicitly
initialize members so that the sqlite manager unit tests pass
|
| |
|
|
|
|
|
| |
Filters are now passed by reference and not by pointer.
Modifying filters to have value type behaviour while
also being polymorphic is quite suspect, but seems to
be the least worst option.
|
| | |
|
| |
|
|
| |
This also involved fleshing out the filter and sort classes.
|
| |
|
|
|
|
| |
Can't use system style includes because the include files are not
available at make time. The include files are only available
after make install.
|
| | |
|
| |
|
|
| |
Use a set function instead to a set a single landmark or category
|
| |
|
|
|
|
| |
Because the request results are sorted, using a previousLastIndex
and resultsAvailable() signal to be incrementally notified of new
results does not work, and so should be removed from the examples
|
| |
|
|
|
|
| |
Compile fails because the conveience headers are only installed
after a make install step. Therefore there are missing headers
during the make step.
|
|
|
Also modify qlandmarkfetchrequest, qlandmarksaverequest,
and qlandmarkcategorysaverequest so they are a bit easier to use.
|