Hmm, that was weird, I don't recall sending that message. Well,
consider this take 2 of the pervious message which ended rather abruptly.
Occasionally, when I exit window-eyes either by closing the window
itself of the control pannel or using the quickquit.vbs script,
window-eyes will say that it's already running if I try to relaunch it.
I have tried a manual start of the gwtoolkit, and the homersharedobject
aps and then combinations of the relaunch we and quickquit aps. Well,
it's like when you take your car to the mechanic and whatever was wrong
in the garage is perfectly fine in the shop; we worked flawlessly
through all tests. But wait! don't close the message just yet! thanks.
Is anyone else seeing the same issue? When it happens, I have to use the
kill wineyes script and then launch we again, which necessitates a
relaunch of we so that items in list and tree views can read properly,
and then the cycle perpetuates. I always ask this but, am I explaining
this properly? Help? Please?
Dave c. bahr
On 12/9/2011 10:08 PM, Dave Bahr wrote:
Hi gang,
This is a problem I've been having for a bit now, since 7.5.0 I
think. When I close window-eyes via the control insert
--
Dave c. bahr
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.
GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage
your list subscription at http://www.gwmicro.com/listserv.
