Clock add-on: version 21.09 released, what's coming in the next version #addonrelease


 

Hello everyone,

Clock 21.09 is now available (not available via Add-on Updater yet):

Release Clock 21.09 · hkatic/clock (github.com)

 

The biggest changes are modernization and incorporation of more recent localization updates. Starting from this release, NVDA 2019.3 or later is required.

 

Also, I’m working on the next version of the add-on. This upcoming version is perhaps one of the largest updates to Clock add-on in quite a while – the last big change was Python 3 compatibility done by Abdel last year.

Key highlights:

  • Various add-on messages are becoming more user friendly. For example, if you open alarm setup screen, the first control is “select type of timer”. Since this combo box is really about alarm duration unit (hours, minutes, seconds), it will be renamed to “alarm duration in” combo box. There are other messages like this which will be updated.
  • Quiet hours definition: previously if you enabled quiet hours, you had to follow an exact format when specifying quiet hours, and the add-on would complain if it couldn’t understand how you’ve defined quiet hours. The next version of Clock add-on will fundamentally change how you specify quiet hours – instead of text fields, a series of combo boxes will let you specify quiet hours start and end times (hours and minutes). Also, the checkbox labeled “input in 24-hour format” will now become a combo box that will let you see how start and end hour combo boxes will be shown to you. But these are small in comparison to vast under the hood changes to accompany user interface changes – starting from the next version of Clock add-on, quiet hours start and end times will be represented internally as integers (minutes between 0 and 1439); settings will be saved in either 12-hour or 24-hour format for compatibility with older add-on releases. All these changes mean NVDA will no longer complain about quiet hours format issues.
  • Clearing quiet hours: currently if you do define quiet hours and later uncheck “quiet hours” checkbox, quiet hours you have defined are still available. This is most noticeable in current add-on releases where if you do clear quiet hours texts, NVDA will complain about quiet hours format, which is actually a logic error. In the future when you do clear “quiet hours” checkbox, quiet hours you’ve specified will also be removed.
  • Elapsed and remaining times: if you set alarm or run the stopwatch for more than 24 hours, NVDA may think elapsed or remaining time is less than a day. This will be corrected so NVDA will announce correct hour/minute/second for elapsed and/or remaining time for alarm or stopwatch that spans more than 24 hours.
  • Various optimizations: in particular, parts of the add-on is being optimized to do less work. One best example is checking for time announcement intervals – in current releases, NVDA will retrieve list of time intervals every second (so up to 3600 times per hour); future releases will retrieve time intervals less often – latest development code was optimized so that intervals will be obtained only at the top of every minute (so up to 60 times per hour). Another example is announcing day of the year – this routine will do less work while giving you the information you expect (day of the year, week number, current year, remaining days for the current year); specifically, internals were optimized and now calls up to 25 percent less bytecode than before. There are other things being optimized, all designed to do more modernizations before handing the add-on back to the community in a few months.
  • Reducing unnecessary disk writes: currently if errors were found in the add-on or whenever you set alarms, changes will be saved to disk. Unfortunately this causes other add-ons to save settings if they were told to listen to config save action. To avoid this, the add-on will no longer forcefully save changes to disk each time something happens. This also means if you told NVDA to not save settings when NVDA exits, you must press Control+NVDA+C to save settings, including changes made by Clock add-on.

 

I expect the next version will be released sometime in November 2021. At that point I’ll ask if people are willing to take this add-on and make it better (Abdel and others who have worked on the add-on recently (excluding I) get priority considerations).

Thanks.

Cheers,

Joseph


 

Hi,

By the way, if you have suggestions or bug reports, feel free to create issues at:

https://github.com/hkatic/clock/issues/new

When filing issues, please provide steps to reproduce, NVDA version, and the add-on version you are using. Thanks.

Cheers,

Joseph

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Joseph Lee via groups.io
Sent: Sunday, September 12, 2021 4:17 PM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda-addons] Clock add-on: version 21.09 released, what's coming in the next version #AddonRelease

 

Hello everyone,

Clock 21.09 is now available (not available via Add-on Updater yet):

Release Clock 21.09 · hkatic/clock (github.com)

 

The biggest changes are modernization and incorporation of more recent localization updates. Starting from this release, NVDA 2019.3 or later is required.

 

Also, I’m working on the next version of the add-on. This upcoming version is perhaps one of the largest updates to Clock add-on in quite a while – the last big change was Python 3 compatibility done by Abdel last year.

