← Back to team overview

nvda-sonar-users team mailing list archive

Re: Plugin Class Definition Code Question

 

Hi Gavin,

Out of curiosity, is this really a dialog with inaccessible hotspots? Dialogs are normally fairly accessible even if you have to use object navigation. That said, I guess it wouldn't surprise me; Native Instruments are pretty good and finding ways to make things inaccessible.

You'd have to add an extra check to the bottom of chooseNVDAObjectOverlayClasses to detect this case. For example:
		if obj.windowClassName == "#32770" and obj.name == "Samples Missing":
			clsList.insert(0, KontaktSamplesMissingDialog)

I only really intended this hotspot framework for internal use. If people are going to add more themselves regularly, I might need to come up with a way for this to be done from external modules.

Jamie

On 24/12/2012 1:25 AM, Gavin Grundlingh wrote:
Hi all,

When defining a plugin class for Kontakt in Sonar's app module, I wanted
to also add hot spots for the "Samples Missing" dialog. From reading the
code in the module, I gathered that plugin classes are identified by the
start of their window titles, as well as the window class name. Is there
a conditional statement I can add that will check for a window class of
#32770 with a title of "Samples Missing"? The hot spot functionality
seems to only be available for classes with names like "AfxFrameW42U".

Regards,

Gavin Grundlingh
Phone: +27 (0) 83 713-6191
Secondary Phone: +27 (0) 79 157-2466
Fax: +27 (0) 86 617-5792
Email: g.batworx@xxxxxxxxx <mailto:g.batworx@xxxxxxxxx>
Secondary Email: customtracks@xxxxxxxxxx <mailto:customtracks@xxxxxxxxxx>
Skype: Batworx
Facebook: http://www.facebook.com/batworx
Twitter: http://twitter.com/batworx




--
James Teh
Email/MSN Messenger/Jabber: jamie@xxxxxxxxxxx
Web site: http://www.jantrid.net/
Twitter: jcsteh


References