Ok Doug, here you go.

I am carbon coping a message to the list I sent you minus the converted setfiles ofcourse since attachments aren't allowed to the list I imagine.

But others who might be helping trouble shoot this can follow along and as you indicated, this might be better served publically.


Here is my list of problems, and the converted setfiles.

The sets aren't properly associated, except the first one but the loader set doesn't load which gets the other setfiles.

If I have this straight, Tom used two associations.

The main
SF7DataWin.000
and he also used loader sets associated with other window classes to load other setfiles.

Well, the main
SF7DataWin.000
is associated, but the SF7Loader1.000
is not associated.

I was able to re-associate it and then when I loaded the graphic eq module in soundforge, the proper setfile loaded but what used to work and voice doesn't with we 7.

What I have going on is a hyperactive window obtaining focus and then speaking a user window
and then activating it.

That way the slider function speaks, and it's value will speak when you change the arrows or page up and down.

When ;you tab around the eq values will read, they do fine with we 6.1

This pattern of breakage exhibits more or less all through soundforge with we7.1 I can fix then to work in we 7 but the over-haul is extensive.

I think the hyperactive windows are tracking, but they're not voice the slider values for some reason like they were in we 6.1 I could define another hyperactive window to voice this, but why should I have to when activating the window and giving it focus was enough in we 6.1?

Has something in the code changed?

If I turn on hyperactive messages, I can see the windows changing, but the values don't read anymore.

HOpefull        y, this will be clear to you.

Regards,
Chris.


At 08:20 AM 7/15/2009, you wrote:
Chris,

I'm posting to the list because as you stated, if this is a big problem it needs to be discussed so everyone is aware.

I received the Window-Eyes 6.1 set files for Sound Forge 8 and for Sound Forge 7 but I did not get the converted Window-Eyes 7.x versions of this or the list of what settings you found to be different after the conversion. Given these are very complex set files I didn't want to go through all 76 windows for all 56 sets <smile>. So in addition to the 6.1 sets, please send me the 7.0 converted versions and a list of settings which did not convert properly from 6.1 to 7.0. From your message you specifically listed hyper window coordinates or something.

Regards,
Doug

Doug Geoffray wrote:
Chris,

The information you received was not correct. The set association change was done from 5.5 to 6.0 and the 6.0 readme.txt file did explain the change and consequence and resolution very clearly. Since you are having issues from 6.1 to 7.0 this is not the case.

I don't remember the set file issue you are having but how about this? Please send me the 6.1 version of the set file and the 7.x version of the set file and specifically tell me what window, whether it is a standard or hyperactive and what the 6.1 format has for the coordinates and what the 7.x has for the coordinates or whatever the discrepancy is. This will allow me to verify what happened if indeed there was a conversion problem.

Also, given how bad this problem is for you using this one application, have you noticed any other set files with the same problem? It seems likely if the set file conversion has issues that it would effect all or many of your other set files. Also, keep in mind when we update our factory sets, we run them through the exact same wefixset utility that you are using.

Regards,
Doug

Chris Belle wrote:
Hmmmm, now this is very interesting.

I was told that there were some very minor changes in setfiles to improve them but they shouldn't break.

If setfiles get broken this bad and if this is a known thing or something that is a sacrifice for the better from an engineering stand-point, then something should be put in the readme to the effect, because it's not minor, it's major, because lots of hard work can be hosed.

There wasn't enough follow-through or attention given to this last year when this should have been addressed.

For us non-programmer types, setfile creation is the closest thing to a configurable environment we have, maybe until scripting grows up to where window-eyes gets something as comprehensive and powerful as say the Snowman's hotspot clicker, for jaws, smile.


At 03:22 PM 7/13/2009, you wrote:
I have an idea, the coordinates might be different by a few pixels,
but the way set files are associated has changed from 6.1 to 7.1 very
greatly, so you will have to do the associations all over again.

Hope this helps.

on Monday 07/13/2009 Chris Belle([email protected]) wrote
 > Hi Chip?
 >
 > I did do exactly what you suggested, and got no where.
 >
 > I have since been able to duplicate this problem with a competent
 > technician colleague who I work with regularly, this morning as a
 > matter of fact.
 >
 > Sure enough, setfiles that work well for soundforge 7b with we 6.1
 > will break badly under we7 and not load correctly, hyperactive window
> cordinates will be messed up, and associations for loading will be messed up.
 >
 > I was told that this was probably something specific to my machine.
 >
> Now I have good evidence that it is not so and that window-eyes is at fault.
 >
 >          At 11:18 AM 7/13/2009, you wrote:
