Woops! Meant to say, "and NOT a full fledged solution."
Aaron
On 6/22/2012 11:38 AM, Aaron Smith wrote:
I'm sure there's more bulletproofing that needs to be done to make
sure that the accessible is valid before using it (ie.If Not accObj Is
Nothing Then). Understand that, this being the scripting list, I was
providing a simple proof of concept, and a full fledged solution to
Foobar's accessibility issues.
Aaron
On 6/22/2012 11:11 AM, Life My Way wrote:
Ok, when i did this the list view works but when i go to alt f 4 out
of the
my documents where i have the portable version of foobar 2000 i get
another
error message but can not copy it it goes away to quickly what can i do?
----- Original Message -----
From: "Aaron Smith" <[email protected]>
To: <[email protected]>
Sent: Friday, June 22, 2012 9:40 AM
Subject: Re: foobar 2000
That means that the text you copied didn't work wrap correctly. Just
delete the line that starts with OutputDebugString, and the line that
has just & vbCrLf. Once those two lines are gone, that should take care
of it.
Aaron
On 6/22/2012 10:23 AM, Life My Way wrote:
Ok, this is what i get using the virtual view script to copy it.
Foobar media player.vbs - Microsoft VBScript compilation ...
Line 9 Column 1
ยท& vbCrLf
Expected statement
< 0x800A0400 >
Ignore Error Stop App Edit App View Help Restart App
----- Original Message -----
From: "Aaron Smith" <[email protected]>
To: <[email protected]>
Cc: "Life My Way" <[email protected]>
Sent: Friday, June 22, 2012 7:20 AM
Subject: Re: foobar 2000
Sure. What was the error you received?
Aaron
On 6/21/2012 8:17 PM, Life My Way wrote:
Arron, when i tried and place this script into window eyes i get an
error
message not sure what it is though that it will not work. can you
check
it
out please?
----- Original Message -----
From: "Aaron Smith" <[email protected]>
To: <[email protected]>
Sent: Tuesday, June 19, 2012 7:07 AM
Subject: Re: foobar 2000
In addition to what Ralf has provided, here's a quick snippet I wrote
many moons ago to get the values for menu and list items (or at
least it
used to -- I haven't tested it lately):
' Begin
Option Explicit
Const FB_MODULENAME = "FOO_UI_STD"
Const FB_LISTVIEW_CLASS = "{4B94B650-C2D8-40de-A0AD-E8FADF62D56C}"
Const FB_MENUBAR_CLASS = "ATL:ToolbarWindow32"
ConnectObject MSAAEventSource, "MSAA_"
Sub MSAA_OnObjectFocus(accObj)
OutputDebugString accobj.Window.Classname & ", " &
accObj.Role.Text
& vbCrLf
If Not accObj.Window Is Nothing Then
If accObj.Window.ClassName = FB_MENUBAR_CLASS Then
Speak "menu item " & accObj.Name
ElseIf accObj.Window.ClassName = FB_LISTVIEW_CLASS Then
Speak "list item " & accObj.Name
End If
End If
End Sub
' End
I should point out that there's no process filtering on the MSAA
events,
so if this is something you end up using, you'll want to make sure
you're only monitoring the MSAA events for Foobar.
Aaron
On 6/19/2012 3:30 AM, Ralf Kefferpuetz wrote:
I've written a small app some time ago to make the listview speak.
You
can
get it here:
https://dl.dropbox.com/u/5095431/foobar.vbs
Ralf Heinrich Kefferpuetz
Web: http://www.keffi.eu
Facebook: http://www.facebook.com/Keffi.eu
Germany
-----Original Message-----
From: Life My Way [mailto:[email protected]]
Sent: Tuesday, June 19, 2012 7:29 AM
To: [email protected]
Subject: foobar 2000
could someone take a look at foobar 2000 and see if they could
make it
more
screen reader friendly?
--
Aaron Smith
Web Development * App Development * Product Support Specialist
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.