Key highlights:

  • Various add-on messages are becoming more user friendly. For example, if you open alarm setup screen, the first control is “select type of timer”. Since this combo box is really about alarm duration unit (hours, minutes, seconds), it will be renamed to “alarm duration in” combo box. There are other messages like this which will be updated.
  • Quiet hours definition: previously if you enabled quiet hours, you had to follow an exact format when specifying quiet hours, and the add-on would complain if it couldn’t understand how you’ve defined quiet hours. The next version of Clock add-on will fundamentally change how you specify quiet hours – instead of text fields, a series of combo boxes will let you specify quiet hours start and end times (hours and minutes). Also, the checkbox labeled “input in 24-hour format” will now become a combo box that will let you see how start and end hour combo boxes will be shown to you. But these are small in comparison to vast under the hood changes to accompany user interface changes – starting from the next version of Clock add-on, quiet hours start and end times will be represented internally as integers (minutes between 0 and 1439); settings will be saved in either 12-hour or 24-hour format for compatibility with older add-on releases. All these changes mean NVDA will no longer complain about quiet hours format issues.
  • Clearing quiet hours: currently if you do define quiet hours and later uncheck “quiet hours” checkbox, quiet hours you have defined are still available. This is most noticeable in current add-on releases where if you do clear quiet hours texts, NVDA will complain about quiet hours format, which is actually a logic error. In the future when you do clear “quiet hours” checkbox, quiet hours you’ve specified will also be removed.
  • Elapsed and remaining times: if you set alarm or run the stopwatch for more than 24 hours, NVDA may think elapsed or remaining time is less than a day. This will be corrected so NVDA will announce correct hour/minute/second for elapsed and/or remaining time for alarm or stopwatch that spans more than 24 hours.
  • Various optimizations: in particular, parts of the add-on is being optimized to do less work. One best example is checking for time announcement intervals – in current releases, NVDA will retrieve list of time intervals every second (so up to 3600 times per hour); future releases will retrieve time intervals less often – latest development code was optimized so that intervals will be obtained only at the top of every minute (so up to 60 times per hour). Another example is announcing day of the year – this routine will do less work while giving you the information you expect (day of the year, week number, current year, remaining days for the current year); specifically, internals were optimized and now calls up to 25 percent less bytecode than before. There are other things being optimized, all designed to do more modernizations before handing the add-on back to the community in a few months.
  • Reducing unnecessary disk writes: currently if errors were found in the add-on or whenever you set alarms, changes will be saved to disk. Unfortunately this causes other add-ons to save settings if they were told to listen to config save action. To avoid this, the add-on will no longer forcefully save changes to disk each time something happens. This also means if you told NVDA to not save settings when NVDA exits, you must press Control+NVDA+C to save settings, including changes made by Clock add-on.

 

I expect the next version will be released sometime in November 2021. At that point I’ll ask if people are willing to take this add-on and make it better (Abdel and others who have worked on the add-on recently (excluding I) get priority considerations).

Thanks.

Cheers,

Joseph


Cyrille
 

Hello

Here are two issues that I had noticed in previous versions of Clock add-on (21.07 and before I think):

1. The time format combo box sometimes uses examples that have two digits for hours or minutes or seconds. This are not good example times since some time format differ only by the number of digits in hours, minutes or seconds. E.g. 01:04:07 AM is a good example time format; 01:33:20 PM is not a good example time format since minutes and seconds have two digits thus you cannot see the difference between H:M:S and HH:MM:SS time format.

2. In 24-hour time format reporting, at midnight, 12 hours is reported instead of 0 or 24. Please try the time format examples with a midnight time.

I have not yet tested the last (21.09) version. Thus I have not opened issues in the GitHub repo.

Cheers,

Cyrille


 
De : "Joseph Lee"
A : nvda-addons@nvda-addons.groups.io
Envoyé: lundi 13 Septembre 2021 01:18
Objet : Re: [nvda-addons] Clock add-on: version 21.09 released, what's coming in the next version #AddonRelease
 

Hi,

By the way, if you have suggestions or bug reports, feel free to create issues at:

https://github.com/hkatic/clock/issues/new

When filing issues, please provide steps to reproduce, NVDA version, and the add-on version you are using. Thanks.

Cheers,

Joseph

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Joseph Lee via groups.io
Sent: Sunday, September 12, 2021 4:17 PM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda-addons] Clock add-on: version 21.09 released, what's coming in the next version #AddonRelease

 

Hello everyone,

Clock 21.09 is now available (not available via Add-on Updater yet):

Release Clock 21.09 · hkatic/clock (github.com)

 

The biggest changes are modernization and incorporation of more recent localization updates. Starting from this release, NVDA 2019.3 or later is required.

 

Also, I’m working on the next version of the add-on. This upcoming version is perhaps one of the largest updates to Clock add-on in quite a while – the last big change was Python 3 compatibility done by Abdel last year.

