Yep, that is too big for 32 bits.
Only way I can think of is to write yourself a function to take it as a
string, and tear the string in two, and process each half separately. I
expect you could probably make that work. Not sure what your use case is.
As written, just say the string instead of the integer.
+--------------------------------------------------------------------------+
Listen to The Snowman on MushroomFM.com, Saturday evenings, 8PM Eastern
time.
60's and 70's tunes, and gently conservative talk.
----- Original Message -----
From: "Doug Lee" <doug.lee@xxxxxxxxxxxxxxx>
To: <jawsscripts@xxxxxxxxxxxxx>
Sent: Friday, February 02, 2018 6:14 AM
Subject: [jawsscripts] Re: SayInt Limit
I believe JAWS scripting integers are always treated as 32-bit signed
values. There are various ways of specifying them, including things like
0xD373AC7D (which is the hex version of your value); but I'm not sure that
will help you.
I did try the following odd sequence, on the theory that handles should be
unsigned:
var variant v = 0xD373AC7D
var handle x = v
sayInteger(x)
But on JAWS 2018 I still get a negative result spoken.
On Fri, Feb 02, 2018 at 11:30:46AM +0000, Bob wrote:
Another odd question, using Jaws 17 for this one.
SayInt (3547573373) is announcing minus 1
Is there any way to work around this?
Thanks
Bob
__________???
View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts
--
Doug Lee, Senior Accessibility Programmer
Level Access (formerly SSB BART Group)
mailto:Doug.Lee@xxxxxxxxxxxxxxx http://www.LevelAccess.com
"While they were saying among themselves it cannot be done,
it was done." --Helen Keller
__________�
View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts
__________�
View the list's information and change your settings at
http://www.freelists.org/list/jawsscripts