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
When using the style manager, you can choose between "Project Styles" or "Default".
Styles are stored in the symbology-style.db under the active user profile see manual and not in the Default profile.
So the use of "Default" in the Style Manager combobox on the top left can be misleading because this style manager setting actually refers to the active user profile and not the user profile "Default", which is the profile name QGIS generates on a new install.
Can "Default" be changed into Active Profile, or perhaps the actual name of the Active profile?
Steps to reproduce the issue
Op the Style Manager and see the combobox on the top left:
Project Styles is fairly self-explainable
Default can be misleading
Versions
<style type="text/css">
p, li { white-space: pre-wrap; }
</style>
What is the bug or the crash?
When using the style manager, you can choose between "Project Styles" or "Default".
Styles are stored in the symbology-style.db under the active user profile see manual and not in the Default profile.
So the use of "Default" in the Style Manager combobox on the top left can be misleading because this style manager setting actually refers to the active user profile and not the user profile "Default", which is the profile name QGIS generates on a new install.
Can "Default" be changed into Active Profile, or perhaps the actual name of the Active profile?
Steps to reproduce the issue
Op the Style Manager and see the combobox on the top left:
Project Styles is fairly self-explainable
Default can be misleading
Versions
<style type="text/css"> p, li { white-space: pre-wrap; } </style>Actieve Python plug-ins
filter_mate
1.8
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.6
processing
2.12.99
Supported QGIS version
New profile
Additional context
No response
The text was updated successfully, but these errors were encountered: