For this particular addon, it isn't a big deal to me whether the
pointer is to a web page on my site or an addon file on my site,
because once I code VAC Control Panel support, there shouldn't need to
be many changes. The apps in VAC don't seem to change often, and they
are small apps besides.
Your offer to add this web pointer concept to the addon structure is
most kind though, and if I do further work on Skype or another big
and/or frequently-changing app, I will most assuredly appreciate the
capability.
On Fri, Jun 20, 2014 at 07:58:31AM -0700, Joseph Lee wrote:
Hi,
Hmmm, that could open up possibilities where some add-on writers who host
add-ons on their site can point to their websites.
For Noelia, Mesar, Alberto and other devs: can we grant Doug an exception to
our current readme structure where instead of pointing to links to download
the add-on file, user would be provided a link to go to an add-on author's
website? Something like:
* Author: Doug Lee
* Add-ons website link.
The rest would be similar to our readme's. This would be handy if the author
wishes for us to post just an add-on entry instead of a file, or provide a
way for an add-on author to provide documentation on his or her website.
This might also be useful for NV Access as well.
Cheers,
Joseph
-----Original Message-----
From: nvda-addons-bounce@xxxxxxxxxxxxx
[mailto:nvda-addons-bounce@xxxxxxxxxxxxx] On Behalf Of Doug Lee
Sent: Friday, June 20, 2014 7:47 AM
To: nvda-addons@xxxxxxxxxxxxx
Subject: [nvda-addons] Re: New addon for Virtual Audio Cable available
Should I write a page for you to point at instead of having you point at the
.nvda-addon file directly? I usually do that for JAWS scripts; I just didn't
do that for NVDA yet out of haste. That would let me announce changes at my
end. Again open to discussion of how to document changes going forward
though.
On Fri, Jun 20, 2014 at 07:12:25AM -0700, Joseph Lee wrote:
Hi,
Sure, we can host the entry with the download link pointing to the file
located on your site (NV Access' OCR entry has the same format).
Cheers,
Joseph
-----Original Message-----
From: nvda-addons-bounce@xxxxxxxxxxxxx
[mailto:nvda-addons-bounce@xxxxxxxxxxxxx] On Behalf Of Doug Lee
Sent: Friday, June 20, 2014 7:09 AM
To: nvda-addons@xxxxxxxxxxxxx
Subject: [nvda-addons] Re: New addon for Virtual Audio Cable available
I have no problem with you listing this on the main addon site. I do prefer
to manage the updates on my web site if possible, but I'm open to discussion
of this process. I also need to see what should be in the readme and where
it should go. I'm sure I can write such a thing.
I'm trying to add support for the VAC Control Panel (for both NVDA and
JAWS) today anyway.
As for control IDs and indices, the control IDs appear to be static and even
to be unchanged across some VAC releases according to test results I
received earlier from a user of an older VAC incarnation. I should get
visual verification that my tab order is sensible, and it looks like my
sorted-controlID approach for tab order may not be enough for the VAC
Control Panel; so I might have to institute a system for listing control IDs
explicitly to form a tab order there.
Thanks for the feedback.
On Fri, Jun 20, 2014 at 05:52:16AM -0700, Joseph Lee wrote:
Hi Doug,
Code reviews:
1. Are the control ID's static? If not, perhaps using child object indecies
might help too (the indecies will change if some UI elements are added or
removed).
2. I like your idea of using a common app module framework for both of these
VAC variants, as these would be useful to support common methods between two
or more programs from the same vendor (not between app modules and global
plugins unless if you want to store a common set of methods in a file
somewhere).
If there is popular demand and if you agree to it, we'd be happy to list
your add-on on the community add-ons site, linking to your add-on download
link, with you or one of the other authors writing the readme.
Cheers,
joseph
-----Original Message-----
From: nvda-addons-bounce@xxxxxxxxxxxxx
[mailto:nvda-addons-bounce@xxxxxxxxxxxxx] On Behalf Of Doug Lee
Sent: Friday, June 20, 2014 5:43 AM
To: nvda-addons@xxxxxxxxxxxxx
Subject: [nvda-addons] Re: New addon for Virtual Audio Cable available
I am using Windows 8.1, and lacking knowledge of how to explore what we once
called the Start menu, I just type in app names to run them. I actually
missed the existence of the VAC Control Panel. I will look at that now to
see if I can make that easier to use as well.
On Fri, Jun 20, 2014 at 09:30:55AM +0200, Ondrej Rosik wrote:
HI,
I have no idea about your code, but on my system with VAC 4.10 it works as
expected. But I think that this version is quite outdated so maybe I
definitelly should update and test it again. Anyways as a future request, it
would be great if you can also name fields in the application control panel.
But still, good job.
D??a 19. 6. 2014 23:17 Doug Lee wrote / nap??sal(a):
I have posted an NVDA addon for Virtual Audio Cable at
http://www.dlee.org/vac/vac.nvda-addon
The home page for Virtual Audio Cable itself is
http://software.muzychenko.net/eng/vac.htm
The addon does three things: Fixes field names, fixes tab order or at
least improves it, and avoids focus loss when you press Start/Stop. (I
am aware that it is odd to alter tab order with an addon, but for these
small apps, I thought it would help enough to be worth it.)
The addon applies to the two audiorepeater applications in Virtual
Audio Cable 4.1.4: audiorepeater 1.51 and audiorepeater_ks 1.82.
I am not sure how modern my approach to addon creation is, so I welcome
constructive feedback at this address on how I accomplished this.
I do find that the focus recovery can fail sometimes and that the tab
order code may be sensitive to timing because obj.setFocus() must
sometimes be called twice with an intervening delay in order to work;
but overall, I find this addon functional enough to be useful.
The rest of this message is just for code readers, reviewers, curious
souls, etc.:
audiorepeater.py and audiorepeater_ks.py are the directly loaded
modules. They both delegate the bulk of their work to ar_common.py,
which contains the required AppModule class and handles the field
naming, focus recovery, and Tab/Shift+Tab gesture intercepts. The tab
order itself is handled by wins.py. That module takes care to rebuild
its data structures if the active app changes, either because the user
closed one instance and opened a new one or, rare though this may be,
because the user ran both audiorepeater and audiorepeater_ks at the
same time. I don't see a way to load multiple instances of either app
at once, but this addon code should support that use case if it
happens.
Tab order is equal to ascending progression through control IDs - a
rare approach but a very functional one for these apps, it seems to me.
On the first Tab or Shift+Tab in a given app instance, a dict of
controlID-to-object mappings is built for that instance, so finding the
next tab stop can be done quickly.
----------------------------------------------------------------
NVDA add-ons Central: A list for discussing NVDA add-ons
To post a message, send an email to nvda-addons@xxxxxxxxxxxxx.
To unsubscribe, send an email with the subject line of "unsubscribe"
(without quotes) to nvda-addons-request@xxxxxxxxxxxxx.
If you have questions for list moderators, please send a message to
nvda-addons-moderators@xxxxxxxxxxxxx.
Community addons can be found here: http://addons.nvda-project.org
