LinuxBeaver

Results 71 comments of LinuxBeaver

You can test the update now by downloading this code and binaries. https://cdn.discordapp.com/attachments/1072485707664326691/1176355122775855135/source_code_and_binaries_of_new_inner_glow.zip?ex=656e9114&is=655c1c14&hm=dbfa65b9b82c682a828e4f222c10d2adb717b1fedd8650466109cdabea585e3d&

Assuming you said documentation on how to use this filter is not clear. **Linux Download is here** https://github.com/LinuxBeaver/Gimp_Layer_Effects_Text_Styler_Plugin_GEGL_Effects/releases/download/Continual_July22_2023/GEGL_Effects_Linux_Binaries.zip **Windows Download is here** https://github.com/LinuxBeaver/Gimp_Layer_Effects_Text_Styler_Plugin_GEGL_Effects/releases/download/Continual_July22_2023/GEGL_Effects_Windows_Binaries.zip **Source code is here** https://github.com/LinuxBeaver/Gimp_Layer_Effects_Text_Styler_Plugin_GEGL_Effects/releases/download/Continual_July22_2023/source_code_of_gegl_effects_CE.zip Source code...

dude.. I had to . GIMP 2.99.19 was crashing my plugins mid session when closing tabs or when GIMP closes. Then after the crash GIMP would run in a hidden...

ok... I did all I could to stop the crash. If it still happens I can't do anything. My GEGL code is perfect... I can't possibly do anymore even if...

It does work with flatpak. Put it here /home/USERNAME/.var/app/org.gimp.GIMP/data/gegl-0.4/plug-ins

Bevel's work on anything but very dark text - and color overlays only work proper on white text, but I have no idea why it is doing that. This shouldn't...

Try using GEGL Bevel or GEGL inner glow on their own and see what happens.

It says it has no property called string. Based on everything I know string is referring to this. https://gegl.org/operations/gegl-gegl.html I don't know why this error is happening.

![image](https://user-images.githubusercontent.com/78667207/214437287-4ff1e737-5d3f-48cf-a884-9a2da689ffd4.png) See if your copy of GEGL has this string setting. If it gives you an EEEEEEK error then something is wrong.

I just confirmed "string" is not the issue. That is a trivial error on line 790 that should have zero effect on the filter. Something else is going on here.