Other then the few bugs that still await patching (gimprc, and jpeg preview size), GIMP 2.8 64-bit's been running flawlessly on my system. Very tempted to install Partha's build, but don't want to mess up what I currently have at this moment. Anyway, just wondering or, if you know of a site that tells when such updates are going to be implemented, I would appreciate the link. Thanks in advance.

the samj portable version of partha build will not mess up nothing (as mine )

but for the main question i have no idea, i don't even know if that bugs are already patched...personally i found almost irrilevant the bug for jpg (but maybe because i would use in any case RIOT-save for the web to export ) but the other may be well more disturbing.

Maybe i did found a workaround using the samj utility, it seems working but has a basic limitation :
you may use both PSPI and userfilter (i believe needs more test to be sure ) BUT not in the same session,
basically i used 2 configuration files one that load pspi another the user filter and to change configuration is needed reload gimp

I agree that the jpeg preview is more nuissance then an actually bug, but the gimprc patch is much desired (so I can have my user filter back; lol). Don't think there is consensus for the brush lag issue either but I believe Partha addressed this in his build (but I could be wrong) by addressing the color profile issue. Still, 2.8's been out for well over a month; time to release 2.8.1, then, if another bug gets patched 2.8.2 (it's 2.8.3 that will be the most stable build based on past gimp change releases; lol). Also, isn't 2.10 going to be released by the end of the year? Thought they were going to drive this release on the fast track but I could be wrong (this querry is outside the scope of my original request so it's more out of curiosity then needs a reply).

I'm wondering when they're going to fix the bug where the image constantly breaks up if you move it by middle-clicking on the mouse. It doesn't behave nearly as badly if you grab the little preview window and move it around that way, but you shouldn't have to do that.

@lyle: The brush lag issue is fixed. The newest source from git contains the patch. So parthas build should contain the fix. I tested it (I have always the newest gimp on my machine...) and I activated all the filters, including color management and it works absolutely fine now.

@lacertile: I think, the movement issue was fixed with the brush lag fix, too. I think, it is nearly impossible to fix it completely. When you move the mouse, every moved pixel, an event is fired to repaint the region that the mouse pointer just left. There are many recalculations neccessary, but moving the mouse means just a small region to be rapainted. Moving the whole image by panning means to recalculate the whole canvas. And that takes a long time, so the whole canvas is only repainted correctely, when the mouse (and the image) stops. Maybe these calculations can be optimized by using assembler, but that would end up support for multiple platforms and multiple processor families.

Hatti

All the bugs are fixed in the GIT version.
Including the shift + left mouse click to link all layers.

Sure, but that functionality wasn't broken in 2.6, so I don't understand why it was in 2.8. I will check out Partha's latest build however and see if it is improved.

Just downloaded Partha's 2.8.1 64-bit build. The image fracturing issue is much improved. It still breaks up when moving around, but it is much faster about correcting itself and getting back in place as opposed to the several second lag in the 2.8 version. I haven't done any more work in than just that quick test, but I think this will be more manageable.

Some very interesting info that I was unaware of. The next official release will be 2.8.2. Details why below.

http://www.gimpusers.com/news/00424-gim ... mment12909

good catch

Lyle,

This has always been the case.

Odd numbers are developmental releases while even are considered stable.

Not exactly: it was so for the..hu...how call it...main release number:
2.6 was stable 2.7 unstable

but 2.6.11 was stable even if 11 is a odd number

now instead 2.8.3 would be a beta release of the stable branch

Using the same logic 2.9.2 should be a stable release of a instable branch.. that obviously make no sense but seems are always bureaucratic minds liking to complicate thing without fearing the ridiculous

What PC said. lol

Just was surprised that they started doing the sub updates this way, but I actually like it in the sense that when they do a sub updated, even more bugs will get ferreted out before the masses actually see an update.

I'm not sure I follow your logic there. As far as I understand it, this is just a naming convention. If it's true (I'll wait for an announcement through an official GIMP channel before I believe it) all it will mean is that bug reports for odd-numbered sub versions would be suspect because they are reports against an unknown build standard- which git snapshot was compiled?- which may be helpful to the developers.

Personally I think the whole even=stable, odd=unstable convention is not working because it requires us to continually explain it to new comers. (Is it explained somewhere on gimp.org?)

I agree with kevin. Odd and even numbers simply do not work.
They should just be named Gimp-2.xx_Stable OR Gimp-2.xx_UnStable.
That would really clear up the confusion.

Perhaps a max of 3 bug fixes and then a Stable release should be implemented?
In fact i had assumed the developers were going that route this time.
Fix a few bugs, and release a new version. I would say it is due.

Brush delay with color aware enabled, jpeg preview, and gimprc (for starters; these been patched); yup, I agree it's overdue Rod. lol