Seriously. Damn - then I might not have tested it long enough. I was about to give this version a try but it seems as if the waiting goes on. Such a little bug, but it kills productivity.

Thanks for pointing it out.

Yes exactly , it kill productivity . Hope developers will fix that soon

With all due respect guys, if you find a hiccup like this to be a show stopper then you can't possible be whiling to use Krita for what it is.

First of all, on a Alpha or Beta, we do expect some "buggy" behavior, the intention is for people to test and report the issues, if this version was ready for release it wouldn't be called by these ways.

Tagging is buggy, yet, why create and add tags before creating and or editing brushes?, this is usually the last step, some times some workflows are just counterproductive by nature. I'm not saying you guys are, just that it seems odd that you jump into the "ah never mind Krita, is not a bug-free program after all" type of comments.

I'm not trying to argue or saying that you are wrong, I just saying that your expectations and the way you comments are written, are rather on a different state than those of many users of Krita like myself, sounds like you try really hard not to use Krita, I mean, no one is obligated to, right?

andreasresch wrote:Seriously. Damn - then I might not have tested it long enough. I was about to give this version a try but it seems as if the waiting goes on. Such a little bug, but it kills productivity.

Thanks for pointing it out.

I mean, in all good terms, lets be honest, I don't think you ever going to be happy with Krita, your gripe with this is been going for so long. I've seen people who either jump into the coding train to accomplish what they want or just move on, life is short, why spend it in frustration? I would just like to point out that this attitude never fuels volunteers coders energy.

Any way, the best of luck to you man!

Quiralta wrote:With all due respect guys, if you find a hiccup like this to be a show stopper then you can't possible be whiling to use Krita for what it is.

First of all, on a Alpha or Beta, we do expect some "buggy" behavior, the intention is for people to test and report the issues, if this version was ready for release it wouldn't be called by these ways.

Tagging is buggy, yet, why create and add tags before creating and or editing brushes?, this is usually the last step, some times some workflows are just counterproductive by nature. I'm not saying you guys are, just that it seems odd that you jump into the "ah never mind Krita, is not a bug-free program after all" type of comments.

I'm not trying to argue or saying that you are wrong, I just saying that your expectations and the way you comments are written, are rather on a different state than those of many users of Krita like myself, sounds like you try really hard not to use Krita, I mean, no one is obligated to, right?

andreasresch wrote:Seriously. Damn - then I might not have tested it long enough. I was about to give this version a try but it seems as if the waiting goes on. Such a little bug, but it kills productivity.

Thanks for pointing it out.

I mean, in all good terms, lets be honest, I don't think you ever going to be happy with Krita, your gripe with this is been going for so long. I've seen people who either jump into the coding train to accomplish what they want or just move on, life is short, why spend it in frustration? I would just like to point out that this attitude never fuels volunteers coders energy.

Any way, the best of luck to you man!

Wow - I don't even know where to start with commenting on all that, so I won't. Whatever your reasons were to write all that, and your intentions might have been good, I'll just let that balloon fly. Cheerio.

We dont expect miracles man Tag issue is long term problem . We see it for almost a year or so . We see a lot of new features coming to krite when some basic stuff still ist polished enough ( expect performance , with that developers make awesome job from release to release) . I am not new in the biznes I helped with development of blender for years ( bug reporting stuff etc ) and I just keeping the same good habit I learn there . Keep polishing basic stuff before jumping in to new stuff like gamount masking feature which may by interesting but will be use for maybe 5% of user in maybe 5% of time spend in krite when brush editor is main feature used all the time . See difference ?

Krite in my opinion is no more some student style side project ( which your explanation will fit ) but very interesting soft aiming to by professional app so we making with Andre some professional suggestions . Looking by amount of report of that bug in forum , reddit etc we re not alone

Regarding the "please polish the stuff already inside, not make new features" - actually you and Krita team generally agree. We're on a strict bug fixing mission right now, but... keep in mind there are different kinds of developers involved here:

- paid developers, right now Boud, Dmitry, Jouni, and a new ones: me (tiar) and Ghevan (ivanyossi) - they do what Boud says, aka right now we're only fixing bugs, nothing else, (Dmitry was also doing HDR, but he finished it in January or February and now he's fixing bugs; I spent one day on Clone Brush, other than that for last 3 months I was fixing bugs, etc.)

- Google Summer of Code students that do what they declared to do, which can only be new features - for example Gamut Masking is, if I'm not wrong, Wolthera's GSOC project (EDIT: absolutely not - done by Anna Medonosova, volunteer developer, sorry for misleading - but this year we'll get for example SVG animated brush tips thanks to gsoc),

- volunteer developers, who do whatever they want and their code is just checked and included to Krita - keep in mind that "bug fixing mission" is not binding for them.

Regarding the tags bug - yes, we're working on it, or rather Boud was working on it and we were hoping it could be done before 4.2., but it's a big project and there were other more important issues that needed to be taken care of - for example Qt 5.12 (new version of library Krita uses) being completely broken - it broke tablet code, drag&drop actions etc., and "just don't use that version" wasn't an option because a lot of Linux distributions already released it to users (hence the "emergency" Krita version 4.1.8 for Linux users). There were problems with Python scripting not found on Linux and other things that were important. The work Boud have done already is not lost of course and he'll be trying to get it included in 4.3.0.

Also regarding the bug fixing mission - around September we're planning to have a zero-bugs release, consistent with what was promised last year in the fundraiser.

Glad to hear that ! I want to be clear, all my suggestion are only focus to help not to critic developers and I love these small crazy features which come to krita regularly I just think ( i worked in industry for years you can find my work here www.pedryczart.com ) that krita is seriously something special and with good direction of development it can by next killer app like a blender or 3dcoat in 3d world ( consider small teams projects which grow to by industry standards ) Definitely Krita is closest to by a "killer" of photoshop in concept art industry for sure

that September ultimate fixed release will be krita 4.3 ?