Key highlights:

  • Various add-on messages are becoming more user friendly. For example, if you open alarm setup screen, the first control is “select type of timer”. Since this combo box is really about alarm duration unit (hours, minutes, seconds), it will be renamed to “alarm duration in” combo box. There are other messages like this which will be updated.
  • Quiet hours definition: previously if you enabled quiet hours, you had to follow an exact format when specifying quiet hours, and the add-on would complain if it couldn’t understand how you’ve defined quiet hours. The next version of Clock add-on will fundamentally change how you specify quiet hours – instead of text fields, a series of combo boxes will let you specify quiet hours start and end times (hours and minutes). Also, the checkbox labeled “input in 24-hour format” will now become a combo box that will let you see how start and end hour combo boxes will be shown to you. But these are small in comparison to vast under the hood changes to accompany user interface changes – starting from the next version of Clock add-on, quiet hours start and end times will be represented internally as integers (minutes between 0 and 1439); settings will be saved in either 12-hour or 24-hour format for compatibility with older add-on releases. All these changes mean NVDA will no longer complain about quiet hours format issues.
  • Clearing quiet hours: currently if you do define quiet hours and later uncheck “quiet hours” checkbox, quiet hours you have defined are still available. This is most noticeable in current add-on releases where if you do clear quiet hours texts, NVDA will complain about quiet hours format, which is actually a logic error. In the future when you do clear “quiet hours” checkbox, quiet hours you’ve specified will also be removed.
  • Elapsed and remaining times: if you set alarm or run the stopwatch for more than 24 hours, NVDA may think elapsed or remaining time is less than a day. This will be corrected so NVDA will announce correct hour/minute/second for elapsed and/or remaining time for alarm or stopwatch that spans more than 24 hours.
  • Various optimizations: in particular, parts of the add-on is being optimized to do less work. One best example is checking for time announcement intervals – in current releases, NVDA will retrieve list of time intervals every second (so up to 3600 times per hour); future releases will retrieve time intervals less often – latest development code was optimized so that intervals will be obtained only at the top of every minute (so up to 60 times per hour). Another example is announcing day of the year – this routine will do less work while giving you the information you expect (day of the year, week number, current year, remaining days for the current year); specifically, internals were optimized and now calls up to 25 percent less bytecode than before. There are other things being optimized, all designed to do more modernizations before handing the add-on back to the community in a few months.
  • Reducing unnecessary disk writes: currently if errors were found in the add-on or whenever you set alarms, changes will be saved to disk. Unfortunately this causes other add-ons to save settings if they were told to listen to config save action. To avoid this, the add-on will no longer forcefully save changes to disk each time something happens. This also means if you told NVDA to not save settings when NVDA exits, you must press Control+NVDA+C to save settings, including changes made by Clock add-on.

 

I expect the next version will be released sometime in November 2021. At that point I’ll ask if people are willing to take this add-on and make it better (Abdel and others who have worked on the add-on recently (excluding I) get priority considerations).

Thanks.

Cheers,

Joseph

 


Abdel
 

Hi Joseph,

Thank you for this beautiful work.

Wouldn't it have been better to put this version in the development channel until its stability is confirmed ?

Kind regards,
Abdel.

Le 13/09/2021 à 01:17, Joseph Lee a écrit :

Hello everyone,

Clock 21.09 is now available (not available via Add-on Updater yet):

Release Clock 21.09 · hkatic/clock (github.com)

 

The biggest changes are modernization and incorporation of more recent localization updates. Starting from this release, NVDA 2019.3 or later is required.

 

Also, I’m working on the next version of the add-on. This upcoming version is perhaps one of the largest updates to Clock add-on in quite a while – the last big change was Python 3 compatibility done by Abdel last year.

