- Don't spew a whole lot of "rethrowing expection" log messages on the
default log level
- Don't output tons of duplicate transform error messages - instead
only output the message if its different to the last error encountered
(avoids flooding the console when transform failures occur during
raster projection, resulting in quasi-hangs)
In the case of messy transforms (e.g. transforming global coordinates
to a localized projection) the raster projection setup code can be
very expensive, so add a responsive check to abort early if the
render operation is canceled
* drag'n'drop improvements
part 3
this completely removes hidden config accessible under double click
now a widget groupbox (by opposition to the field config) is shown on top of the right panel
... raster bounds.
Fixes#34435
Unfortunately I wasn't able to write a test for this
case: it seems to be related to a very rare combination
of floating point (double) rounding issues that I could
only reproduce manually.
But since I was trying to test it and I wrote some
raster block test cases, I thought it would be good
to leave them in the PR instead of throwing them
away.
2020-02-14 09:15:00 +01:00
Benjamin Jakimow benjamin.jakimow@geo.hu-berlin.de
Instead of hiding this functionality from users, we instead add an explicit
toggle to the Table Designer dialog "Table" menu to hide or show
the header cells in the designer, and re-add the widgets which
allow users to customise the header appearance back into the
item configuration widget.
Whenever a header cell is selected in the table designer, the formatting
widgets are disabled since the item's header configuration widgets
are used to set the background/foreground color and other properties
of these cells instead.
allow the original path text to be selected and copied, and
make the original path a hyperlink to open the corresponding
folder
Makes it much easier for users to find the correct fixed paths,
e.g. by allowing them to use OS level find files functionality
- "Extract Shapefile encoding": extracts the embedded shapefile encoding
information and lists it for the user (and storing it in output strings
for use in models)
- "Set layer encoding": allows users to set the encoding for a vector
layer to a different encoding (applies to the layer only, no permanent
changes are made to the data source). For use in handling encoding
issues in Processing models
