In some package managers (such as NIX[1], used in NixOS[2]), all the data is
installed into a read-only file system.
When QGis is first launched on those systems, it copies the template
`qgis.db` from the share directory into the user private .local
directory, but keeps its permissions unchanged: readonly. Any attempt
from QGIS to update this file fails.
This commit makes sure that the `qgis.db` file is user writable when it
is copied from the installation directory.
[1] https://nixos.org/nix/
[2] https://nixos.org/
created atlas image sizes
Because the exporter prefers to use the image size when it's
specified (as is done in QGIS app), we need to ignore this
when the aspect ratio of that size doesn't match the aspect
ratio of the page to render.
Fixes#18534
Here's the rules if you want to add more here (developed by
@nirvn and myself)
- Keep colors in the "middle" - avoid too light or too dark colors,
too light colors will make line layers invisible on the
default white background, too dark colors are too visually heavy
for polygon areas
- Avoid over saturated/pure colors, which are too visually heavy. E.g.
- No blues! Blues have a single meaning on maps (water) and we're
almost never going to fluke that a randomly assigned blue color
is given to a water feature layer. So we just avoid blues altogether
as users are almost always going to have to change layers away
from blue anyway.
- Avoid yellow. Yellow is used as the default selected feature color
in QGIS, so keep colors well away from this yellow to avoid confusion
between selected/unselected yellow layers
- Keep things "happy", "positive" and "friendly". No baby puke green/browns
Instead of just showing/hiding the dock, use the toggleUserVisible
method instead. This means that open docks, which are however
hidden behind a different tab, aren't closed, but instead are
brought forward to be user visible.
message log critical/warning messages
These messages are still logged, but the log indicator is not
modified to flag their appearance.
This allows certain error messages to be logged (e.g. on startup)
which cannot be fixed by users/developers (e.g. those caused
by upstream Qt issues, 3rd party Python libraries, etc) but
without flagging them.
Currently, we get so many of these warnings on startup that the
log indicator loses all impact, and newly introduced, VALID
errors go unnoticed/ignored.
