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:

 "RicksPlace" <ofbgmail@mi.rr.com>

Subject:

 Re: WE And Microsoft Development Environments

Date:

 Sat, Apr 14, 2012 5:01:19 am
This is a multi-part message in MIME format.

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

Hi Aaron.
Thanks again and I will continue experimenting with it today.
My old Script (App) defined (Registered) a Hot Key that worked and I think accessed a Window Object's Properties and Events.
If these work that will demo:
Use of MSAA;
Use of a Window Object;
Use of a Hot Key.
That should make for a pretty decent intro demo and tutorial to post up someplace.
I will likely continue with a second Demo and Tutorial with a few more features after this one.
So far so good.
Rick USA
----- Original Message -----
From: Aaron Smith
To: gw-scripting@gwmicro.com
Sent: Friday, April 13, 2012 8:35 PM
Subject: Re: WE And Microsoft Development Environments


On 4/13/2012 5:19 PM, RicksPlace wrote:
It still needs some testing and the Form1 grabs focus sometimes even though hidden.


You can keep the form from displaying by creating a Main() routine, and putting your startup logic there:


Sub Main()
' Instantiate your form
Dim myForm as Form1 = New Form1()

' Put initialization stuff here instead of in Form_OnLoad

' Continue on without displaying the form
Application.Run()
End SubIf you then ever need to show the form, you can do myForm.Show()

You can do this in C#, too, by changing code in the Main() function in Program.cs from:

Application.Run(new Form1());

to

Form myForm = new Form1();
Application.Run();

Aaron

--
Aaron Smith
Web Development * App Development * Product Support Specialist
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * 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.
------=_NextPart_000_0014_01CD19FB.A0F81130
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=ISO-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19170">
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff text=#000000>
<DIV><FONT size=2 face=Arial>Hi Aaron.</FONT></DIV>
<DIV><FONT size=2 face=Arial>Thanks again and I will continue experimenting with
it today.</FONT></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">My old Script (App) defined (Registered) a Hot
Key that worked and I think accessed a Window Object's Properties and
Events.</DIV>
<DIV style="FONT: 10pt arial">If these work that will demo:</DIV>
<DIV style="FONT: 10pt arial">Use of MSAA;</DIV>
<DIV style="FONT: 10pt arial">Use of a Window Object;</DIV>
<DIV style="FONT: 10pt arial">Use of a Hot Key.</DIV>
<DIV style="FONT: 10pt arial">That should make for a pretty decent intro demo
and tutorial to post up someplace.</DIV>
<DIV style="FONT: 10pt arial">I will likely continue with a second Demo and
Tutorial with a few more features after this one.</DIV>
<DIV style="FONT: 10pt arial">So far so good.</DIV>
<DIV style="FONT: 10pt arial">Rick USA</DIV>
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=aaron@gwmicro.com href="mailto:aaron@gwmicro.com">Aaron Smith</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=gw-scripting@gwmicro.com
href="mailto:gw-scripting@gwmicro.com">gw-scripting@gwmicro.com</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Friday, April 13, 2012 8:35
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: WE And Microsoft Development
Environments</DIV>
<DIV><BR></DIV>On 4/13/2012 5:19 PM, RicksPlace wrote:
<BLOCKQUOTE cite=mid:E672EAE2E46A4EFF93D32CCC6D96A3A7@RTCOMP01 type="cite">
<META name=GENERATOR content="MSHTML 8.00.6001.19170"><FONT size=2
face=Arial>It still needs some testing and the Form1 grabs focus sometimes
even though hidden.</FONT><BR></BLOCKQUOTE><BR>You can keep the form from
displaying by creating a Main() routine, and putting your startup logic
there:<BR><BR><SPAN id=ctl00_MTCS_main_ctl03><PRE id=ctl00_MTCS_main_ctl03_code class=libCScode space="preserve">Sub Main()
' Instantiate your form
Dim myForm as Form1 = New Form1()

' Put initialization stuff here instead of in Form_OnLoad

' Continue on without displaying the form
Application.Run()
End Sub</PRE></SPAN>If you then ever need to show the form, you can do
myForm.Show()<BR><BR>You can do this in C#, too, by changing code in the
Main() function in Program.cs from:<BR><BR>&nbsp;&nbsp;&nbsp;
Application.Run(new Form1());<BR><BR>to<BR><BR>&nbsp;&nbsp;&nbsp; Form myForm
= new Form1();<BR>&nbsp;&nbsp;&nbsp; Application.Run();<BR><BR>Aaron<BR><PRE class=moz-signature cols="72">--
Aaron Smith
Web Development * App Development * Product Support Specialist
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * 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.</PRE></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0014_01CD19FB.A0F81130--