David Kirkby was writing a scientific application that required
bitmaps of specific colors to be read as data. The interpolation
of colors was causing problems with the application, and David wondered
if there was any way to turn off interpolation.
Kelly Martin suggested using indexed mode, and Blue Lang
suggested
"dialogs-$gt;pallete edit->new"
then choose only the colors you want and image->mode->index(ed) the image
to 4 colors, and you should be rocking.
David added that the images needed to be in 24 bit mode for the software.
Sven Neumann suggested disabling anti-aliasing and changing the Interpolation
type to Nearest-Neighbor in the Preferences Dialog. He also added
If you use the EllipseSelect tool and fill the
selection, disable antialiasing in the EllipseSelect tool options. If
you are stroking the selection, use the Pencil to stroke.
Mike Kelly submitted two bug reports to Bugzilla a few weeks ago and they
have remained "UNCONFIRMED" Mike wanted to know if this was the right thing to
do with bug reports and if there was anything he could do to help.
Sven Neumann said that writing to the mailing list was a to get people
to notice a bug. The one major flaw with the list, as he saw it, was
that it didn't send mail to the bugs-list.
Daniel Egger thanked Mike for following through on the bug and added that the
developers following Bugzilla were busy and hadn't been confirming many
bugs lately. He added
Creating proper bugreports is a very good start, having a fix in
hand is even better but fixing foreign bugs will make you a god.... :)
Raphael Quinet added
I wish that more people would use the bug database for reporting
bugs. This is the correct way to do it. And these bug reports included
all the necessary information to reproduce and analyze the bugs, which
is very nice.
Raphael also suggested making the old
gimp bugs list the default owner for all Gimp bugs. This would e-mail any
update to the list until someone took ownership of the bug.
Federico Mena Quintero added
Go to the module administration page in Bugzilla. You can enter a
list of addresses that will be mailed when a new bug is logged for a
module.
Raphael Quinet had some additional comments about committing a bug fix to
CVS after it has been reported to Bugzilla.
I have a small suggestion for the handling of bug reports and bug fixes:
Whenever you commit a bug fix in CVS and this bug was reported in bugzilla,
do the following things:
This will ensure a better synchonization between CVS and bugzilla. It will
also help people to know when a bug was fixed and when it can be expected
to appear in a released version (the message in bugzilla has a timestamp).
And someone who looks at the entries in the CVS log cab get more info about
why a change was made by looking up the corresponding bug report.
This is what I am doing at work and it makes it much easier for everybody to
trace the bug fixes. Actually, when a part of the code is in testing / bug
fixing phase before a release, nobody is allowed to commit or merge any
changes in the release branch unless the commit message contains a reference
to a bug report.
Raphael Quinet has been helping confirm bugs on Solaris and Unix, but is unable to confirm bugs for Windows, IRIX, HP-UX or other OSes. These bugs usually stay unconfirmed for quite a while. Raphael want to know if there were people on the development list that would also be interested in actively confirming bugs on these and other platforms.
Sven Neumann asked if anyone had changed Bugzilla so that it would email bug reports to the bugs-list. After various permissions and accounts dealings, Daniel Egger and Raphael changed all open bugs to belong to the bugs-list. Raphael warned of the oncoming spam to the bugs-list of 250+ changed bug reports.