> >why don't you send the set files to support, with a detailed explanation
 > >of how things work under 6.1, and a detailed explanation of what it
 > >takes to see they're broken under 7.1?
 > >
 > >
 > >
 > >
 > >
 > >
 > >------------------------------
 > >
 > >Chip Orange
 > >Database Administrator
 > >Florida Public Service Commission
 > >
 > >[email protected]
 > >(850) 413-6314
 > >
 > >  (Any opinions expressed are solely those of the author and do not
 > >necessarily reflect those of the Florida Public Service Commission.)
 > >
 > >
 > > > -----Original Message-----
 > > > From: Chris Belle [mailto:[email protected]]
 > > > Sent: Monday, July 13, 2009 1:10 AM
 > > > To: [email protected]
 > > > Subject: Re: FW: 7.1 stability problems
 > > >
 > > > I've gotten the same here on several ocasions.
 > > >
 > > > After abandoning we 7.0 in frustration because of a failure to
> > > communicate to gwmicro my issues for various reasons I won't go in to
 > > > here, I decided to give we7.1 a test drive.
 > > >
> > > To their credit, one issue that's seems to have been resolved is the
 > > > drag and drop issue, it now seems to be working.
 > > >
 > > > This was broken in the we7 release.
 > > >
 > > > My test drive of it with levelator with we7.1 seems to work now.
 > > >
 > > > One very serious problem I am having with we since the whole we7
 > > > cycle began is the issue of  setfiles being broken between
 > > > we6.1 and we7.
 > > >
> > > I have some very extensive and very well written soundforge setfiles
 > > > written by my good friend Tom Kingston whom I beta tested for
 > > > last year.
 > > >
 > > > These setfiles add a lot of functionallity and usability to
> > > soundforge 8, and I modifyed them to work with my prefered soundforge
 > > > 7 installation.
 > > >
 > > > When I upgraded to we7 in any of it's incarnations, these setfiles
> > > neither load correctly, and window cordinates are messed up, and all
 > > > kinds of strange things happen.
 > > >
> > > I've had some very brief conversation with gwmicro over this but have
 > > > never gotten this satisfactorily addressed.
 > > >
 > > > There is no change with we7.1, the setfiles are still very broken.
 > > >
 > > > The basic structure of the setfiles is this, there are two loader
 > > > sets which are associated with different modules in soundforge, and
> > > hyperactive windows will trigger and load the appropriate setfile as > > > needed for any given window, so when you want to create a new setfile > > > for a new part of the forge, you just make a new setfile and load it
 > > > with a hyperactive window from one of the loader sets.
 > > >
 > > > Pretty slick, kind of what I used to do with the ram locations with
 > > > vocal-eyes and branching remember when we only had 10 hyperactive
 > > > windows, my have we come a long way.
 > > >
 > > >   something changed in we7 which broke these setfiles.
 > > >
 > > > Any enlightening information would be appreciated.
 > > >
 > > > Regards.
 > > >
 > > >
 > > >
 > > >          At 04:36 PM 7/12/2009, you wrote:
> > > >I am having the same problem. If you move around to quick in windows
 > > > >explorer or internet explorer w e will crash.
 > > > >
 > > > >Edward
 > > > >
 > > > >
 > > > >-----Original Message-----
 > > > >From: Chip Orange [mailto:[email protected]]
 > > > >Sent: Sunday, July 12, 2009 3:29 PM
 > > > >To: [email protected]
 > > > >Subject: RE: 7.1 stability problems
 > > > >
 > > > >Yes, Bill, I was; then I switched to dec-talk access 32,
 > > > from Eloquence, and
 > > > >things do seem much better.  why not try that and see if it
 > > > makes a big
 > > > >difference; it will help them a lot, in tracking it down, if
 > > > you find this
 > > > >out.
 > > > >
 > > > >Chip
 > > > >
 > > > >
 > > > >-----Original Message-----
 > > > >From: Bill Holton [mailto:[email protected]]
 > > > >Sent: Sunday, July 12, 2009 2:32 PM
 > > > >To: [email protected]
 > > > >Subject: 7.1 stability problems
 > > > >
 > > > >Hi.
 > > > >
 > > > >Is anyone else having trouble with 7.1 when you start moving
 > > > fast around the
 > > > >computer?  I have WE 7.1 stop talking on both my XP and
 > > > Vista machines, both
 > > > >using eloquence, if I start keying around too fast with
 > > > either Windows keys
 > > > >or WE hotkeys.  The rest of the sounds on the PC work fine,
 > > > and it's not
 > > > >locking up, but it takes speech about ten seconds to start
 > > > again.  Other
 > > > >times it doesn't start again, and the only way to get WE
 > > > back is to do a
 > > > >hard reset.
 > > > >
 > > > >On my Vista machine, I also have a problem I have had ever
 > > > since I started
 > > > >using Vista, only now it happens more frequently.  Speech
 > > > will die, the
 > > > >other sounds are working fine, and the only way to get WE
 > > > back is to turn
 > > > >the machine off or do a start menu restart.  Then, just
 > > > before Windows shuts
 > > > >down, the speech comes back fine, for about two seconds,
 > > > then the machine is
 > > > >restarted.  This is very frustrating.  Anyone else having
 > > > this situation?
 > > > >
 > > > >Thanks.  Bill
 > > > >
 > > > >Bill
 > > > >
 > > > >
 > > > >
 > > > >If you reply to this message it will be delivered to the
 > > > original sender
 > > > >only.  If your reply would benefit others on the list and
 > > > your message is
 > > > >related to GW Micro, then please consider sending your message to
 > > > >[email protected] so the entire list will receive it.
 > > > >
 > > > >All GW-Info messages are archived at
 > > > http://www.gwmicro.com/gwinfo, and can
 > > > >be searched through and sorted using the search form at the
 > > > bottom of the
 > > > >page.
 > > > >
 > > > >If you wish to unsubscribe from this list, send a message to
 > > > >[email protected] and include leave gw-info in the body
 > > > of the message.
 > > > >
 > > > >If you reply to this message it will be delivered to the
 > > > original sender
 > > > >only.  If your reply would benefit others on the list and
 > > > your message is
 > > > >related to GW Micro, then please consider sending your message to
 > > > >[email protected] so the entire list will receive it.
 > > > >
 > > > >All GW-Info messages are archived at
 > > > http://www.gwmicro.com/gwinfo, and can
 > > > >be searched through and sorted using the search form at the
 > > > bottom of the
 > > > >page.
 > > > >
 > > > >If you wish to unsubscribe from this list, send a message to
 > > > >[email protected] and include leave gw-info in the body
 > > > of the message.
 > > > >
 > > > >If you reply to this message it will be delivered to the original
 > > > >sender only.  If your reply would benefit others on the list and
 > > > >your message is related to GW Micro, then please consider sending
 > > > >your message to [email protected] so the entire list will
 > > > receive it.
 > > > >
