PS. Sorry, forgot to thank you for your acknowledgement of my random thoughts re ToolTip reading not being enabled by default, and for warning re enabling TetherJawsToPc, as regards menu usage. I was aware of that caveat, but useful to have it voiced up here in case others see the function as a "one-fits-all" solution to things, which, as you so wisely point out, it certainly isn't. but, boy, it's a handy little exploration tool I assure you. Even in Audible Download manager today,I decided to tab around and route JawsToPc at every stop, with ToolTip reading enabled, and found out a couple of very reassuring, and elpful little tips that I never knew before! I'd reeeeally also one day, like to discuss up here, people's methods of how they might go about getting non-standard popup ToolTip-like events, to trrigger jaws' auto Reading of those. but, I must resubject that posting of course. You know what I mean though? there are a heap of situations I reckon, where popups occur as a result of mouseOver stuff, particularly on the web, but other local apps as well, which jaws simply doesn't auto read, and one wonders if: (a) one could perhaps simply reclassify the event to be, "Picked up" by the ToolTip auto-read function, they also could be brought to life, and/or (b) working out whether the text presented was readable by jaws anywayz, like if it wasn't just a bitMap popup which wouldn't be. etc. groan. soooo much to learn! From: "Don Marang" <donald.marang@xxxxxxxxx> To: <jawsscripts@xxxxxxxxxxxxx> Sent: Sunday, February 27, 2011 9:06 PM Subject: [jawsscripts] Re: JAWSWillFollowPc/TetherJawsToPC Broken in Jaws 10, 11 and 12. > The tether function must work at either the FocusChangedEvent level or > lower, such as internally. I will see if I can reproduce your results. > It > worked the way I expected a year or two ago. This had to be at least JAWS > 9, because I jumped from 5.1 to 9. I originally thought this was an > answer > to a problem I had writing scripts for Verizon. I will check the dates an > version I was using. I think this was on Windows 7 as well, which would > mean at least JAWS 10. > > Tethering effects much more than the movements of the focus caused by the > Tab key. It is not desirable for this feature to be the default. For one > thing, when using an arrow key through a menu, it will automatically open > and move into all submenus! > > I totally agree with you about the ToolTip verbosity. > > Don Marang > Vinux Software Development Coordinator (vinux.org.uk) > > There is just so much stuff in the world that, to me, is devoid of any > real > substance, value, and content that I just try to make sure that I am > working > on things that matter. > Dean Kamen > > > -------------------------------------------------- > From: "Geoff Chapman" <gch@xxxxxxxxxxxxxxxx> > Sent: Thursday, February 24, 2011 8:25 PM > To: <jawsscripts@xxxxxxxxxxxxx> > Subject: [jawsscripts] JAWSWillFollowPc/TetherJawsToPC Broken in Jaws 10, > 11 and 12. > >> mighty scripters. >> Just letting people know of another unfortunate breakage that seems to >> have crept in unnoticed or uncared about over the past 3 versions, and >> that's what is, in my view, >> the rather handy newby application exploration feature, of today's >> subject >> line., viz, JAWSWillFollowPC. Or, as the actual Script is named, >> TetherJawsToPc. >> >> grumph! >> >> I have spent some time today, seeking to drill down into some of the >> functions/scripts which might've caused this, as it would seem on the >> surface a relatively simple one to repair maybe? but have had no luck in >> tracking it down myself. >> The Actual TetherJawsToPc script looks identical to me between jaws >> versions 9 and 10, >> so am presuming the problem must be somewhat deeper, i.e. buried in one >> of >> the functions related to tabKey or shiftTabKey pressing itself? >> which appear to be one's maybe like, SayFocusedObject, or >> SayObjectTypeAndText, or perhaps, GetObjectHelp? >> >> The Tether JawsToPc Script appears to me to just toggle the jcf option, >> (opt_Tether_Jaws_To_PC, from one setting to another, >> So I presume, that something in the tab and shiftTab key pressing >> functions, is maybe not checking for this setting in the relevant jcf >> file? >> and subsequently executing a routeJawsToPc based on it's 1 or 0? >> something >> like this perhaps? >> >> but something sure changed though between jaws 9 and 10, because tha'ts >> where it's been broken, and remained broken ever since. >> >> For those who may not be aware of this little gem, >> (when it actually functions properly,) >> When coupled with Auto ToolTip reading option set to on, (which is set >> individually within the prefferences section for each verbosity level, in >> the verbosity dialog, >> - which is, not, the default setting for jaws, for reasons which have >> always totally eluded me,) >> when tethering jawsToPc, it can give a very handy way of hearing, what >> particular buttons or controls may do in an application, which activate >> the normal toolTip event class when mouse hovers over a control. it >> basically means your mouse will follow your pc focus, and thus speak all >> those tooltips automatically for you, if any are present. >> >> one can also of course check it's functionality simply by first >> activating >> the jawsCursor, turning on the tetherJawsToPc function with >> Jawskey+Control+NumPad minus, pressing Tab, then pressing AltDelete, to >> check the jawsCursor Coordinates. >> When it's working properly, of course if the tab key is moving focus >> around an application window, like, for example, the winamp or vlc >> preferences dialog, >> pressing alt+delete after a tab press, should yield a change in the >> coordinates output, >> along with tooltips auto spoken, if that option has been enabled. >> Also, subsequently pressing RouteJawsToPc, when the function is working >> properly, then executing alt+delete again, should also, not, yield any >> change in the coordinates, when jawsCursor is active. >> However as you'll notice in jaws 10, 11 or 12, carying out the above, >> does, yield a change, meaning it's not tracking as it should. >> >> any thoughts from anyone as to how one might dig down further to find out >> where this has come adrift? >> or if anyone would care to have a shot themselves and let us know ... >> even >> better! <grin.> >> But not an urgent one, just something I'd like to fix. >> >> >> thanks muchly. >> >> geoff c. >> >> >> >> >> __________� >> >> View the list's information and change your settings at >> //www.freelists.org/list/jawsscripts >> >> > __________� > > View the list's information and change your settings at > //www.freelists.org/list/jawsscripts > > __________� View the list's information and change your settings at //www.freelists.org/list/jawsscripts