New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dialogs quality problems and consistency : replace "non standard" icons #14
Comments
@nyalldawson, Any idea on why we have both mIconExpression and mIconExpressionEditorOpen? what would be the difference ? |
@DelazJ I the believe one with '...' is supposed to be used for buttons or other actions which open a new expression builder dialog. The other is a generic icon to be used to show that something is set to an expression. |
Trying to add icons where they should be, I'm looking for good practices. Sometimes, same change in two different files do not have same result (icon shown in one and not in the other one).
<resources>
<include location="../../images/images.qrc"/>
</resources> The aim is to have an exemple of what is the optimal code for icon insertion and not overload the file with unneeded matters. <widget class="QToolButton" name="mBrowseButton">
<property name="toolTip">
<string>Browse for action</string>
</property>
<property name="statusTip">
<string>Click to browse for an action</string>
</property>
<property name="whatsThis">
<string>Clicking the button will let you select an application to use as the action</string>
</property>
<property name="text">
<string>...</string>
</property>
<property name="icon">
<iconset resource="../../images/images.qrc">
<normaloff>:/images/themes/default/mActionFileOpen.svg</normaloff>:/images/themes/default/mActionFileOpen.svg</iconset>
</property>
</widget> |
Throughout QGIS, dialogs have quality problems. It would be nice if someone could check all dialogs for the following problems: replacing "non standard" icons. We still have some inconsitently
used icons (such as the expression builder icon) used throughout qgis.
List of icons (to be completed):
The text was updated successfully, but these errors were encountered: