The GW-Scripting list is a discussion list for information regarding the development and use of Window-Eyes scripts. Any subscriber of the GW-Scripting list has the ability to post on-topic messages.

From:

 "LB" <lab_bronx@fltg.net>

Subject:

 Re: external application query

Date:

 Sun, Sep 29, 2013 8:18:55 pm
This is a multi-part message in MIME format.

------=_NextPart_000_0020_01CEBD51.1F293D00
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Sean,

When making the WE object you also must get the window you are in, the application process and all that stuff to insure the events you get are coming from the window you are in. All that is standard procedure so you and Windoweyes are in the same frame of mind so to speak...
After doing that it should work just fine as Chip states.
Bruce

Sent: Sunday, September 29, 2013 7:36 PM
Subject: RE: external application query


Sure; they're supposed to work like anyone else's events.



Chip





From: Sean Farrow [mailto:sean.farrow@seanfarrow.co.uk]
Sent: Sunday, September 29, 2013 6:36 PM
To: gw-scripting@gwmicro.com
Subject: external application query
Importance: High



Hi,

I'm in the process of writing an application and was wondering whether an external application that communicates with Window-Eyes can use events available in Window-Eyes supplied objects (i.e. OnChildClipRender).

Any help/information appreciated.

Regards

Sean.



------=_NextPart_000_0020_01CEBD51.1F293D00
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40"; xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>;
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.23520">
<STYLE>@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
LI.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
DIV.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"; FONT-SIZE: 11pt
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: windowtext; mso-style-type: personal
}
SPAN.EmailStyle18 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: personal-reply
}
..MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.WordSection1 {
page: WordSection1
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=EN-US link=blue bgColor=#ffffff vLink=purple>
<DIV><FONT size=2 face=Arial>Hi Sean,</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT>&nbsp;</DIV>
<DIV><FONT size=2 face=Arial>&nbsp;&nbsp;&nbsp; When making the WE object you
also must get the window you are in, the&nbsp; application process and all that
stuff to insure the events you get are coming from the window you are in. All
that is standard procedure so you and Windoweyes are in the same frame of mind
so to speak...</FONT></DIV>
<DIV><FONT size=2 face=Arial>&nbsp;&nbsp;&nbsp; After doing that it should work
just fine as Chip states.</FONT></DIV>
<DIV><FONT size=2 face=Arial>&nbsp;&nbsp;&nbsp; &nbsp;&nbsp;&nbsp;
Bruce</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT>&nbsp;</DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px"
dir=ltr>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Sunday, September 29, 2013 7:36
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> RE: external application
query</DIV>
<DIV><BR></DIV>
<DIV class=WordSection1>
<P class=MsoNormal><SPAN style="COLOR: #1f497d">Sure; they’re supposed to work
like anyone else’s events.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p>&nbsp;</o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d">Chip<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p>&nbsp;</o:p></SPAN></P>
<P class=MsoNormal><SPAN style="COLOR: #1f497d"><o:p>&nbsp;</o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt"> Sean Farrow
[mailto:sean.farrow@seanfarrow.co.uk] <BR><B>Sent:</B> Sunday, September 29,
2013 6:36 PM<BR><B>To:</B> <A
href="mailto:gw-scripting@gwmicro.com">gw-scripting@gwmicro.com</A><BR><B>Subject:</B>
external application query<BR><B>Importance:</B>
High<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p>&nbsp;</o:p></P>
<P class=MsoNormal><SPAN lang=EN-GB>Hi,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-GB>I’m in the process of writing an
application and was wondering whether an external application that
communicates with Window-Eyes can use events available in Window-Eyes supplied
objects (i.e. OnChildClipRender).<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-GB>Any help/information
appreciated.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-GB>Regards<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN lang=EN-GB>Sean.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
lang=EN-GB><o:p>&nbsp;</o:p></SPAN></P></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0020_01CEBD51.1F293D00--