I always click it when I don't feel like accidentally touching objects or making object within the canvas, but this funny message comes up. It's a small inconvenience for any one who use the tool that way. When not working in a vector layer, Krita should swap to move viewport button instead when pressing the arrow button. Just a thought although it is inconvenient for those who use it that way.
Created attachment 108805 [details] A bug related to this No longer just a wishlist, this is a bug.
This only happens when I keep the message there on Krita, and exit Krita to do whatever using Krita 4.0 Pre-Alpha 2 on Windows 10 x64.
This is a wishlist item for further improvement. This message was added to a number of tools because of how many bug reports we were getting tired of responding to with "your tools are broken and do nothing". Those reports have gone down dramatically since 4.0 has been released. One solution would be to disable tools that don't work with different layer types. I am sure there are other potential ways we could handle it.
Every time I try to move the canvas with the middle mouse(on a wacom actually) this shows ups it is really annoying!!!!
I found another bug related to this. If you use the the tool on a vector layer, and try to apply filter layer/mask, you get this message.
@Frederico - when does it show up when using the middle mouse button? If I am on a vector layer it doesn't show up with a middle mouse button. Does this tool work on other types of layers that I am not aware of?
this bug is going to have to get more concrete before anything would be able to get done. We could probably tweak when this is shown, but we need something more descriptive than what is in the current report. @Reptillian -- You cannot use the Select Shape tool on a filter layer. This is the type of reason why we need this message since people don't understand how this tool works.
@Scott Petrovic -- I'm aware of that, but I think you're missing out on the try. Like, if I right-click just to look at filter layer/mask, the message appears, and it interferes with workflow. It's just not worth clicking on another tool, and then apply to avoid getting the message, and then go back and click the mouse tool.
If you found another bug I would put it as another ticket. Mixing it with this is probably confusing me. For the new bug, it does seem like the on-canvas messages are interfering with other dialogs. Your steps are an easy way to trigger it. It is probably not the only way to get in that situation though as there are quite a few on-canvas messages. Just give the steps to reproduce in a new ticket. There is also a separate conversation going on in here that deals with middle clicking that we need more information on. That might need a different change depending on how the person replies. They didn't specify what type of tool, or layer type, they are even on.
It might be my bad, im not in a vector layer, just normal layer and was thinking the arrow icon "select shapes tool" was a kind of default tool. I guess it is not a bug then, just confusing for me:(
@Frederico - no worries. Long terms we are hoping to make the shape selection tool work like a move tool when on a raster layer. That way it will work on both raster and vector layers and this situation won't exist. That tools is a bit awkward now as it only works on vector layers.
I have created a new bug report related to this tool - Bug 393859 - https://bugs.kde.org/show_bug.cgi?id=393859
Getting back to the original request then... It sounds like your original proposal was to make the shape selection tool do something on raster layers. I think your suggestion of the "move viewport button" (I think you are talking about the Pan tool?). We have had other people want this to be the move contents tool...since it moves content on vector layers.
Actually, all I want to see is this error message problem go away when needed which is why I suggest switching to pan tool automatically while working with raster layers, but it doesn't solve the on canvas issue. I must say that the current move content tool has it own issue that would be better off discussed in another place.
It's not intrusive for 4.2. So, I'll set this to resolved.