Query: Advanced Search

Allow iteration over all element tags

Handle scene graph items as unique_ptrs everywhere

Fix matching of circular lines

Add a proper interface between scene graph and renderer

Primitive item picking

Place labels on polygons using the polygon centroid

Move the text rotation computation to SceneGeometry as well

Add method to compute a polygon centroid, for label placement

Ignore layers when their value matches the current level

Fix pen style application

Use valid line cap styles

Deal with multi-polygons that contain broken-down outer polygons

Implement lock-screen visibility control on Android

Correctly handle area line width

Add platform section signs

Handle all remaining opacity properties as well

Add a few more landuse styles

Fix MapCSS parser breaking on object type names being used as values

Implement path-following text positioning

Implement support for the text-opacity MapCSS property

Implement MapCSS shield styles

Implement fill-opacity property

Remove hard-coded bounding box

Support an alternative way of specifying layer names

Also filter non-visual relations for determining which levels to show

Fix a few road rendering issues and improve amenity display

Add proper floor level handling

Be more explicit in what we consider an escalator

	Include stories about projects I am a member of.

Rename visibility hint.

Improve stair styling

Add styles for roads

Show more water areas, non-passenger railway tracks less prominently

Implement width calculation for cased lines

Implement MapCSS numeric comparison conditions

Implement scene to geo coordinate mapping

Implement meters to scene unit mapping

Implement styling for cased lines

Implement correct multi-polygon handling

Focus zoom on the current mouse position

Try harder to keep the viewport inside the scene bounding box

Generalize train trip timezone lookup

Remove explicit timezone information from the train station database

Don't copy the style evaluation result

Only enable anti-aliasing when needed

Implement support for MapCSS font properties

Filter out scene graph elements that are out of view before rendering

Remove accidentally committed test code

Prepare for removal of the explicit train station timezone column

Switch from Gares & Connexion (P3104) to SNCF station codes (P8181)

Implement notification grouping on Android

Implement in-layer rendering order as specified by MapCSS

Consider OSM layers for the rendering z-order

Split scene graph by layer

De-duplicate the style application code

Add all 2D styling properties, and implement line cap/join styles

Force the projection test results to integers

Initial version of an OSM/MapCSS-based indoor map renderer

Remove explicit timezone information from airport database

Display rich text notification messages on Android

Add a few more utility methods needed by the station map renderer

Use the new coordinate-based timezone/country lookup in post-processing

Add the generated z-order curve timezone index

Improve diagnostic output in the knowledge db unit test

Fix latitude range computation in encoding parameters

Deal with two special cases of timezones not mapping to exactly one country

Improve the Python timezone equivalence check

Put all encoding parameters into the generated code

In D27989#670416, @kossebau wrote:

minimumSize() becomes deprecated by this, the deprecation macros will
follow once the current users have been adjusted.

IMHO you should add the macros from the start, otherwise it will be only forgotten later, as there is no mechanism to remind you. And without compiler warnings all the remaining users might never learn about it.

I would expect you have prepared patches for some known users already to testdrive the new API for usefulness, so the set of remaining users (in KDE spheres) should be already small. And those not yet withzout a patch, what would be the plan to care for them? In the end it needs to compiler warnings to get other people in the game. After all API is not deprecated without a reason. Being too gentle with warnings does not help anyone in the end.

Store whether we have an unambiguous or equivalent timezone

Filter invalid IANA timezone ids from the 2020a timezone shapefile

Exclude the polar regions from the timezone index

Update to the 2020a timezone db release

Merge branch 'release/20.04'

Fix parsing headers with a name that is a prefix of a well-known header

feat(akonadi): sort agents alphabetically

Try to find an equivalent timezone in the right country

Prefer coordinate over country lookup, if the countries match in both cases

Add a IANA timezone to country mapping

Support API level < 24 as well.

If you don't have commit access I can land this for you, I'd need a name and email address to use in the Git commit though.

Phabricator messed up the path (missing "src/" prefix), with that fixed it does work as expected. The result gets even better with case-insensitive sorting IMHO (d->proxy->setSortCaseSensitivity(Qt::CaseInsensitive);).

Wikidata property proposal has been accepted, the property exists now: https://www.wikidata.org/wiki/Property:P8181
Next step: populate that with data, and replace our use of P3104 with that.

Experimental geo coordinate to timezone mapping

Use both the geo coordinate and the country to determine the timezone

Change the way we store timezones in the static database

Implement support for notification urgency on Android

Advanced Search
Use Results
Edit Query
Hide Query

May 23 2020

May 22 2020

May 21 2020

May 20 2020

May 19 2020

May 18 2020

May 17 2020

May 15 2020

May 14 2020

May 13 2020

May 12 2020

May 11 2020

May 10 2020

May 8 2020

May 7 2020

Advanced SearchUse ResultsEdit QueryHide Query