Sean,
Could you elaborate a bit more?
Doug
Sean Farrow wrote:
Hi Doug:
Perhaps a new dialog with a treeview and a checkbox?
Sean.
------------------------------------------------------------------------
*From:* Doug Geoffray [mailto:[EMAIL PROTECTED]
*Sent:* 22 September 2008 18:40
*To:* [email protected]
*Subject:* Re: determining when an edit/rich edit refreshes
Sean,
This certainly is something that could be added. But in most cases,
adding a feature like this becomes complicated. Not by the
implementation, that's easy. But by the user interface. Meaning how
can the user specify the window? Does this block all events outside
this window or only certain ones? Do you want just this window or any
window and its children? These are questions I immediately thought
of. I'm sure many more would come up. Obviously you can give me your
personal need but we have to look at the full impact. If the feature
is too specific or becomes too much work to set it up the feature
doesn't get used.
Of course the other option is Aaron's favorite on liner, "You've got
the source code" <smile>.
Regards,
Doug
Sean Farrow wrote:
Hi:
As this discussion went along, I was thinking how nice it would be to restrict the events we see with the weEvent script to certain windows somehow, whether that be by control id/iaccessible/some other method.
Would this be a useful feature/would this be something gw would look to adding?
Cheers
Sean.
-----Original Message-----
From: Aaron Smith [mailto:[EMAIL PROTECTED]
Sent: 22 September 2008 16:57
To: [email protected]
Subject: Re: determining when an edit/rich edit refreshes
Marlon Brandão de Sousa wrote:
A k. I was thinking about scripting apps like instant messaging ones,
if I would have to, let's say, keep collecting text from the history
window once each second and comparing it with the previous test to
make the incoming messages be anounced automatically.
Marlon
In that case, I would watch to see what MSAA events come through when a new
message arrives. It's possible that you could trigger on something like that.
Aaron
--
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
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 3460 (20080922) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 3460 (20080922) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
--
Doug Geoffray
GW Micro, Inc.
Voice 260-489-3671
Fax 260-489-2608
http://www.gwmicro.com
__________ Information from ESET NOD32 Antivirus, version of virus
signature database 3460 (20080922) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
__________ Information from ESET NOD32 Antivirus, version of virus
signature database 3460 (20080922) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
--
Doug Geoffray
GW Micro, Inc.
Voice 260-489-3671
Fax 260-489-2608
http://www.gwmicro.com
