No description
2211ca7fd3
… waitpid(). My use case was when testing gimp_brush_select_new(). When doing tests, if I let the brush dialog opened while letting the plug-in exit cleanly otherwise, it somehow locked the process (I have stared so long at the code and still don't understand why). gimp_plug_in_close() would wait for it forever and the only way out was to kill GIMP completely. I guess we could try to run waitpid() with WNOHANG (and finally force-kill the child if it really won't exit) but it made the whole logics extra complicated. The logics with g_child_watch_add_full() is that we don't stop waiting for the child and just set a callback to finalize what needs to be. Now the worst case scenario would be to leave zombie processes dangling around, but it's better than freezing GIMP. Finally as a weird side effect, doing this change even unblocked the process with an unfinished brush selector so we don't even have a zombie anymore (at least for this specific case). All good in the end! Last side effect: it can speed up a tiny bit the plug-in close as we don't wait for processes anymore, which could be more visible at first startups (when we reload all the plug-ins). Though there is nothing scientific to my numbers, after multiple "first startups", it seems it went down from about 3.5 to 3.2 seconds on my specific machine. Nothing extra fancy, but we take what we can (and speeding up the startup was never the goal of this change anyway). It doesn't affect Windows which has its own logics to handle process termination and I preferred not to touch it. |
||
|---|---|---|
| .gitlab | ||
| app | ||
| app-tools | ||
| build | ||
| cursors | ||
| data | ||
| desktop | ||
| devel-docs | ||
| docs | ||
| etc | ||
| extensions | ||
| icons | ||
| libgimp | ||
| libgimpbase | ||
| libgimpcolor | ||
| libgimpconfig | ||
| libgimpmath | ||
| libgimpmodule | ||
| libgimpthumb | ||
| libgimpwidgets | ||
| m4macros | ||
| menus | ||
| modules | ||
| pdb | ||
| plug-ins | ||
| po | ||
| po-libgimp | ||
| po-plug-ins | ||
| po-python | ||
| po-script-fu | ||
| po-tags | ||
| po-tips | ||
| po-windows-installer | ||
| themes | ||
| tools | ||
| .dir-locals.el | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .kateconfig | ||
| acinclude.m4 | ||
| AUTHORS | ||
| authors.dtd | ||
| authors.xml | ||
| authors.xsl | ||
| authors4gimp-web.xsl | ||
| autogen.sh | ||
| ChangeLog.pre-1-0 | ||
| ChangeLog.pre-1-2 | ||
| ChangeLog.pre-2-0 | ||
| ChangeLog.pre-2-2 | ||
| ChangeLog.pre-2-4 | ||
| ChangeLog.pre-2-6 | ||
| ChangeLog.pre-git | ||
| config.h.win32 | ||
| configure.ac | ||
| COPYING | ||
| gimp-zip.in | ||
| gimp.doap | ||
| gimp.pc.in | ||
| gimpthumb.pc.in | ||
| gimpui.pc.in | ||
| HACKING | ||
| INSTALL.in | ||
| LICENSE | ||
| MAINTAINERS | ||
| Makefile.am | ||
| meson.build | ||
| meson.make | ||
| meson_dist_script.sh | ||
| meson_options.txt | ||
| NEWS | ||
| NEWS.pre-2-0 | ||
| NEWS.pre-2-2 | ||
| NEWS.pre-2-4 | ||
| NEWS.pre-2-6 | ||
| NEWS.pre-2-8 | ||
| NEWS.pre-2-10 | ||
| README | ||
| README.i18n | ||
------------------------------
GNU Image Manipulation Program
2.99 Development Branch
------------------------------
This is an unstable development release, an intermediate state on the
way to the next stable release: GIMP 3. GIMP 2.99 may or may not do what
you expect. Save your work early and often. If you want a stable
version, please use GIMP 2.10 instead.
If you think you found a bug in this version, please make sure that it
hasn't been reported earlier and that it is not just new stuff that is
still being worked on and obviously not quite finished yet.
If you want to hack on GIMP, please read the file HACKING. For
detailed installation instructions, see the file INSTALL.
1. Web Resources
================
GIMP's home page is at:
https://www.gimp.org/
Please be sure to visit this site for information, documentation,
tutorials, news, etc. All things GIMP-ish are available from there.
There you can get the latest versions of plug-ins, using a convenient
forms-based interface.
The latest version of GIMP can be found at:
https://www.gimp.org/downloads/
2. Mailing Lists
================
We have several mailing lists dedicated to GIMP user and development
discussion. There is more info at
https://www.gimp.org/mail_lists.html
Links to several archives of the mailing lists are included in that page.
Gimp-user-list is a mailing list dedicated to user problems, hints and
tips, discussion of cool effects, etc. Gimp-developer-list is oriented
to GIMP core and plug-in developers. Gimp-gui-list is for discussing
about GIMP interface to improve user experience. Most people will only
want to be subscribed to gimp-user-list. If you want to help develop
GIMP, the gimp-developer mailing list is a good starting point; if you
want to help with GUI design, the gimp-gui list is where you want to
subscribe.
3. IRC
======
And finally, for the real junkies, there is an IRC channel devoted to
GIMP. On GIMPNet (a private free software oriented network) there is
#gimp. Many of the developers hang out there. Some of the GIMPNet
servers are:
irc.gimp.org:6667
irc.us.gimp.org:6667
irc.eu.gimp.org:6667
4. Customizing
==============
The look of GIMP's interface can be customized like any other GTK+ app
by editing files in `${XDG_CONFIG_HOME}/gtk-3.0/` (settings.ini and
gtk.css in particular) or by using "themes" (ready-made customizations).
Additionally, GIMP reads `${XDG_CONFIG_HOME}/GIMP/2.99/gimp.css` so you
can have settings that only apply to GIMP.
Included is a set of keybindings similar to those in Adobe Photoshop.
You can find them in the ps-menurc file. To use them, copy this file
to `${XDG_CONFIG_HOME}/GIMP/2.99/menurc`. You can also manually change
the keybindings to any of your choice by editing:
`${XDG_CONFIG_HOME}/GIMP/2.99/menurc`.
Have fun,
Spencer Kimball
Peter Mattis
Federico Mena
Manish Singh
Sven Neumann
Michael Natterer
Dave Neary
Martin Nordholts