[jawsscripts] Re: PS further thoughts on my last, was optimal ScreenStabilizedEvent usage?

  • From: "Geoff Chapman" <gch@xxxxxxxxxxxxxxxx>
  • To: <jawsscripts@xxxxxxxxxxxxx>
  • Date: Wed, 7 Nov 2012 23:03:28 +1100

hahahahaha. so obscure it went right over my head!
<grin.>
But, I did non-advanced maths when I was at school eh.

such a short time ago hahaha.


----- Original Message ----- 
From: "Andrew Hart" <ahart@xxxxxxxxxxxxx>
To: <jawsscripts@xxxxxxxxxxxxx>
Sent: Tuesday, November 06, 2012 6:49 AM
Subject: [jawsscripts] Re: PS further thoughts on my last, was optimal 
ScreenStabilizedEvent usage?


> Actually, telling when the screen has finished updating is not that
> simple.  The OS could make an update, and then make another update
> almost immediately after, depending on system activity and requests from
> processes, etc.  I imagine FS have simply picked a relatively short time
> to wait and if no updates are made to the screen in that interval, then
> the event fires.  However, this is probably a tricky balancing act.  If
> the interval is to short, the event for fire constantly while if the
> time interval is too long, then the event may not fire when it should.
>
> if you find it is firing too frequently for your needs, so that your
> custom code is getting run too often, you could use GettickCount to
> implement your own timer and use this to make sure your custom code gets
> run less frequently. It's just like thinning a Poisson process!  *grin*
>  Please excuse the incomprehensible and pretty pathetic maths joke, but
> I couldn't resist.
>
> Cheers,
> Andrew.
>
>> Hi
>>
>> For the application I was working on at the time, I put a line in my
>> ScreenStabilizedEvent function to append something to the clipboard each
>> time it was called.  Then I would do something simple like switch from 
>> one
>> screen to another or tab from one field to another.  After doing one of
>> those things only once, I would paste the contents of the clipboard into
>> Notepad.  I saw multiple invocations of the script.  I would then clear 
>> the
>> clipboard and try the next test.  What I wanted to point out was that 
>> just
>> because ScreenStabilizedEvent fires does not mean that the screen has 
>> been
>> completed.  The number of times it fires is going to vary between
>> applications depending on the interval between writing each chunk to the
>> screen.  I would expect ScreenStabilizedEvent to be called much less 
>> often
>> than NewTextEvent which is called for every chunk.  I was hoping that
>> ScreenStabilizedEvent would let me know when the screen is complete, but
>> that's not necessarily so.
>>
>>
>> -----Original Message-----
>> From: jawsscripts-bounce@xxxxxxxxxxxxx
>> [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Geoff Chapman
>> Sent: Monday, November 05, 2012 01:26
>> To: jawsscripts@xxxxxxxxxxxxx
>> Subject: [jawsscripts] Re: PS further thoughts on my last, was optimal
>> ScreenStabilizedEvent usage?
>>
>> Hi Mike.
>>
>> Hmmm, tha'ts certainly interesting. how do you tell the differential 
>> between
>> those two things though?
>>
>> I.e. how could you tell the screen was only being filled the once, and 
>> still
>> seeing multiple firings of ScreenStabilizedEvent?
>> and, yes, that'd be the trick eh. to know what the time factor was that 
>> jaws
>> waited before it felt appropriate to fire it.
>> putting a SayString ("beep") in there to test it, certainly it doesn't 
>> seem
>> to fire nearly as often, say, as newTextEvent does.
>>
>> ----- Original Message -----
>> From: "Mike O'Brien" <mike23432@xxxxxxxxxxx>
>> To: <jawsscripts@xxxxxxxxxxxxx>
>> Sent: Saturday, November 03, 2012 1:22 AM
>> Subject: [jawsscripts] Re: PS further thoughts on my last, was optimal
>> ScreenStabilizedEvent usage?
>>
>>
>>> Hi
>>>
>>> The description of ScreenStabilizedEvent says that it will fire when a
>>> certain amount of time has passed since the last write to the screen.
>>> I don't know what that amount of time is,, but I have seen the
>>> function fire multiple times for the same screen during it being filled
>> the one time.
>>>
>>>
>>> -----Original Message-----
>>> From: jawsscripts-bounce@xxxxxxxxxxxxx
>>> [mailto:jawsscripts-bounce@xxxxxxxxxxxxx] On Behalf Of Geoff Chapman
>>> Sent: Thursday, November 01, 2012 1:51 PM
>>> To: jawsscripts@xxxxxxxxxxxxx
>>> Subject: [jawsscripts] PS further thoughts on my last, was optimal
>>> ScreenStabilizedEvent usage?
>>>
>>> Although, thinking about this a little more, I realize that iTunes
>>> already makes the horrible swoosh noise when, it, thinks, it's
>>> finished writing all info to the iTunes store window, so perhaps I'm
>>> somewhat barking up the wrong tree in my last.  And rather what I
>>> should be asking is, how I might jolly well check when Jaws is
>>> finished getting confused/sluggish with it's refresh whole screen
>>> functionality, instead?
>>>
>>> Is there a way of using ScreenStabilizedEvent to query that? when it's
>>> osm has finished being written to, /messed with?
>>>
>>> Thanks again for any thoughts.
>>>
>>> Geoff c.
>>>
>>> ----- Original Message -----
>>> From: "Geoff Chapman" <gch@xxxxxxxxxxxxxxxx>
>>> To: <jawsscripts@xxxxxxxxxxxxx>
>>> Sent: Friday, November 02, 2012 4:22 AM
>>> Subject: [jawsscripts] optimal ScreenStabilizedEvent usage?
>>>
>>>
>>>> Mighty Scripters.
>>>> Wondering if any kind soul might feel like offering up a bit of
>>>> starter code for me, that I might be able to utilize to see if the
>>>> ScreenStabilizedEvent, function, might work in this dog-like iTunes
>>>> store,
>>>
>>>> in the iTunes application?
>>>>
>>>> It's only parameter is a variable called HwndLastScreenWrite, and I
>>>> know the class of the window recieving data when one does a search in
>>>> iTunes store, is WC_iTunesWebViewControl,
>>>>
>>>> But, just how might I write code that said something like:
>>>>
>>>>
>>>>
>>>> if you've finished writing data to
>>>>
>>>> WC_iTunesWebViewControl now, then,
>>>>
>>>> SayString ("ready")
>>>>
>>>> EndIf
>>>>
>>>> or something similar?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Of course Any aditional thoughts/comments from anyone as to
>>>> usefulness, or
>>>
>>>> otherwise, of screenStabilizedEvent, would also be  much appreciated.
>>>>
>>>>
>>>>
>>>> Thanks much for any thoughts/assistance.
>>>>
>>>>
>>>>
>>>> Geoff c.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> __________�
>>>>
>>>> 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
>>>
>>> __________�
>>>
>>> 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
>>
>> __________�
>>
>> 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
>
> 

__________�

View the list's information and change your settings at 
http://www.freelists.org/list/jawsscripts

Other related posts:

  1. Home
  2. jawsscripts
  3. Archive
  4. 11-2012