Key highlights:

  • Various add-on messages are becoming more user friendly. For example, if you open alarm setup screen, the first control is “select type of timer”. Since this combo box is really about alarm duration unit (hours, minutes, seconds), it will be renamed to “alarm duration in” combo box. There are other messages like this which will be updated.
  • Quiet hours definition: previously if you enabled quiet hours, you had to follow an exact format when specifying quiet hours, and the add-on would complain if it couldn’t understand how you’ve defined quiet hours. The next version of Clock add-on will fundamentally change how you specify quiet hours – instead of text fields, a series of combo boxes will let you specify quiet hours start and end times (hours and minutes). Also, the checkbox labeled “input in 24-hour format” will now become a combo box that will let you see how start and end hour combo boxes will be shown to you. But these are small in comparison to vast under the hood changes to accompany user interface changes – starting from the next version of Clock add-on, quiet hours start and end times will be represented internally as integers (minutes between 0 and 1439); settings will be saved in either 12-hour or 24-hour format for compatibility with older add-on releases. All these changes mean NVDA will no longer complain about quiet hours format issues.
  • Clearing quiet hours: currently if you do define quiet hours and later uncheck “quiet hours” checkbox, quiet hours you have defined are still available. This is most noticeable in current add-on releases where if you do clear quiet hours texts, NVDA will complain about quiet hours format, which is actually a logic error. In the future when you do clear “quiet hours” checkbox, quiet hours you’ve specified will also be removed.
  • Elapsed and remaining times: if you set alarm or run the stopwatch for more than 24 hours, NVDA may think elapsed or remaining time is less than a day. This will be corrected so NVDA will announce correct hour/minute/second for elapsed and/or remaining time for alarm or stopwatch that spans more than 24 hours.
  • Various optimizations: in particular, parts of the add-on is being optimized to do less work. One best example is checking for time announcement intervals – in current releases, NVDA will retrieve list of time intervals every second (so up to 3600 times per hour); future releases will retrieve time intervals less often – latest development code was optimized so that intervals will be obtained only at the top of every minute (so up to 60 times per hour). Another example is announcing day of the year – this routine will do less work while giving you the information you expect (day of the year, week number, current year, remaining days for the current year); specifically, internals were optimized and now calls up to 25 percent less bytecode than before. There are other things being optimized, all designed to do more modernizations before handing the add-on back to the community in a few months.
  • Reducing unnecessary disk writes: currently if errors were found in the add-on or whenever you set alarms, changes will be saved to disk. Unfortunately this causes other add-ons to save settings if they were told to listen to config save action. To avoid this, the add-on will no longer forcefully save changes to disk each time something happens. This also means if you told NVDA to not save settings when NVDA exits, you must press Control+NVDA+C to save settings, including changes made by Clock add-on.

 

I expect the next version will be released sometime in November 2021. At that point I’ll ask if people are willing to take this add-on and make it better (Abdel and others who have worked on the add-on recently (excluding I) get priority considerations).

Thanks.

Cheers,

Joseph


 

Hi,

That’s the plan for the November release. Sometime in late September I plan to release a development build with latest changes so folks can test things. After that, I expect to release about two or three snapshots before finalizing the next stable version.

Cheers,

Joseph

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Abdel
Sent: Monday, September 13, 2021 4:05 AM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Clock add-on: version 21.09 released, what's coming in the next version #AddonRelease

 

Hi Joseph,

Thank you for this beautiful work.

Wouldn't it have been better to put this version in the development channel until its stability is confirmed ?

Kind regards,
Abdel.

Le 13/09/2021 à 01:17, Joseph Lee a écrit :

Hello everyone,

Clock 21.09 is now available (not available via Add-on Updater yet):

Release Clock 21.09 · hkatic/clock (github.com)

 

The biggest changes are modernization and incorporation of more recent localization updates. Starting from this release, NVDA 2019.3 or later is required.

 

Also, I’m working on the next version of the add-on. This upcoming version is perhaps one of the largest updates to Clock add-on in quite a while – the last big change was Python 3 compatibility done by Abdel last year.

Key highlights:

  • Various add-on messages are becoming more user friendly. For example, if you open alarm setup screen, the first control is “select type of timer”. Since this combo box is really about alarm duration unit (hours, minutes, seconds), it will be renamed to “alarm duration in” combo box. There are other messages like this which will be updated.
  • Quiet hours definition: previously if you enabled quiet hours, you had to follow an exact format when specifying quiet hours, and the add-on would complain if it couldn’t understand how you’ve defined quiet hours. The next version of Clock add-on will fundamentally change how you specify quiet hours – instead of text fields, a series of combo boxes will let you specify quiet hours start and end times (hours and minutes). Also, the checkbox labeled “input in 24-hour format” will now become a combo box that will let you see how start and end hour combo boxes will be shown to you. But these are small in comparison to vast under the hood changes to accompany user interface changes – starting from the next version of Clock add-on, quiet hours start and end times will be represented internally as integers (minutes between 0 and 1439); settings will be saved in either 12-hour or 24-hour format for compatibility with older add-on releases. All these changes mean NVDA will no longer complain about quiet hours format issues.
  • Clearing quiet hours: currently if you do define quiet hours and later uncheck “quiet hours” checkbox, quiet hours you have defined are still available. This is most noticeable in current add-on releases where if you do clear quiet hours texts, NVDA will complain about quiet hours format, which is actually a logic error. In the future when you do clear “quiet hours” checkbox, quiet hours you’ve specified will also be removed.
  • Elapsed and remaining times: if you set alarm or run the stopwatch for more than 24 hours, NVDA may think elapsed or remaining time is less than a day. This will be corrected so NVDA will announce correct hour/minute/second for elapsed and/or remaining time for alarm or stopwatch that spans more than 24 hours.
  • Various optimizations: in particular, parts of the add-on is being optimized to do less work. One best example is checking for time announcement intervals – in current releases, NVDA will retrieve list of time intervals every second (so up to 3600 times per hour); future releases will retrieve time intervals less often – latest development code was optimized so that intervals will be obtained only at the top of every minute (so up to 60 times per hour). Another example is announcing day of the year – this routine will do less work while giving you the information you expect (day of the year, week number, current year, remaining days for the current year); specifically, internals were optimized and now calls up to 25 percent less bytecode than before. There are other things being optimized, all designed to do more modernizations before handing the add-on back to the community in a few months.
  • Reducing unnecessary disk writes: currently if errors were found in the add-on or whenever you set alarms, changes will be saved to disk. Unfortunately this causes other add-ons to save settings if they were told to listen to config save action. To avoid this, the add-on will no longer forcefully save changes to disk each time something happens. This also means if you told NVDA to not save settings when NVDA exits, you must press Control+NVDA+C to save settings, including changes made by Clock add-on.

 

