Hi Dave, Well, what can I tell you?! This is what FS says, & there must be some kind of method to their madness, so to speak! I don't have the scripting knowledge to understand what will happen if the line of text is inserted into the JSS file being that the semicolon is at the beginning of the line of text. From my very limited script knowledge that semicolon basically tells Jaws to ignore that line of text so, if that's true I wouldn't have a clue as to what that would mean. I guess the important thing would be to know exactly where in the JSS file this line of text goes in order to know what effect it would have with prior scripts. My guess would be that this JSS text line insertion is only a temporary fix of some sort for Jaws 17 & earlier until FS gets the merge utility configured & ready for prime time use. Hopefully Señor Eric Damry will wade in on this topic & clarify for us what's happening. Take care. Mike
----- Original Message ----- From: Dave Carlson To: [email protected] Sent: Saturday, December 12, 2015 9:10 PM Subject: Re: [JAWS-Users] JAWS 16 scripts with JAWS 17 Mike, This makes no sense, what FS posted. First, it sounds like this makes a JAWS 17 script compatible with prior versions of JAWS, not forward-compatible. Second, that line, even without the quotes, is prefaced with a semicolon, which makes it simply a comment line, and not executed or compiled. Dave Carlson Oregonian, woodworker, Engineer, Musician, and Pioneer ----- Original Message ----- From: "Mike B" <[email protected]> To: <[email protected]> Sent: Saturday, December 12, 2015 08:29 PM Subject: Re: [JAWS-Users] JAWS 16 scripts with JAWS 17 Hi Steve, Is this the section in what's new in Jaws 17 you're referring to? Compatibility Mode option has been removed from Script Manager and the -c command line switch has been removed from scompile.exe. To compile scripts that will work with prior versions of JAWS, you must now insert the following line without the quotes into your JSS file: ";#pragma usePoFile 0" list end Take care. Mike ----- Original Message ----- From: Steve To: [email protected] Sent: Saturday, December 12, 2015 8:10 PM Subject: Re: [JAWS-Users] JAWS 16 scripts with JAWS 17 Did you try putting that command in the .jss file that they referred to in the Jaws 17.1224 update. It is supposed to make some scripts compatible with the new script manager. ----- Original Message ----- From: Greg Washington To: [email protected] Sent: Saturday, December 12, 2015 9:19 PM Subject: Re: [JAWS-Users] JAWS 16 scripts with JAWS 17 Not sure if this will be a problem for you but the scripts for Quicken 2003 do not work in the latest update of Jaws 17 but do work in Jaws 16. I am in conversation with Freedom Scientific to see if this can be resolved. Greg Washington -----Original Message----- From: JAWS-Users-List [mailto:[email protected]] On Behalf Of Reed Poynter Sent: Saturday, December 12, 2015 8:05 PM To: [email protected] Subject: [JAWS-Users] JAWS 16 scripts with JAWS 17 Hello, What should my expectations be? Can I copy my scripts compiled under JAWS 16 into my JAWS 17 ENU folder and expect them to work properly? Anything in particular that I should look out for? Thanks, Reed For answers to frequently asked questions about this list visit: http://www.jaws-users.com/help/ For answers to frequently asked questions about this list visit: http://www.jaws-users.com/help/ For answers to frequently asked questions about this list visit: http://www.jaws-users.com/help/ For answers to frequently asked questions about this list visit: http://www.jaws-users.com/help/ For answers to frequently asked questions about this list visit: http://www.jaws-users.com/help/ For answers to frequently asked questions about this list visit: http://www.jaws-users.com/help/
