[identify] Right-click with identify features tool does not work with all selection modes

[qgib]

Author Name: Harrissou Santanna (@DelazJ)
Original Redmine Issue: 19251
Affected QGIS version: 3.1(master)
Redmine category:unknown

---

Using the "Identify Results" tool, right-click on the canvas, you'll be prompted with the list of overlaid features.
This is only true if you have the "identify features by area or single click" tool enabled at the top of the Identify Results panel.
If you had switched to any other "select" tool, nothing would have happened, either with a single right-click or drawing an extent with the right button pressed (I wonder if the latter process is desirable)

Anyway, I think we should either:

• find a way to notify the user that the configs are not good
• or allow the right-click button to ignore the active selection tool and still pops-up the result as if it was a single right-click.

[Pedro-Murteira]

Still true on QGIS 3.16.15 and 3,22,2,

[DelazJ]

Afaics with 3.33 c6a8e94ca9 on Debian 12, right-click with the selection tool returns result for following selection tools:

• Identify feature(s)
• Identify feature(s) on mouse over
• and Identifiy feature(s) by polygon

Both "Identify feature(s) by freehand" and "Identify feature(s) by radius" do not return any results (as you can see at the end of the video at #54484)

[nyalldawson]

This is not a bug -- there's no right click option because it doesn't make sense for the radius or freehand modes.

The only reason it shows for the "polygon" mode is because it's allowing you to take the clicked feature as the polygon boundary (instead of forcing you to click-click-click and digitize it manually!)

[github-actions]

The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale".
If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.

[github-actions]

While we hate to see this happen, this issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue.
Or, if you have any further questions, there are also further support channels that can help you.