I expect the next version will be released sometime in November 2021. At that point I’ll ask if people are willing to take this add-on and make it better (Abdel and others who have worked on the add-on recently (excluding I) get priority considerations).

Thanks.

Cheers,

Joseph


 

Hi,

For item 1, I think it might be time to remove some duplicate sounding time formats, as they partly come from time format used for Windows GetTimeFormatEx function.

For item 2, I’m looking into the overall time output functionality and plan to perhaps overhaul this facility. I understand how to reproduce this – can you give us examples so we can figure out what’s up?

Cheers,

Joseph

 

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Cyrille via groups.io
Sent: Sunday, September 12, 2021 11:48 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Clock add-on: version 21.09 released, what's coming in the next version #AddonRelease

 

Hello

Here are two issues that I had noticed in previous versions of Clock add-on (21.07 and before I think):

1. The time format combo box sometimes uses examples that have two digits for hours or minutes or seconds. This are not good example times since some time format differ only by the number of digits in hours, minutes or seconds. E.g. 01:04:07 AM is a good example time format; 01:33:20 PM is not a good example time format since minutes and seconds have two digits thus you cannot see the difference between H:M:S and HH:MM:SS time format.

2. In 24-hour time format reporting, at midnight, 12 hours is reported instead of 0 or 24. Please try the time format examples with a midnight time.

I have not yet tested the last (21.09) version. Thus I have not opened issues in the GitHub repo.

Cheers,

Cyrille


 

De : "Joseph Lee"
A : nvda-addons@nvda-addons.groups.io
Envoyé: lundi 13 Septembre 2021 01:18
Objet : Re: [nvda-addons] Clock add-on: version 21.09 released, what's coming in the next version #AddonRelease
 

Hi,

By the way, if you have suggestions or bug reports, feel free to create issues at:

https://github.com/hkatic/clock/issues/new

When filing issues, please provide steps to reproduce, NVDA version, and the add-on version you are using. Thanks.

Cheers,

Joseph

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Joseph Lee via groups.io
Sent: Sunday, September 12, 2021 4:17 PM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda-addons] Clock add-on: version 21.09 released, what's coming in the next version #AddonRelease

 

Hello everyone,

Clock 21.09 is now available (not available via Add-on Updater yet):

Release Clock 21.09 · hkatic/clock (github.com)

 

The biggest changes are modernization and incorporation of more recent localization updates. Starting from this release, NVDA 2019.3 or later is required.

 

Also, I’m working on the next version of the add-on. This upcoming version is perhaps one of the largest updates to Clock add-on in quite a while – the last big change was Python 3 compatibility done by Abdel last year.

Key highlights:

  • Various add-on messages are becoming more user friendly. For example, if you open alarm setup screen, the first control is “select type of timer”. Since this combo box is really about alarm duration unit (hours, minutes, seconds), it will be renamed to “alarm duration in” combo box. There are other messages like this which will be updated.
  • Quiet hours definition: previously if you enabled quiet hours, you had to follow an exact format when specifying quiet hours, and the add-on would complain if it couldn’t understand how you’ve defined quiet hours. The next version of Clock add-on will fundamentally change how you specify quiet hours – instead of text fields, a series of combo boxes will let you specify quiet hours start and end times (hours and minutes). Also, the checkbox labeled “input in 24-hour format” will now become a combo box that will let you see how start and end hour combo boxes will be shown to you. But these are small in comparison to vast under the hood changes to accompany user interface changes – starting from the next version of Clock add-on, quiet hours start and end times will be represented internally as integers (minutes between 0 and 1439); settings will be saved in either 12-hour or 24-hour format for compatibility with older add-on releases. All these changes mean NVDA will no longer complain about quiet hours format issues.
  • Clearing quiet hours: currently if you do define quiet hours and later uncheck “quiet hours” checkbox, quiet hours you have defined are still available. This is most noticeable in current add-on releases where if you do clear quiet hours texts, NVDA will complain about quiet hours format, which is actually a logic error. In the future when you do clear “quiet hours” checkbox, quiet hours you’ve specified will also be removed.
  • Elapsed and remaining times: if you set alarm or run the stopwatch for more than 24 hours, NVDA may think elapsed or remaining time is less than a day. This will be corrected so NVDA will announce correct hour/minute/second for elapsed and/or remaining time for alarm or stopwatch that spans more than 24 hours.
  • Various optimizations: in particular, parts of the add-on is being optimized to do less work. One best example is checking for time announcement intervals – in current releases, NVDA will retrieve list of time intervals every second (so up to 3600 times per hour); future releases will retrieve time intervals less often – latest development code was optimized so that intervals will be obtained only at the top of every minute (so up to 60 times per hour). Another example is announcing day of the year – this routine will do less work while giving you the information you expect (day of the year, week number, current year, remaining days for the current year); specifically, internals were optimized and now calls up to 25 percent less bytecode than before. There are other things being optimized, all designed to do more modernizations before handing the add-on back to the community in a few months.
  • Reducing unnecessary disk writes: currently if errors were found in the add-on or whenever you set alarms, changes will be saved to disk. Unfortunately this causes other add-ons to save settings if they were told to listen to config save action. To avoid this, the add-on will no longer forcefully save changes to disk each time something happens. This also means if you told NVDA to not save settings when NVDA exits, you must press Control+NVDA+C to save settings, including changes made by Clock add-on.

 

