Opened 14 years ago
Last modified 13 years ago
#2596 new bug
One draw too much on switch off
Reported by: | aperi2007 | Owned by: | nobody |
---|---|---|---|
Priority: | major: does not work as expected | Milestone: | Version 1.7.0 |
Component: | MapCanvas | Version: | Trunk |
Keywords: | Cc: | ||
Must Fix for Release: | No | Platform: | All |
Platform Version: | Awaiting user input: | yes |
Description
Starting with a layer switch-on, if the layer is switch-off. The canvas is redraw one time again with the layer switch-on before draw the canvas without the layer.
This is time consuming action if the layer switched-off is a big archive with a large extent.
Change History (7)
follow-up: 2 comment:1 by , 14 years ago
Milestone: | Version 1.5.0 → Version 1.6.0 |
---|
comment:2 by , 14 years ago
I do some tests. It happened even with shapefile.
If I checked the "use cache render" this don't happened.
It don't happened even if I deselect the "use cache render", but set the number of features to draw before updating the display to zero (0).
In effect it seem happened only when this settings is set to some number other than zero.
Infact I usually use as settings 3000 or 5000 features because I have postres with some table very big (1.000.000 features and so on). And use the 0 setting is unacceptable because it mean wait some minutes before to see something (to full-extent). I surely prefer set to 5000 features before drawing to have a feedback of progress of display-ing. But this double redrawing is quite boring.
Now I test better with the use of caching.
Replying to pcav:
Does enabling cache improve this significantly?
comment:3 by , 13 years ago
Awaiting user input: | set |
---|
Can't see that happen at all using Trunk on Linux -- with or without rendering cache.
Can you test with Trunk?
comment:4 by , 13 years ago
Milestone: | Version 1.6.0 → Version 1.7.0 |
---|---|
Platform: | Windows → All |
Platform Version: | 7 |
I'm able to see what Andrea is saying.
*) With render caching enabled, then the "number of features to be drawn before updating the display" does not work anymore. If you refresh the map the vector will be rendered as if the option is set to "0", so I guess that it would be needed to disabled this option when the render caching is enabled.
*) With the render caching is disabled and you choose something different from "0" in "number of features to be drawn before updating the display" (and you are using a vector with many features, I'm testing myself a 50000 polygons vector) then the problem is evident.
Add another (small) vector and then start enabling/disabling it in the TOC, the big vector is continuously redrawn at each click... very annoying.
In general without render caching enabled (and "number of features to be drawn before updating the display" set to 0), enabling/disabling a vector in a project where there are many others vectors, or a few big ones, it takes really a lot.
I'm on trunk/ubuntu 10,04 and with the render caching enabled, on the contrary, it works really smooth.
It the options enabled by default?
comment:5 by , 13 years ago
Now I can see even better:
have a look at the following screencast:
http://www.faunalia.pt/downlaods/redrawns.mpeg
the vectors seems to be redrawn TWICE when toggling editing and it is even redrawn when clicking "Ok" or "apply" in QGIS menus.
Does enabling cache improve this significantly?