> > > >All GW-Info messages are archived at http://www.gwmicro.com/gwinfo,
 > > > >and can be searched through and sorted using the search
 > > > >form at the bottom of the page.
 > > > >
 > > > >If you wish to unsubscribe from this list, send a message to
 > > > >[email protected] and include leave gw-info in the body
 > > > >of the message.
 > > >
 > > > If you reply to this message it will be delivered to the original
 > > > sender only.  If your reply would benefit others on the list and
 > > > your message is related to GW Micro, then please consider sending
 > > > your message to [email protected] so the entire list will
 > > > receive it.
 > > >
 > > > All GW-Info messages are archived at
 > > > http://www.gwmicro.com/gwinfo, and can be searched through
 > > > and sorted using the search
 > > > form at the bottom of the page.
 > > >
 > > > If you wish to unsubscribe from this list, send a message to
 > > > [email protected] and include leave gw-info in the body
 > > > of the message.
 > > >
 > > >
 > >
 > >If you reply to this message it will be delivered to the original
 > >sender only.  If your reply would benefit others on the list and
 > >your message is related to GW Micro, then please consider sending
> >your message to [email protected] so the entire list will receive it.
 > >
 > >All GW-Info messages are archived at http://www.gwmicro.com/gwinfo,
 > >and can be searched through and sorted using the search
 > >form at the bottom of the page.
 > >
 > >If you wish to unsubscribe from this list, send a message to
 > >[email protected] and include leave gw-info in the body
 > >of the message.
 >
 > If you reply to this message it will be delivered to the original
 > sender only.  If your reply would benefit others on the list and
 > your message is related to GW Micro, then please consider sending
 > your message to [email protected] so the entire list will receive it.
 >
> All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the search
 > form at the bottom of the page.
 >
 > If you wish to unsubscribe from this list, send a message to
 > [email protected] and include leave gw-info in the body
 > of the message.

--
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         [email protected]

If you reply to this message it will be delivered to the original
sender only.  If your reply would benefit others on the list and
your message is related to GW Micro, then please consider sending
your message to [email protected] so the entire list will receive it.

All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the search
form at the bottom of the page.

If you wish to unsubscribe from this list, send a message to
[email protected] and include leave gw-info in the body
of the message.

If you reply to this message it will be delivered to the original
sender only.  If your reply would benefit others on the list and
your message is related to GW Micro, then please consider sending
your message to [email protected] so the entire list will receive it.

All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be searched through and sorted using the search
form at the bottom of the page.
If you wish to unsubscribe from this list, send a message to
[email protected] and include leave gw-info in the body of the message.

--
Doug Geoffray
GW Micro, Inc.
Voice 260-489-3671
Fax 260-489-2608
http://www.gwmicro.com
At 07:43 PM 7/14/2009, you wrote:

If you reply to this message it will be delivered to the original
sender only.  If your reply would benefit others on the list and
your message is related to GW Micro, then please consider sending
your message to [email protected] so the entire list will receive it.

All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be 
searched through and sorted using the search
form at the bottom of the page.
If you wish to unsubscribe from this list, send a message to
[email protected] and include leave gw-info in the body of the message.

Reply via email to