I expect the next version will be released sometime in November 2021. At that point I’ll ask if people are willing to take this add-on and make it better (Abdel and others who have worked on the add-on recently (excluding I) get priority considerations).

Thanks.

Cheers,

Joseph

 


Cyrille
 

Hello

For item 2, writing an example from memory:
STR:
- Set-up time reporting with HH:MM:SS format; not very sure of the format, but should be this one or one quite similar.
- Call time reporting (NVDA+F12) a few minutes after midnight.
Expected 00:12:33
Actual: 12:12:33

Hope this helps
Cheers,

Cyrille

 
De : "Joseph Lee"
A : nvda-addons@nvda-addons.groups.io
Envoyé: lundi 13 Septembre 2021 14:31
Objet : Re: [nvda-addons] Clock add-on: version 21.09 released, what's coming in the next version #AddonRelease
 

Hi,

For item 1, I think it might be time to remove some duplicate sounding time formats, as they partly come from time format used for Windows GetTimeFormatEx function.

For item 2, I’m looking into the overall time output functionality and plan to perhaps overhaul this facility. I understand how to reproduce this – can you give us examples so we can figure out what’s up?

Cheers,

Joseph

 

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Cyrille via groups.io
Sent: Sunday, September 12, 2021 11:48 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Clock add-on: version 21.09 released, what's coming in the next version #AddonRelease

 

Hello

Here are two issues that I had noticed in previous versions of Clock add-on (21.07 and before I think):

1. The time format combo box sometimes uses examples that have two digits for hours or minutes or seconds. This are not good example times since some time format differ only by the number of digits in hours, minutes or seconds. E.g. 01:04:07 AM is a good example time format; 01:33:20 PM is not a good example time format since minutes and seconds have two digits thus you cannot see the difference between H:M:S and HH:MM:SS time format.

2. In 24-hour time format reporting, at midnight, 12 hours is reported instead of 0 or 24. Please try the time format examples with a midnight time.

I have not yet tested the last (21.09) version. Thus I have not opened issues in the GitHub repo.

Cheers,

Cyrille


 

De : "Joseph Lee"
A : nvda-addons@nvda-addons.groups.io
Envoyé: lundi 13 Septembre 2021 01:18
Objet : Re: [nvda-addons] Clock add-on: version 21.09 released, what's coming in the next version #AddonRelease
 

Hi,

By the way, if you have suggestions or bug reports, feel free to create issues at:

https://github.com/hkatic/clock/issues/new

When filing issues, please provide steps to reproduce, NVDA version, and the add-on version you are using. Thanks.

Cheers,

Joseph

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Joseph Lee via groups.io
Sent: Sunday, September 12, 2021 4:17 PM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda-addons] Clock add-on: version 21.09 released, what's coming in the next version #AddonRelease

 

Hello everyone,

Clock 21.09 is now available (not available via Add-on Updater yet):

Release Clock 21.09 · hkatic/clock (github.com)

 

The biggest changes are modernization and incorporation of more recent localization updates. Starting from this release, NVDA 2019.3 or later is required.

 

Also, I’m working on the next version of the add-on. This upcoming version is perhaps one of the largest updates to Clock add-on in quite a while – the last big change was Python 3 compatibility done by Abdel last year.

