Skip to content

Add "No message timeout" braille setting#6777

Merged
feerrenrut merged 3 commits into
nvaccess:masterfrom
dkager:i6669
May 30, 2017
Merged

Add "No message timeout" braille setting#6777
feerrenrut merged 3 commits into
nvaccess:masterfrom
dkager:i6669

Conversation

@dkager

@dkager dkager commented Jan 21, 2017

Copy link
Copy Markdown
Contributor

In #6669 we discussed two corner cases for the braille message timeout:

  1. To completely disable messages.
  2. To show messages indefinitely.

In the end I decided to leave the original behavior alone: a message timeout of 0 disables messages altogether.
There is now an extra checkbox "No message timeout" to show messages indefinitely. It seemed most logical to add this checkbox after the edit field. Of course, enabling the checkbox disables the edit field.
This approach avoids having to add a config profile upgrade step and won't be confusing to users who currently have the timeout set to 0.

@feerrenrut feerrenrut left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, overall this looks really good. What happens when the there is a message currently being displayed "indefinitely" and the setting is changed to a timeout?

Comment thread source/gui/settingsDialogs.py Outdated
self.messageTimeoutEdit.Disable()

# Translators: The label for a setting in braille settings to display a message on the braille display indefinitely.
noMessageTimeoutLabelText = _("No &message timeout")

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Personally, I think the positive form of this label would be clearer, eg: "Show message indefinitely"

Comment thread source/gui/settingsDialogs.py Outdated
min=int(config.conf.getConfigValidationParameter(["braille", "messageTimeout"], "min")),
max=int(config.conf.getConfigValidationParameter(["braille", "messageTimeout"], "max")),
initial=config.conf["braille"]["messageTimeout"])
if self.noMessageTimeoutCheckBox.GetValue():

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This causes an exception, since self.noMessageTimeoutCheckBox is not created until line 1575

@dkager

dkager commented Apr 25, 2017

Copy link
Copy Markdown
Contributor Author

@feerrenrut Pushed some new stuff.

@feerrenrut

Copy link
Copy Markdown
Contributor

I have had a look at this, the alignment of the controls looks good. Could you please talk about what kind of testing you have done on this?

@dkager

dkager commented Apr 26, 2017

Copy link
Copy Markdown
Contributor Author

Could you please talk about what kind of testing you have done on this?

Tested this with one display (since the code isn't driver-specific).
This was in early February, but from what I recall I used something like NVDA+t to have a quick message appear, then:

  • Left it alone and verified that it stayed on the display.
  • Focused another GUI element to make sure the message was cleared immediately.
  • Used braille display keys to read the message and ensured it stayed on the display.
  • Unselected the checkbox to make sure the message cleared (it does, because saving that setting causes the GUI to update which clears the message).

Also tested this with an actual use case, reading messages in Skype without having to rush.

feerrenrut added a commit that referenced this pull request Apr 27, 2017
Re Issue: #6669
Merge branch 'dkager-i6669' into next
@feerrenrut feerrenrut merged commit 6ca7499 into nvaccess:master May 30, 2017
@nvaccessAuto nvaccessAuto added this to the 2017.3 milestone May 30, 2017
feerrenrut added a commit that referenced this pull request May 30, 2017
- PR #7169 : Editable div elements in Chrome are no longer have their label reported as their value while in browse mode. (Issue #7153)
- PR #6396 : An unbound gesture (script_restart) has been added to allow NVDA to be restarted quickly. (PR #6396)
- PR #6777 : A Braille setting has been added to "show messages indefinitely". (Issue #6669)
- PR #7133 : Pressing end while in browse mode of an empty Microsoft Word document no longer causes a runtime error. (Issue #7009)
- PR #6868 : The keyboard layout can now be set from the NVDA Welcome dialog. (Issue #6863)
- PR #6813 : The names of "landmarks" are abbreviated in Braille (Issue #3975)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants