dallasgroot/Gimp
dallasgroot/Gimp
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Gimp/menus/layers-menu.ui

97 lines
5.6 KiB
Text
Raw Permalink Normal View History

menus: implement a bunch of menus in GtkBuilder format. It's not all of them yet, just the ones which work out of the box with current code and which I could easily trigger.
2023-02-23 12:15:40 -08:00
<?xml version="1.0" encoding="utf-8"?>
<interface>
<menu id="/layers-popup">
<submenu>
app, menus: handle the case where a menu is used both as popup and submenu. Several menus can be triggered either as popups on their own when right-clicking the dockable or on items, or as a submenu in the docks main menu. In the former case, we want the menu items to be at the root level, whereas in the latter case, we want them inside a properly named submenu. To handle this, I wrap these in a properly labelled <submenu> in the .ui files, and I add a boolean flag to gimp_menu_shell_fill() which will drop the top submenu if and only if this is the only top item. I use this flag only when using these menus as popup menu on their own. Also fixing a few memory leaks around these pieces of code.
2023-02-28 06:35:12 -08:00
<attribute name="label" translatable="yes" context="layers-action">Layers Menu</attribute>
<attribute name="icon">gimp-layers</attribute>
<item><attribute name="action">app.layers-edit-text</attribute></item>
vectors: Implement vector layers from GSoC 2006 Ports the work done by Hendrik Boom, Martin Nordholts, Gilles Rochefort, and Jacob Boerema to Gimp 2.99/3.0.
2025-03-24 19:39:49 -07:00
<item><attribute name="action">app.layers-edit-vector</attribute></item>
app, menus: handle the case where a menu is used both as popup and submenu. Several menus can be triggered either as popups on their own when right-clicking the dockable or on items, or as a submenu in the docks main menu. In the former case, we want the menu items to be at the root level, whereas in the latter case, we want them inside a properly named submenu. To handle this, I wrap these in a properly labelled <submenu> in the .ui files, and I add a boolean flag to gimp_menu_shell_fill() which will drop the top submenu if and only if this is the only top item. I use this flag only when using these menus as popup menu on their own. Also fixing a few memory leaks around these pieces of code.
2023-02-28 06:35:12 -08:00
<item><attribute name="action">app.layers-edit-attributes</attribute></item>
<submenu>
menus, plug-ins: more tab menu translatability
2023-07-16 07:22:58 -07:00
<attribute name="label" translatable="yes" context="layers-action">Blend Space</attribute>
app, menus: handle the case where a menu is used both as popup and submenu. Several menus can be triggered either as popups on their own when right-clicking the dockable or on items, or as a submenu in the docks main menu. In the former case, we want the menu items to be at the root level, whereas in the latter case, we want them inside a properly named submenu. To handle this, I wrap these in a properly labelled <submenu> in the .ui files, and I add a boolean flag to gimp_menu_shell_fill() which will drop the top submenu if and only if this is the only top item. I use this flag only when using these menus as popup menu on their own. Also fixing a few memory leaks around these pieces of code.
2023-02-28 06:35:12 -08:00
<item><attribute name="action">app.layers-blend-space-auto</attribute></item>
<item><attribute name="action">app.layers-blend-space-rgb-linear</attribute></item>
app, libgimp, pdb: fix perceptual blend space for linear TRC ICC profiles In previous versions what has been stored/specified as perceptual blending or compositing spaces has really been the non-linear variant of the images babl space. To maintain loading of old files, the code has been updated to actually mean non-linear and a new perceptual value has been added to the GimpLayerColorSpace enum, while preserving all old enum values. This change bumps XCF file version to 23
2024-11-29 17:06:53 -08:00
<item><attribute name="action">app.layers-blend-space-rgb-non-linear</attribute></item>
app, menus: handle the case where a menu is used both as popup and submenu. Several menus can be triggered either as popups on their own when right-clicking the dockable or on items, or as a submenu in the docks main menu. In the former case, we want the menu items to be at the root level, whereas in the latter case, we want them inside a properly named submenu. To handle this, I wrap these in a properly labelled <submenu> in the .ui files, and I add a boolean flag to gimp_menu_shell_fill() which will drop the top submenu if and only if this is the only top item. I use this flag only when using these menus as popup menu on their own. Also fixing a few memory leaks around these pieces of code.
2023-02-28 06:35:12 -08:00
<item><attribute name="action">app.layers-blend-space-rgb-perceptual</attribute></item>
</submenu>
<submenu>
menus, plug-ins: more tab menu translatability
2023-07-16 07:22:58 -07:00
<attribute name="label" translatable="yes" context="layers-action">Composite Space</attribute>
app, menus: handle the case where a menu is used both as popup and submenu. Several menus can be triggered either as popups on their own when right-clicking the dockable or on items, or as a submenu in the docks main menu. In the former case, we want the menu items to be at the root level, whereas in the latter case, we want them inside a properly named submenu. To handle this, I wrap these in a properly labelled <submenu> in the .ui files, and I add a boolean flag to gimp_menu_shell_fill() which will drop the top submenu if and only if this is the only top item. I use this flag only when using these menus as popup menu on their own. Also fixing a few memory leaks around these pieces of code.
2023-02-28 06:35:12 -08:00
<item><attribute name="action">app.layers-composite-space-auto</attribute></item>
<item><attribute name="action">app.layers-composite-space-rgb-linear</attribute></item>
app, libgimp, pdb: fix perceptual blend space for linear TRC ICC profiles In previous versions what has been stored/specified as perceptual blending or compositing spaces has really been the non-linear variant of the images babl space. To maintain loading of old files, the code has been updated to actually mean non-linear and a new perceptual value has been added to the GimpLayerColorSpace enum, while preserving all old enum values. This change bumps XCF file version to 23
2024-11-29 17:06:53 -08:00
<item><attribute name="action">app.layers-composite-space-rgb-non-linear</attribute></item>
app, menus: handle the case where a menu is used both as popup and submenu. Several menus can be triggered either as popups on their own when right-clicking the dockable or on items, or as a submenu in the docks main menu. In the former case, we want the menu items to be at the root level, whereas in the latter case, we want them inside a properly named submenu. To handle this, I wrap these in a properly labelled <submenu> in the .ui files, and I add a boolean flag to gimp_menu_shell_fill() which will drop the top submenu if and only if this is the only top item. I use this flag only when using these menus as popup menu on their own. Also fixing a few memory leaks around these pieces of code.
2023-02-28 06:35:12 -08:00
<item><attribute name="action">app.layers-composite-space-rgb-perceptual</attribute></item>
</submenu>
<submenu>
menus, plug-ins: more tab menu translatability
2023-07-16 07:22:58 -07:00
<attribute name="label" translatable="yes" context="layers-action">Composite Mode</attribute>
app, menus: handle the case where a menu is used both as popup and submenu. Several menus can be triggered either as popups on their own when right-clicking the dockable or on items, or as a submenu in the docks main menu. In the former case, we want the menu items to be at the root level, whereas in the latter case, we want them inside a properly named submenu. To handle this, I wrap these in a properly labelled <submenu> in the .ui files, and I add a boolean flag to gimp_menu_shell_fill() which will drop the top submenu if and only if this is the only top item. I use this flag only when using these menus as popup menu on their own. Also fixing a few memory leaks around these pieces of code.
2023-02-28 06:35:12 -08:00
<item><attribute name="action">app.layers-composite-mode-auto</attribute></item>
<item><attribute name="action">app.layers-composite-mode-union</attribute></item>
<item><attribute name="action">app.layers-composite-mode-clip-to-backdrop</attribute></item>
<item><attribute name="action">app.layers-composite-mode-clip-to-layer</attribute></item>
<item><attribute name="action">app.layers-composite-mode-intersection</attribute></item>
</submenu>
<submenu>
menus, plug-ins: more tab menu translatability
2023-07-16 07:22:58 -07:00
<attribute name="label" translatable="yes">Color Tags</attribute>
app, menus: handle the case where a menu is used both as popup and submenu. Several menus can be triggered either as popups on their own when right-clicking the dockable or on items, or as a submenu in the docks main menu. In the former case, we want the menu items to be at the root level, whereas in the latter case, we want them inside a properly named submenu. To handle this, I wrap these in a properly labelled <submenu> in the .ui files, and I add a boolean flag to gimp_menu_shell_fill() which will drop the top submenu if and only if this is the only top item. I use this flag only when using these menus as popup menu on their own. Also fixing a few memory leaks around these pieces of code.
2023-02-28 06:35:12 -08:00
<item><attribute name="action">app.layers-color-tag-none</attribute></item>
<item><attribute name="action">app.layers-color-tag-blue</attribute></item>
<item><attribute name="action">app.layers-color-tag-green</attribute></item>
<item><attribute name="action">app.layers-color-tag-yellow</attribute></item>
<item><attribute name="action">app.layers-color-tag-orange</attribute></item>
<item><attribute name="action">app.layers-color-tag-brown</attribute></item>
<item><attribute name="action">app.layers-color-tag-red</attribute></item>
<item><attribute name="action">app.layers-color-tag-violet</attribute></item>
<item><attribute name="action">app.layers-color-tag-gray</attribute></item>
</submenu>
<section>
<item><attribute name="action">app.layers-new</attribute></item>
<item><attribute name="action">app.layers-new-from-visible</attribute></item>
<item><attribute name="action">app.layers-new-group</attribute></item>
<!--
<item><attribute name="action">app.layers-raise</attribute></item>
<item><attribute name="action">app.layers-raise-to-top</attribute></item>
<item><attribute name="action">app.layers-lower</attribute></item>
<item><attribute name="action">app.layers-lower-to-bottom</attribute></item>
-->
<item><attribute name="action">app.layers-duplicate</attribute></item>
<item><attribute name="action">app.layers-anchor</attribute></item>
<item><attribute name="action">app.layers-merge-down</attribute></item>
<item><attribute name="action">app.layers-merge-group</attribute></item>
<item><attribute name="action">app.layers-delete</attribute></item>
</section>
app: new link layers. These are layers who content depends on another source (right now only an external image). This can be useful when for instance working at several people on a single artwork, hence being able to load new versions of an image without even touching anything in the XCF (for instance, say you draw an animated character while someone else is taking care of the background). Similarly to what we do for text layers, once you start modifying the contents, it turns into a "normal" layer. The link information is still available though, so it is possible to revert to the monitoring state with the menu item "Monitor Linked Image" which appear when a link layer became a normal layer. This is not finale as I'm still experimenting. In particular, I have not implemented XCF saving/loading yet for this new layer type.
2019-07-04 14:49:20 -07:00
<section>
app, menus: vectors -> path in dialog and action identifiers
2025-07-07 07:16:48 -07:00
<item><attribute name="action">app.layers-text-to-path</attribute></item>
<item><attribute name="action">app.layers-text-along-path</attribute></item>
app, menus: new actions layers-rasterize and layers-retrieve. These 2 new actions are meant to be usable on all 3 types of non-raster (and non-group) layers, i.e. link, text and vector layers, to respectively rasterize and un-rasterize them. This will also work with multiple selected layers, and is not specific to one type of layers. I also change how gimp_text_layer_discard() used to work, by marking the text layer as modified instead of actually discarding all text information. The main consequence of this was that a layer rasterized this way was forever lost. Now it can actually be revived as a text layer, not only through the new layers-retrieve action, but also by trying to edit it with the Text tool, which will trigger the same dialog as when a text layer had been rasterized by editing it with a paint tool. Whereas the label of "layers-rasterize" seem to be quite straightforward (simply "Rasterize" per discussions in gimp-ux#252), I am really unsure of the label for "layers-retrieve". Further UX discussions should help on this front.
2025-10-09 10:45:10 -07:00
<item><attribute name="action">app.layers-rasterize</attribute></item>
app, menus: rename layers-retrieve to layers-revert-rasterize. Based on the label, and also "retrieve" was just too generic. It made sense in the context of rasterizable items, but with the more generic "layers" context, it would raise uncertainty.
2025-10-13 08:54:56 -07:00
<item><attribute name="action">app.layers-revert-rasterize</attribute></item>
vectors: Implement vector layers from GSoC 2006 Ports the work done by Hendrik Boom, Martin Nordholts, Gilles Rochefort, and Jacob Boerema to Gimp 2.99/3.0.
2025-03-24 19:39:49 -07:00
</section>
app, menus: handle the case where a menu is used both as popup and submenu. Several menus can be triggered either as popups on their own when right-clicking the dockable or on items, or as a submenu in the docks main menu. In the former case, we want the menu items to be at the root level, whereas in the latter case, we want them inside a properly named submenu. To handle this, I wrap these in a properly labelled <submenu> in the .ui files, and I add a boolean flag to gimp_menu_shell_fill() which will drop the top submenu if and only if this is the only top item. I use this flag only when using these menus as popup menu on their own. Also fixing a few memory leaks around these pieces of code.
2023-02-28 06:35:12 -08:00
<section>
<item><attribute name="action">app.layers-resize</attribute></item>
<item><attribute name="action">app.layers-resize-to-image</attribute></item>
<item><attribute name="action">app.layers-scale</attribute></item>
</section>
<section>
<item><attribute name="action">app.layers-mask-add</attribute></item>
<item><attribute name="action">app.layers-mask-apply</attribute></item>
<item><attribute name="action">app.layers-mask-delete</attribute></item>
</section>
<section>
<item><attribute name="action">app.layers-mask-show</attribute></item>
<item><attribute name="action">app.layers-mask-edit</attribute></item>
<item><attribute name="action">app.layers-mask-disable</attribute></item>
<item><attribute name="action">app.layers-mask-selection-replace</attribute></item>
</section>
<section>
<item><attribute name="action">app.layers-alpha-add</attribute></item>
<item><attribute name="action">app.layers-alpha-remove</attribute></item>
<item><attribute name="action">app.layers-alpha-selection-replace</attribute></item>
</section>
<section>
<item><attribute name="action">app.layers-merge-layers</attribute></item>
<item><attribute name="action">app.layers-flatten-image</attribute></item>
</section>
menus: implement a bunch of menus in GtkBuilder format. It's not all of them yet, just the ones which work out of the box with current code and which I could easily trigger.
2023-02-23 12:15:40 -08:00
</submenu>
</menu>
</interface>
Reference in a new issue Copy permalink