View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000289 | SpeedFan | Configuration | public | 2005-06-12 14:14 | 2005-11-15 22:46 |
| Reporter | flachschippe | Assigned To | alfredo | ||
| Priority | normal | Severity | tweak | Reproducibility | always |
| Status | acknowledged | Resolution | open | ||
| Platform | PC Athlon 64 Nforce 4 | OS | Windows | OS Version | 2000 SP 4 |
| Summary | 0000289: 'Enter' key closes config dialog when event popup text is entered | ||||
| Description | Enter key should instead confirm and end the text entry. | ||||
| Steps To Reproduce | Create or update any popup event, enter a message text, hit Enter -- the dialog closes, without creating or updating the event. | ||||
| Tags | No tags attached. | ||||
| Motherboard Model | |||||
| Video Card Model | |||||
|
|
This can be especially annoying in conjunction with issue 286 (no confirm on config close). |
|
|
The ENTER key in a dialog means "press the default button or the currently highlighted one". |
|
|
Then the default is not set nicely (:-). In an attempt to get a nicer behavior, I tabbed to the 'Update' button, then clicked in the text input box. The dotted line on the 'Update' button vanishes, and if I watch *very* closely, I can see that the 'OK' button outline changes, suggesting that 'OK' is now the default action. But it is not, 'Cancel' is the default action, which is not intended, is it? |
|
|
Reminder sent to: almico Did one more experiment, see the added note. I don't feel that this is just a tweak, it can 'major'ly annoy users a lot if their work is unintentionally discarded. |
|
|
I checked again and ENTER presses the highlighted button. If the highlighted button is OK, then OK is pressed. While this is standard Windows behaviour (and interface requirement), I agree that a confirmation dialog would be nice. Otherwise I might disable the OK button while there is an event under editing. I would prefer the latter. |
|
|
> ENTER presses the highlighted button. I agree. However, if I manually highlight the 'Update' button (via tab key), and then click in the message text input box, the 'Update' button is unhighlighted (what's the word here?) and the default button is then 'OK'. This has the effect that text edits are discarded when 'Enter' is pressed. Instead, the 'Update' button should automatically become the default (or highlighted?) button as soon as any changes are made to an event. |
|
|
The way it is now, the 'Enter' key does not have any effect at all, not even the current event is updated. As stated is the original issue description: Enter key should [...] confirm and end the text entry. With the current, umm, unconventional four-button-set, the 'Enter' key should have the same effect that the 'Update' button has (for consistency, the 'Update' button would have to be the default button). |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2005-06-12 14:14 | flachschippe | New Issue | |
| 2005-06-12 14:22 | flachschippe | Note Added: 0000973 | |
| 2005-06-14 10:35 | alfredo | Note Added: 0000974 | |
| 2005-06-14 10:35 | alfredo | Severity | major => tweak |
| 2005-06-14 10:35 | alfredo | Status | assigned => acknowledged |
| 2005-06-15 00:12 | flachschippe | Note Added: 0000990 | |
| 2005-06-15 00:15 | flachschippe | Note Added: 0000991 | |
| 2005-06-15 10:05 | alfredo | Note Added: 0000992 | |
| 2005-06-18 08:18 | flachschippe | Note Added: 0000997 | |
| 2005-11-15 22:46 | flachschippe | Note Added: 0001366 |