Key highlights:

  • Various add-on messages are becoming more user friendly. For example, if you open alarm setup screen, the first control is “select type of timer”. Since this combo box is really about alarm duration unit (hours, minutes, seconds), it will be renamed to “alarm duration in” combo box. There are other messages like this which will be updated.
  • Quiet hours definition: previously if you enabled quiet hours, you had to follow an exact format when specifying quiet hours, and the add-on would complain if it couldn’t understand how you’ve defined quiet hours. The next version of Clock add-on will fundamentally change how you specify quiet hours – instead of text fields, a series of combo boxes will let you specify quiet hours start and end times (hours and minutes). Also, the checkbox labeled “input in 24-hour format” will now become a combo box that will let you see how start and end hour combo boxes will be shown to you. But these are small in comparison to vast under the hood changes to accompany user interface changes – starting from the next version of Clock add-on, quiet hours start and end times will be represented internally as integers (minutes between 0 and 1439); settings will be saved in either 12-hour or 24-hour format for compatibility with older add-on releases. All these changes mean NVDA will no longer complain about quiet hours format issues.
  • Clearing quiet hours: currently if you do define quiet hours and later uncheck “quiet hours” checkbox, quiet hours you have defined are still available. This is most noticeable in current add-on releases where if you do clear quiet hours texts, NVDA will complain about quiet hours format, which is actually a logic error. In the future when you do clear “quiet hours” checkbox, quiet hours you’ve specified will also be removed.
  • Elapsed and remaining times: if you set alarm or run the stopwatch for more than 24 hours, NVDA may think elapsed or remaining time is less than a day. This will be corrected so NVDA will announce correct hour/minute/second for elapsed and/or remaining time for alarm or stopwatch that spans more than 24 hours.
  • Various optimizations: in particular, parts of the add-on is being optimized to do less work. One best example is checking for time announcement intervals – in current releases, NVDA will retrieve list of time intervals every second (so up to 3600 times per hour); future releases will retrieve time intervals less often – latest development code was optimized so that intervals will be obtained only at the top of every minute (so up to 60 times per hour). Another example is announcing day of the year – this routine will do less work while giving you the information you expect (day of the year, week number, current year, remaining days for the current year); specifically, internals were optimized and now calls up to 25 percent less bytecode than before. There are other things being optimized, all designed to do more modernizations before handing the add-on back to the community in a few months.
  • Reducing unnecessary disk writes: currently if errors were found in the add-on or whenever you set alarms, changes will be saved to disk. Unfortunately this causes other add-ons to save settings if they were told to listen to config save action. To avoid this, the add-on will no longer forcefully save changes to disk each time something happens. This also means if you told NVDA to not save settings when NVDA exits, you must press Control+NVDA+C to save settings, including changes made by Clock add-on.

 

I expect the next version will be released sometime in November 2021. At that point I’ll ask if people are willing to take this add-on and make it better (Abdel and others who have worked on the add-on recently (excluding I) get priority considerations).

Thanks.

Cheers,

Joseph

 

 


 

Hi,

So if I understand you, this issue comes up if you are dealing with a 24-hour format time- as in no “AM” or “PM”? If so, I think I know why – caused by time format specifier. I’ll come up with a fix in the next dev and stable builds (the dev build will be going out some time today as a try build and hopefully via Add-on Updater).

Cheers,

Joseph

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Cyrille via groups.io
Sent: Monday, September 13, 2021 6:59 AM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Clock add-on: version 21.09 released, what's coming in the next version #AddonRelease

 

Hello

For item 2, writing an example from memory:
STR:
- Set-up time reporting with HH:MM:SS format; not very sure of the format, but should be this one or one quite similar.
- Call time reporting (NVDA+F12) a few minutes after midnight.
Expected 00:12:33
Actual: 12:12:33

Hope this helps
Cheers,

Cyrille

 

De : "Joseph Lee"
A : nvda-addons@nvda-addons.groups.io
Envoyé: lundi 13 Septembre 2021 14:31
Objet : Re: [nvda-addons] Clock add-on: version 21.09 released, what's coming in the next version #AddonRelease
 

Hi,

For item 1, I think it might be time to remove some duplicate sounding time formats, as they partly come from time format used for Windows GetTimeFormatEx function.

For item 2, I’m looking into the overall time output functionality and plan to perhaps overhaul this facility. I understand how to reproduce this – can you give us examples so we can figure out what’s up?

Cheers,

Joseph

 

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Cyrille via groups.io
Sent: Sunday, September 12, 2021 11:48 PM
To: nvda-addons@nvda-addons.groups.io
Subject: Re: [nvda-addons] Clock add-on: version 21.09 released, what's coming in the next version #AddonRelease

 

Hello

Here are two issues that I had noticed in previous versions of Clock add-on (21.07 and before I think):

1. The time format combo box sometimes uses examples that have two digits for hours or minutes or seconds. This are not good example times since some time format differ only by the number of digits in hours, minutes or seconds. E.g. 01:04:07 AM is a good example time format; 01:33:20 PM is not a good example time format since minutes and seconds have two digits thus you cannot see the difference between H:M:S and HH:MM:SS time format.

