Bug 184667

Summary:	keyboard shortcuts conflict dialog: use the common sense order of information-question-answers
Product:	[Unmaintained] kdelibs	Reporter:	Maciej Pilichowski <bluedzins>
Component:	general	Assignee:	Michael Jansen <kde>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	BelGraviton, kde
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Unspecified
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Maciej Pilichowski 2009-02-17 15:40:49 UTC

Version:            (using KDE 4.2.0)
Installed from:    SuSE RPMs

Normally you should provide the order
information (about the problem) -- question (solution to the problem) -- answers

But currently the order in the dialog is this:
problem in general -- question -- details of the problem -- answers

So user has to join two parts of the problem and focus on the question in the middle to answer. This is wrong.

Counter-example:
The "V" shortcut is ambiguous with the following shortcuts.
Do you want to assign an empty shortcut to these actions?
Shortcut(s) 'V' for action 'View Source'

[ Reassign ] [ Cancel ]

Not mentioning the sense of the sentence -- "X shortcut is ambiguous with X" (it is clear by definition, X cannot conflict with Y).

It should be something like this:

The "V" shortcut conflicts with the action 'View Source'.
Do you want to reassign an empty shortcut to these actions?

[ Reassign ] [ Cancel ]

(note -- the same verb used for question and for answer).

Comment 1 Andrew Crouthamel 2018-11-02 23:04:14 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Comment 2 Andrew Crouthamel 2018-11-16 05:33:34 UTC

Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!

Comment 3 Justin Zobel 2022-12-12 01:56:06 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 4 Bug Janitor Service 2022-12-27 05:20:29 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Bug Janitor Service 2023-01-11 05:18:27 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!