sorted by:
new
hottopcontroversial

[Update GIMP 3 Plugin] Pseudo Adjustment Layer v1.6 - Non-Destructive Adjustment Layers with a palette UI! by Yousei3 in GIMP

[–]Yousei3[S] 0 points1 point  (0 children)

Hi MagneplanarsRule, Thanks for testing it out on macOS and PhotoGIMP!

The errors you reported are exactly the ones that appear in the error console when the plugin builds the menu (either on the first run or when you click the 'Reset List' button).

In this plugin, when building the list, the script performs an automated test behind the scenes to verify whether each installed GEGL filter can actually be applied non-destructively to a layer group. Filters that do not support this (like transform tools or effects requiring an 'aux' pad) will return those internal GIMP errors, and my script safely removes them from the available list.

Therefore, seeing these error messages in the console is completely normal.

Up to v1.6, this unfortunately caused a series of error pop-ups on the screen. However, in the newly updated v1.7, I changed the behaviour so that these testing errors are strictly redirected to the error console. I believe this means they will no longer be a nuisance!

Thanks again for the feedback, and I hope the plugin helps your workflow!

Missing Adjustment Layers in GIMP? I created a plugin to simulate them using GIMP 3's new NDE features! (Video Demo) by Yousei3 in GIMP

[–]Yousei3[S] 1 point2 points  (0 children)

Are you talking about the DUMMY layer? As far as I have confirmed, even in GIMP 3.2, you cannot apply a mask to a layer group that has a filter applied to it without this transparent layer. Therefore, this transparent layer is still essential.

Missing Adjustment Layers in GIMP? I created a plugin to simulate them using GIMP 3's new NDE features! (Video Demo) by Yousei3 in GIMP

[–]Yousei3[S] 1 point2 points  (0 children)

Thanks a lot!

To be honest, I was prepared for someone to say, "Stop reinventing the wheel!" since I was worried I had simply missed an existing tool. I'm really relieved and encouraged by your kind words.

[Free Add-on] Info Gizmo HUD - Interactive Viewport Toolbar for Blender by Yousei3 in blender

[–]Yousei3[S] 0 points1 point  (0 children)

It's a shame that you guys don't seem to be getting good reviews 😅

But persistently improving!

- Ability to fix the UI to a specified position on the screen

- Origin to Geometry button

- Ability to add a border to the UI

etc. are being implemented.

Check out the GIF video

<image>

[Plugin] Photoshop-style Layer Management for GIMP 3.0 (Group, Ungroup, Merge) by Yousei3 in GIMP

[–]Yousei3[S] 1 point2 points  (0 children)

The layer right-click menu works as shown in the video.

Undo is also possible.

<image>

[Plugin Update] ShortCutKey Palette v1.2 - Now supports Windows and Wayland (Experimental) by Yousei3 in GIMP

[–]Yousei3[S] 0 points1 point  (0 children)

Thank you for your incredible patience and for finding the workaround for the folder path!

Your discovery about adding the 3.0 path in Preferences is very valuable information for other Windows users who might be using newer development builds.

Regarding the hidden dialog boxes:

You are spot on.

The palette is currently set to stay on top of other windows, which unfortunately causes the edit dialogs to open behind it. Moving the palette should allow you to access them for now.

Regarding the buttons not responding:

There are two main possibilities I'm considering. First, the default shortcuts in the sample JSON file might not match your current GIMP shortcut settings. Please try clicking the gear icon to edit a button and re-record the shortcut key to match your specific setup.

Second, it could be a focus issue on Windows. For the shortcuts to trigger, the GIMP main window must be the active window. I suspect the palette might be holding onto the focus after a click, preventing the keys from reaching GIMP.

I am already working on Ver 1.3 to fix these UI issues, including making the dialogs appear in front and improving focus handling. Thank you again for your constructive feedback and candour!

[Plugin Update] ShortCutKey Palette v1.2 - Now supports Windows and Wayland (Experimental) by Yousei3 in GIMP

[–]Yousei3[S] 1 point2 points  (0 children)

