After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 415796 - Document usage of modifiers in path tool options
Document usage of modifiers in path tool options
Status: RESOLVED FIXED
Product: GIMP
Classification: Other
Component: Tools
git master
Other All
: Normal enhancement
: 2.4
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2007-03-07 18:23 UTC by Raphaël Quinet
Modified: 2007-03-07 20:48 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Raphaël Quinet 2007-03-07 18:23:16 UTC
Currently, the Tool Options tab for most tools correctly shows the modifiers that can be used to change some of the options.  For example, the options for Blur/Sharpen, Dodge/Burn or Zoom show that Ctrl can be used to toggle the mode of the tool.  Similarly, the tooltips for the Mode of all selection tools explain the usage of Shift, Ctrl or Shift+Ctrl.

The options for the Path Tool (vectors tool) do not explain that Ctrl can be used to switch to Edit mode and Alt can be used to switch to Move mode.

In theory, it should be simple to replace:
  o Design
  o Edit
  o Move
by:
  o Design
  o Edit (Ctrl)
  o Move (Alt)

However, looking at app/tools/gimpvectoroptions.c:69, this is not so simple in practice because these options are generated by GIMP_CONFIG_INSTALL_PROP_ENUM(), which takes the strings associated with the enum and does not allow additional help messages to be supplied.  So either these tool options should be rewritten without using the convenience function, or a new function should be added, allowing extra help strings to be supplied for the options.
Comment 1 Sven Neumann 2007-03-07 19:51:27 UTC
2007-03-07  Sven Neumann  <sven@gimp.org>

	* app/tools/gimpvectoroptions.c (gimp_vector_options_gui): describe
	usage of modifiers as suggested in bug #415796.
Comment 2 Raphaël Quinet 2007-03-07 20:48:52 UTC
What a hack!  :-)  But thanks for fixing it.  It works fine.