2. In 24-hour time format reporting, at midnight, 12 hours is reported instead of 0 or 24. Please try the time format examples with a midnight time.

I have not yet tested the last (21.09) version. Thus I have not opened issues in the GitHub repo.

Cheers,

Cyrille


 

De : "Joseph Lee"
A : nvda-addons@nvda-addons.groups.io
Envoyé: lundi 13 Septembre 2021 01:18
Objet : Re: [nvda-addons] Clock add-on: version 21.09 released, what's coming in the next version #AddonRelease
 

Hi,

By the way, if you have suggestions or bug reports, feel free to create issues at:

https://github.com/hkatic/clock/issues/new

When filing issues, please provide steps to reproduce, NVDA version, and the add-on version you are using. Thanks.

Cheers,

Joseph

 

From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Joseph Lee via groups.io
Sent: Sunday, September 12, 2021 4:17 PM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda-addons] Clock add-on: version 21.09 released, what's coming in the next version #AddonRelease

 

Hello everyone,

Clock 21.09 is now available (not available via Add-on Updater yet):

Release Clock 21.09 · hkatic/clock (github.com)

 

The biggest changes are modernization and incorporation of more recent localization updates. Starting from this release, NVDA 2019.3 or later is required.

 

Also, I’m working on the next version of the add-on. This upcoming version is perhaps one of the largest updates to Clock add-on in quite a while – the last big change was Python 3 compatibility done by Abdel last year.

Key highlights:

  • Various add-on messages are becoming more user friendly. For example, if you open alarm setup screen, the first control is “select type of timer”. Since this combo box is really about alarm duration unit (hours, minutes, seconds), it will be renamed to “alarm duration in” combo box. There are other messages like this which will be updated.
  • Quiet hours definition: previously if you enabled quiet hours, you had to follow an exact format when specifying quiet hours, and the add-on would complain if it couldn’t understand how you’ve defined quiet hours. The next version of Clock add-on will fundamentally change how you specify quiet hours – instead of text fields, a series of combo boxes will let you specify quiet hours start and end times (hours and minutes). Also, the checkbox labeled “input in 24-hour format” will now become a combo box that will let you see how start and end hour combo boxes will be shown to you. But these are small in comparison to vast under the hood changes to accompany user interface changes – starting from the next version of Clock add-on, quiet hours start and end times will be represented internally as integers (minutes between 0 and 1439); settings will be saved in either 12-hour or 24-hour format for compatibility with older add-on releases. All these changes mean NVDA will no longer complain about quiet hours format issues.
  • Clearing quiet hours: currently if you do define quiet hours and later uncheck “quiet hours” checkbox, quiet hours you have defined are still available. This is most noticeable in current add-on releases where if you do clear quiet hours texts, NVDA will complain about quiet hours format, which is actually a logic error. In the future when you do clear “quiet hours” checkbox, quiet hours you’ve specified will also be removed.
  • Elapsed and remaining times: if you set alarm or run the stopwatch for more than 24 hours, NVDA may think elapsed or remaining time is less than a day. This will be corrected so NVDA will announce correct hour/minute/second for elapsed and/or remaining time for alarm or stopwatch that spans more than 24 hours.
  • Various optimizations: in particular, parts of the add-on is being optimized to do less work. One best example is checking for time announcement intervals – in current releases, NVDA will retrieve list of time intervals every second (so up to 3600 times per hour); future releases will retrieve time intervals less often – latest development code was optimized so that intervals will be obtained only at the top of every minute (so up to 60 times per hour). Another example is announcing day of the year – this routine will do less work while giving you the information you expect (day of the year, week number, current year, remaining days for the current year); specifically, internals were optimized and now calls up to 25 percent less bytecode than before. There are other things being optimized, all designed to do more modernizations before handing the add-on back to the community in a few months.
  • Reducing unnecessary disk writes: currently if errors were found in the add-on or whenever you set alarms, changes will be saved to disk. Unfortunately this causes other add-ons to save settings if they were told to listen to config save action. To avoid this, the add-on will no longer forcefully save changes to disk each time something happens. This also means if you told NVDA to not save settings when NVDA exits, you must press Control+NVDA+C to save settings, including changes made by Clock add-on.

 

I expect the next version will be released sometime in November 2021. At that point I’ll ask if people are willing to take this add-on and make it better (Abdel and others who have worked on the add-on recently (excluding I) get priority considerations).

Thanks.

Cheers,

Joseph

 

 


 

Hi all,

Clock 21.09 is (finally) available via Add-on Updater. Note that you must be running NVDA 2019.3 or later to instlal this add-on. Also, if you are on dev channel for this add-on, you will be prompted to update to 21.09.

Cheers,

Joseph