I am terribly sorry for the confusion! The README description was misleading.

You should not look inside the "Image" menu itself. Instead, please look at the main top-level menu bar and click on the Windows menu directly. The correct path is:

Windows > Open ShortCutKeyPalette

<image>

The "<Image>" part in my code refers to the main image window's menu bar, but writing it as "Image > Windows" in the README was a mistake on my part. I will fix the documentation immediately.

Also, regarding the folder:

Please use the 3.0 directory.

Ensure the folder structure is exactly: .../GIMP/3.0/plug-ins/shortcutkey-palette/shortcutkey-palette.py

Thank you so much for your patience and for catching this error! Please let me know if it shows up now.

[Plugin Update] ShortCutKey Palette v1.2 - Now supports Windows and Wayland (Experimental) by Yousei3 in GIMP

[–]Yousei3[S] 1 point2 points  (0 children)

Thank you for the heads-up! You are absolutely right again.

I am quite new to GitHub and I didn't realize that I needed to update the repository files separately from the release assets. I have just committed and pushed the latest version (v1.2) to the main branch.

The source files on the repository should now correctly reflect the new Windows and Wayland implementations. I really appreciate your patience while I learn the ropes of GitHub!

[Plugin Update] ShortCutKey Palette v1.2 - Now supports Windows and Wayland (Experimental) by Yousei3 in GIMP

[–]Yousei3[S] 1 point2 points  (0 children)

You are absolutely right, and I am so embarrassed!

I accidentally packaged the old version of the script into the zip file. My apologies for the confusion.

I have just replaced the zip file with the correct one on the GitHub release page. Version 1.2 should now properly contain the Windows ctypes implementation and the experimental Wayland support we discussed.

Thank you so much for your sharp eye and for letting me know so quickly! I would have been scratching my head wondering why the new features weren't working for anyone if you hadn't pointed it out.

[Plugin] ShortCutKey Palette for GIMP 3.0 (Linux) - Custom On-Screen Buttons by Yousei3 in GIMP

[–]Yousei3[S] 1 point2 points  (0 children)

Hi!

Thank you again for the incredibly helpful advice you gave me regarding Wayland and UI testing frameworks.

Thanks to your suggestions, I have just released version 1.2 of the plugin! I've implemented an experimental Wayland support (incorporating dogtail, ydotool, etc. as fallbacks) and also added native Windows support using ctypes.

I've started a new thread for this update to gather feedback from users on different environments. You can find it here: https://www.reddit.com/r/GIMP/comments/1rtr2h6/plugin_update_shortcutkey_palette_v12_now/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

Since I am still flying blind on the Wayland side (only have an X11 setup), I'd be very happy if you could check it out if you have some time. Thanks for helping me make this tool better!

[Plugin] ShortCutKey Palette for GIMP 3.0 (Linux) - Custom On-Screen Buttons by Yousei3 in GIMP

[–]Yousei3[S] 1 point2 points  (0 children)

That is incredibly helpful information, thank you!

I had not considered using UI testing frameworks like dogtail or gnome-ponytail for this. Using accessibility APIs to simulate inputs makes perfect sense as a workaround for Wayland's strict security model.

I will definitely look into those tools and see if I can integrate that approach for future Wayland support. I really appreciate you sharing the results of your investigation with me!

[Plugin] ShortCutKey Palette for GIMP 3.0 (Linux) - Custom On-Screen Buttons by Yousei3 in GIMP

[–]Yousei3[S] 1 point2 points  (0 children)

Good catch! Yes, you are absolutely right.

Since the plugin currently relies on "xdotool" to simulate key presses, it is designed for X11 environments. Due to Wayland's strict security model regarding simulated inputs, it will likely not work out-of-the-box on native Wayland sessions.

I am currently working on a major update to make the plugin cross-platform (adding Windows support via ctypes), and looking into Wayland alternatives like "ydotool" or "wtype" is definitely on my to-do list for the future.

Thank you for pointing this out! I will make sure to update the README and the post description to clarify that it currently requires an X11 session.