On Sat, 22 Jan 2005 14:00:42 +0100, Sven Neumann [EMAIL PROTECTED] wrote:
Raphaël Quinet [EMAIL PROTECTED] writes:
[...] I am worried about the configuration parameters that could
be used by more than one plug-in.
Of course plug-ins must not access gimprc directly. gimprc is the core
rc
Hi,
Raphal Quinet [EMAIL PROTECTED] writes:
I expected this suggestion, which is why I wrote that I was worried
about the parameters the could be used by more than one plug-in. If
each plug-in uses its own config file, then it will become tricky for
two plug-ins to share some config
Hi,
Raphal Quinet [EMAIL PROTECTED] writes:
This is again a good idea, but does this mean that the plug-ins
converted to use GimpConfig would then start accessing the config
files directly? I would prefer to make sure that all set/get
operations for the configuration options are going
On Fri, 21 Jan 2005 00:29:00 +0100, Sven Neumann [EMAIL PROTECTED] wrote:
Raphaël Quinet [EMAIL PROTECTED] writes:
So the default should be to open the images with the correct
orientation without asking, and there should be an option in the
preferences (gimprc) that allows the user to
Hi,
Raphal Quinet [EMAIL PROTECTED] writes:
So the default should be to open the images with the correct
orientation without asking, and there should be an option in the
preferences (gimprc) that allows the user to ignore the EXIF
Orientation tag or to be asked every time. The threshold for
Sven wrote:
I want to suggest that we implement this by moving most of the
GimpConfig functionality from the core to libgimpbase or, alternatively,
to a new library, maybe called libgimpconfig.
[ . . . ]
There are a few things that we will need to decide upon, like in which
library
