You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Author Name: Jochen Schwarze (Jochen Schwarze)
Original Redmine Issue: 15892
Redmine category:unknown
In QGIS (2.14.5LTR) when having an svg marker symbol it is not updated when editing it in inkscape and saving it to the same name/location. Even when switching to another svg symbol and then switching back to the one before, the old version of the symbol is displayed and not the one just edited. And simply loading the new version does not work too (the old one is still kept).
Seems to me that there is a QgsSvgCache instantiated when load an svg symbol from file, that is not cleared / updated when load a svg with the same name/location.
Request: Would it be possible to add some sort of 'update' or 'refresh' button to the QgsSvgSelectorWidget that updates the cache when the symbol has changed?
ref. to [[http://gis.stackexchange.com/questions/218978/qgis-update-svg-marker-symbols]]
Author Name: Jochen Schwarze (Jochen Schwarze)
Original Redmine Issue: 15892
Redmine category:unknown
In QGIS (2.14.5LTR) when having an svg marker symbol it is not updated when editing it in inkscape and saving it to the same name/location. Even when switching to another svg symbol and then switching back to the one before, the old version of the symbol is displayed and not the one just edited. And simply loading the new version does not work too (the old one is still kept).
Seems to me that there is a QgsSvgCache instantiated when load an svg symbol from file, that is not cleared / updated when load a svg with the same name/location.
Request: Would it be possible to add some sort of 'update' or 'refresh' button to the QgsSvgSelectorWidget that updates the cache when the symbol has changed?
ref. to [[http://gis.stackexchange.com/questions/218978/qgis-update-svg-marker-symbols]]
The text was updated successfully, but these errors were encountered: