Hello.

I think if it's not a bug, it'a a annoying thing.

When I'm using brush with 70% opacity (example) and I hold V to temporarly switch to Line Tool the opacity changes to what is set in line tool. I think it could be more elegant, if I'm using a 30% opacicity brush and need a straight line it's desire theat my line had 30% opacity too.

Is this make sense for you guys? See below

I agree that it would be reasonable to want the current brush opacity to be 'carried across' to the line tool when doing a temporary switch with the 'V' key. An alternative would be to leave the 'V' key action as it is now and to use 'Shift+V' (or whatever) as an opacity maintaining temporary switch key.

(The 'V' key is not listed in the Keyboard Shortcuts and it is possible to set the 'V' key to perform another function with no warning being given. If you do this, it also acts as a brush->line switch at the same time. This looks like a bug.)

I also agree with your suggestion about the cursor in eraser mode: viewtopic.php?f=288&t=161711

You can raise a bug report here: https://bugs.kde.org/ with an Importance set to 'Wishlist' for your suggestions. They will join the queue of bugs awaiting attention.

Would you mind also reporting the problem with using 'V' as a shortcut key, since you have an interest in this?

ahabgreybeard wrote:...as an opacity maintaining temporary switch key.

... If you do this, it also acts as a brush->line switch at the same time...

Sorry, I think I didn't understand, but I can't find this function (opacity maintaining) on "Keyboard Shortcuts" settings. Could you explain please?

Thank's

The behaviour of the Keyboard Shortcuts is a separate issue from your idea about how the opacity should behave when you use the 'V' key.

There is no 'opacity maintaining' function at the moment. This is something that you say you want. I agree it would be a good idea to have an opacity maintaining behaviour when the 'V' key is used for a temporary switch to the Line tool.

So, this was actually the case, but then boud implemented per-tool opacity: https://invent.kde.org/kde/krita/commit ... cb90f77ac3 to resolve this bug: https://bugs.kde.org/show_bug.cgi?id=359809

Hi Thera,

Thank you for that information and the links. It seems the current situation is more flexible than it used to be in terms of per-tool opacity (and per-brush opacity). Luciano wants to go back to the 'old way' in the specific situation where he presses the 'V' key to make a temporary switch to the Line tool. I suppose he could set Line tool opacity to be equal to brush tool opacity as his personal workaround. It's up to him if he wants to formally push it up to a Wishlist bug report. I can understand why someone would want this in that specific situation.

I believe my comments about Keyboard Shortcut clashes are still relevant and I'll raise a bug report for that soon; unless anyone can tell me that it's ok as it is.

Bug report submitted for Keyboard Shortcut clash: https://bugs.kde.org/show_bug.cgi?id=410552

I reported a bug about this situation with line/brush because I think it worth.
Let's let the developers decide what is better for Krita.