nvda-sonar-users team mailing list archive

["Chris Belle" <cb1963@xxxxxxxxxxxxx>]

yeh, believe it or not, ct  is pretty reliable at that.

but he's got so many what if's and checking going on, that's what's made 
that package so clumsy.

But there are a couple of features I really like.

Sonar uses a lot of tool-tips, and I'm still learning nvda, it can't scan 
for tool tips and such yet can it?

Or have a graphical scanner?

When I do this with window-eyes,
scan graphics, a whole lot of stuff comes up, all the things like turning on 
and off cross-fades, and automation, and the zillion controls on there.

Still, I'm amazed at how reliable and well nvda does what it does.

I sure hope when it gains features it doesn't become all messed up like the 
other guys stuff is.

is that always an inevitable consequence of developing software?

I guess it's just too hard for humans to think like machines and do 
everything in low level code, takes too much time, so we resort to these 
high level tools, and then the optimization goes out the window with the 
kruft factor etc.

But python seems so friendly to me, and all that's been done in a file less 
than 20k.

Maybe nvda will be the long awaited exception.

I do wish I could use my hardware synth though.

But good drivers are hard to write again.

and it's early days.


From: "James Teh" <jamie@xxxxxxxxxxx>
To: <nvda-sonar-users@xxxxxxxxxxxxxxxxxxx>
Sent: Thursday, December 13, 2012 5:28 AM
Subject: Re: [Nvda-sonar-users] ordering effects


> On 13/12/2012 9:19 PM, Chris Belle wrote:
> > I'm not sure how ct is handling it, screen scraping, or calling a window
> > control, since we can't see those scripts.
> Is CT reliable at doing this?
>
> > but jaws users have always had trouble getting effects to go in a
> > certain order on a track or bus strip.
> I remember. To add to this nuisance, Sonar isn't reliable in terms of 
> where it inserts effects. Sometimes, even if you position your cursor on 
> one effect, it always inserts in the wrong place.
>
> > I usually resort to window-eyes and it's slightly better precise mouse
> > movement, well jaws can do, it too, but when pixel poking, I'll give the
> > nod to window-eyes, and click right above or below the effect in
> > question
> NVDA can't even see the effect names with its screen scraping at present, 
> so this probably isn't going to be possible for now. Even if it could, 
> it'd be unreliable at best; screen scraping always is.
>
> Actually, there's a lot in Sonar that NVDA's screen scraping can't see, 
> which is something we're trying to figure out at the moment. It should 
> always be a last resort, but sometimes, it's a very useful last resort.
>
> Jamie
>
> --
> James Teh
> Email/MSN Messenger/Jabber: jamie@xxxxxxxxxxx
> Web site: http://www.jantrid.net/
> Twitter: jcsteh
>
> --
> Mailing list: https://launchpad.net/~nvda-sonar-users
> Post to     : nvda-sonar-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~nvda-sonar-users
> More help   : https://help.launchpad.net/ListHelp