RSS/Atom feed Twitter
Site is read-only, email is disabled
  1. Chat
  2. Useful links
  3. Polls

Featured content

Question about fixes on your 2.8.10 release

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

2 of 2 messages available
Toggle history

Please log in to manage your subscriptions.
Question about fixes on your 2.8.10 release Jehan Pagès 12 Dec 06:26
  Question about fixes on your 2.8.10 release Jehan Pagès 12 Dec 10:29
Jehan Pagès
2013-12-12 06:26:36 UTC (almost 11 years ago)

Question about fixes on your 2.8.10 release

Hi Simone,

We have a user in GIMP who says he encountered a bug which prevented him to paint along selection/path on OSX with our 2.8.10 build.

But he says that he does not have this bug on your 2.8.10 build. Since I can't see what this can be about (this seems to be a different bug as the brush outline thingy), thus whether we fixed it or not, I was wondering if you know about this bug. Is it something you fixed on your build and that we would still have in our tree maybe? If so, would you please provide us with the patch? I don't see a new patch for such a bug in your subversion repository.

If not, well I don't know. Has anyone experienced such a problem with our build on OSX?
Thanks a lot.

Jehan

Jehan Pagès
2013-12-12 10:29:48 UTC (almost 11 years ago)

Question about fixes on your 2.8.10 release

Hi,

Nevermind. It turned out this was actually fixed with the same commit as the brush outline bug. That's why.

Jehan

On Thu, Dec 12, 2013 at 7:26 PM, Jehan Pagès wrote:

Hi Simone,

We have a user in GIMP who says he encountered a bug which prevented him to paint along selection/path on OSX with our 2.8.10 build.

But he says that he does not have this bug on your 2.8.10 build. Since I can't see what this can be about (this seems to be a different bug as the brush outline thingy), thus whether we fixed it or not, I was wondering if you know about this bug. Is it something you fixed on your build and that we would still have in our tree maybe? If so, would you please provide us with the patch? I don't see a new patch for such a bug in your subversion repository.

If not, well I don't know. Has anyone experienced such a problem with our build on OSX?
Thanks a lot.

Jehan