Well fortunately because I can live with it. sorry to have wasted your valuable time on this one.
-----Original Message----- From: Aaron Smith [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 10, 2008 5:40 AM To: [email protected] Subject: Re: problem with progress bar script. Jim, The hotkey queries for progress bars immediately when you press it, so it's most likely grabbing one of the ones that are flying by. The script waits for window activation, and then goes to query the progress bars, which probably takes a nanosecond longer than the hotkey. Raul and I have both tried this on various machines, unable to duplicate the problem. Fortunately, or unfortunately, it does sound like something specific to your machine. Aaron jim grimsby Jr. wrote: > Ok this is so then then why can I read the progress of these file with the > hot key? It is not just that the progress is happing to fast. Because it > happens for a good number of files and when I minimize the program and > alt+tab back progress tones are herd and reading again. On my system at > least in this program this script just plain stops working. If no one else > can reproduce it then it is something on my system and no big deal. > > -----Original Message----- > From: Aaron Smith [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 09, 2008 2:20 PM > To: [email protected] > Subject: Re: problem with progress bar script. > > Jim, > > I can see it happening on my machine, and it's exactly as I describe, > even with the interval set using percentage instead of time. The windows > are flying by quickly, and there's no time for the script to catch the > activation. > > Aaron > > jim grimsby Jr. wrote: >> Interval? I never said that. I am not even reading based on time I am >> reading based on percent as I indicated to Doug and I have it set to play >> tones. The script just stops doing anything for a number of file and this >> can't be for the reason you describe. >> Maybe it is something with my system though. >> >> -----Original Message----- >> From: Aaron Smith [mailto:[EMAIL PROTECTED] >> Sent: Tuesday, September 09, 2008 11:28 AM >> To: [email protected] >> Subject: Re: problem with progress bar script. >> >> I tried this as well, and cannot duplicate the problem. You mentioned >> that you have the interval set to 5 seconds. It is entirely possible >> that you're simply missing some of the progress bars because they happen >> too quickly for the script to catch them within 5 seconds. I can >> certainly see that happen, but that's not a script problem. If you set >> your interval to 1 second, you'll catch them quicker. But even then, if >> the tracks being edited are small enough, the window won't stay up long >> enough for Window-Eyes to notice anything is going on. >> >> Aaron >> >> jim grimsby Jr. wrote: >>> Hi well I can only report what I see on my systems here. I should also >> add >>> I am working with very large files to split. So if you are working with > a >>> small file you might not see this effect. >>> >>> -----Original Message----- >>> From: Raul A. Gallegos [mailto:[EMAIL PROTECTED] >>> Sent: Tuesday, September 09, 2008 7:36 AM >>> To: [email protected] >>> Subject: Re: problem with progress bar script. >>> >>> Hello Jim. I just tried this with Goldwave 5.25 and auto split a file. I >>> have my progress indicator set to play ascending tones on 5 percent. I >>> don't have speech enabled for the percentages. >>> >>> I split a file and it runs through each file it splits as it creates the >>> wave file. Some of them seemed to go by so fast that there was no >>> progress, but even the ones which only took around 5 seconds to be acted >>> upon, I still got the tones playing very fast. I showed Doug my findings >>> and he's checking the script and will respond with more information. >>> However, my first guess would be that if some of these are happening so >>> fast, they may not be acted upon by the progress script. The other thing >>> however is I did not have to alt-tab away to get the progress indicator >>> to resume indicating as it would resume on its own even if it seemed to >>> skip one f the fast processed files. >>> >>> Hope this helps. >>> >>> jim grimsby Jr. said the following on 9/8/2008 11:23 PM: >>>> HELLO Doug, >>>> >>>> I performed the test you requested and the results are as follows. >>>> Speech and the tone stop. >>>> >>>> I am able to read the information with the progress bar hot key. It >>>> changes and so does the title when you go from one file to another. The >>>> progress bar script does nothing. For a while and then it will figure >>>> out that it needs to read a while longer. >>>> >>>> It figured this out always after the active foreground window changed >>>> for a second. Usually this does not happen but sometimes it does. >>>> >>>> Hth >>>> >>>> *From:* Doug Geoffray [mailto:[EMAIL PROTECTED] >>>> *Sent:* Monday, September 08, 2008 6:25 PM >>>> *To:* [email protected] >>>> *Subject:* Re: problem with progress bar script. >>>> >>>> >>>> >>>> Jim, >>>> >>>> So what if you also enable the speech to indicate the progress? I'm >>>> wondering if something is happening where it can't play the .wav files >>>> for the ascending tones? Enabling the speech indication would be a good > >>>> test of this. >>>> >>>> Regards, >>>> Doug >>>> >>>> jim grimsby Jr. wrote: >>>> >>>> Hi Doug ok no problem. >>>> >>>> First I have it set to play ascending tones. It is set at >>>> >>>> 5% intervals speak progress is not checked. >>>> >>>> The progress hot key does infact change when I press it. >>>> >>>> For example it might show 10 percent when I press it the first time and >>>> then 35 percent the next as you would expect. >>>> >>>> Like I said this window goes and split a number of files in to smaller >>>> files. So it show it gets to the 100% mark and then stops tracking all >>>> other progress after that on the next file and the next etc. the hot >>>> key does however reflect the changing progress. >>>> >>>> I have another file to split here shortly would it help if I turned on >>>> speech to see if it only effects the playing of sound? >>>> >>>> >>>> >>>> *From:* Doug Geoffray [mailto:[EMAIL PROTECTED] >>>> *Sent:* Monday, September 08, 2008 2:26 PM >>>> *To:* [email protected] <mailto:[email protected]> >>>> *Subject:* Re: problem with progress bar script. >>>> >>>> >>>> >>>> Jim, >>>> >>>> So how do you have Progress Bar indicator configured? Meaning are you >>>> reading the progress bar in seconds or by percentage? What is your >>>> interval regardless? If you press the Progress Or Scroll bar is the >>>> percentage changing as you would expect? Can you tell me the last thing > >>>> the script speaks for you and what the hotkey is now speaking for you? >>>> >>>> Doug >>>> >>>> jim grimsby Jr. wrote: >>>> >>>> Hi Doug the window is still active and the commands you site work as I >>> would >>>> expect. I thought of this and made sure before I reported the problem. > I >>>> also tried to tab around the dialog and was able to move the focus from >>> the >>>> cancel button to the priority list box with no problem. The window is >>> very >>>> much active. >>>> >>>> >>>> >>>> -----Original Message----- >>>> >>>> From: Doug Geoffray [mailto:[EMAIL PROTECTED] >>>> >>>> Sent: Monday, September 08, 2008 12:37 PM >>>> >>>> To: [email protected] <mailto:[email protected]> >>>> >>>> Subject: Re: problem with progress bar script. >>>> >>>> >>>> >>>> Jim, >>>> >>>> >>>> >>>> My guess would be that activation is going away from the window with the > >>>> progress bars. What if you speak the current titlebar when they stop >>>> >>>> reading? What if you press the Window-Eyes Progress Or Scroll Bar >>>> >>>> hotkey (control-insert-b). If it speak the progress bar then the script > >>>> should as well. But if activation is changing as I suspect, none of >>>> >>>> these will speak until activation goes back there. >>>> >>>> >>>> >>>> Regards, >>>> >>>> Doug >>>> >>>> >>>> >>>> jim grimsby Jr. wrote: >>>> >>>> >>>> >>>> Hello, >>>> >>>> There is a problem with the progress bar script where if you are in >>> the >>>> >>>> >>>> same >>>> >>>> >>>> >>>> window that is performing task after task after a while progress >> bars >>>> >>>> >>>> stop >>>> >>>> >>>> >>>> sounding a tone or reading. >>>> >>>> You can reproduce this problem easily buy doing the following. Bring >>> up >>>> >>>> >>>> gold >>>> >>>> >>>> >>>> wave. >>>> >>>> Now open a large mp3 file or whatever. Just as long as it is big. >>>> >>>> Now auto cue the mp3 file. >>>> >>>> Ok now split it. after a while progress bar reading will stop and >> you >>>> >>>> >>>> will >>>> >>>> >>>> >>>> have to minimize gold wave and talt tab in to it again to get >> progress >>> bar >>>> indication back. >>>> >>>> Or sometimes window-eyes will start reading it on its own if the >>> window >>>> title changes long enough for window-eyes to catch it. >>>> >>>> Hth. >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> -- >>>> >>>> Doug Geoffray >>>> >>>> GW Micro, Inc. >>>> >>>> Voice 260-489-3671 >>>> >>>> Fax 260-489-2608 >>>> >>>> http://www.gwmicro.com >>>> >>>> >>>> >>>> -- >>>> >>>> Doug Geoffray >>>> >>>> GW Micro, Inc. >>>> >>>> Voice 260-489-3671 >>>> >>>> Fax 260-489-2608 >>>> >>>> http://www.gwmicro.com >>>> > -- To insure that you receive proper support, please include all past correspondence (where applicable), and any relevant information pertinent to your situation when submitting a problem report to the GW Micro Technical Support Team. Aaron Smith GW Micro Phone: 260/489-3671 Fax: 260/489-2608 WWW: http://www.gwmicro.com FTP: ftp://ftp.gwmicro.com Technical Support & Web Development
