Hi Bruce,

I'm not following what you mean by local versus online "accounts."
On my Windows 7 machine, I've had difficulty re-installing WE, where I had
to start over because when I got to the version I wanted by continually
upgrading using upgrade packages, the final one turned out to be a demo even
though I was running retail WE.
I learned you can't jump steps.
Starting over and running through all the incremental upgrades did the
trick.

Thanks,

Rod

-----Original Message-----
From: Scripting
[mailto:[email protected]] On
Behalf Of LB via Scripting
Sent: Monday, April 13, 2015 4:59 PM
To: Rick Thomas; Window-Eyes Scripting List
Subject: Installing WE 8.X On Windows 8


Has anyone had problems installing Windoweyes 8.X on a windows 8 computer?
    Local account is OK, but not the on-line account, partial install of
Windoweyes on that account.

        Bruce

----- Original Message -----
From: "Rick Thomas via Scripting" <[email protected]>
To: "'Chip Orange'" <[email protected]>; "'Window-Eyes Scripting List'" 
<[email protected]>; "'Jonathan C Cohn'" 
<[email protected]>
Sent: Monday, April 06, 2015 7:33 AM
Subject: RE: New Window-Eyes C# Example Now Available


> Hi Jonathin:
> Chip has covered it pretty well if you mean comparing some .net language
> like vb.net or c# to VbScript.
> There are allot more powerful features he has not touched on but for the
> most part he is spot on when it comes to creating scripts for WindowEyes.
> As for properties and methods it is actually a snap using the Properties
> Window.
> You might just bring up the default Form1.vb file in forms designer by
> hitting enter on it.
> Then hit f4 and the Properties Window comes up which is a dialog.
> There is a list of properties for the Form like Name, BackgroundColor,
> ForgroundColor, Size and the like you can arrow up and down having the
> default values read to you.
> To change the name arrow to the Name property tab and type the new name in
> the text box.
> To set the form size arrow to the size property and enter something like
> 1024, 768.
> Now close  the property Window, close the designer and hit f5 to run the
> project and your new form is displayed.
> The Properties Dialog works for all controls from the Form object to any
> objects you might drop on it like Buttons, TextBoxes or ListBoxes and so 
> on.
> When you select one of these controls from either inside the designer or
> from the list of available controls for a form, also in the designer and 
> you
> find it by tabbing to it, the appropriate properties for that control are
> displayed in the table of properties and you can set them as mentioned 
> above
> so you don't have to worry about memorizing properties and the same for
> event handlers...
> You  simply pick a control as above, still in the Properties Dialog and 
> tab
> to the list of events available for that control, hit enter on the event 
> you
> want and the event handlers are setup for you automatically and you can 
> type
> your code into these handlers.
> Now there are other steps but it is really just about that simple.
> Setting and wiring up Properties and Event Handlers is a snap and takes 
> only
> a few seconds.
> I can create a new vb.net Windows project, drop a button on a form, set a
> few properties, add an event handler, test the button click event and save
> the new project in 2 minutes or less.
> So actually setting properties and wiring up event handlers is a very, 
> very
> fast thing to do so long as they are .net objects.
> Working with the WindowEyes Object Model is diferent since it is a non 
> .net
> Platform object and must be accessed using COM Interop.
> I think if you have to ask you likely would be better off sticking with
> something like vbScript or trying to find help learning Pytho which may be

> a
> really nice choice for external WindowEyes scripts.
>
> Rick USA
>
>
> _______________________________________________
> Any views or opinions presented in this email are solely those of the 
> author and do not necessarily represent those of Ai Squared.
>
> For membership options, visit 
>
http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/lab4me%40
fltg.net.
> For subscription options, visit 
> http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com
> List archives can be found at 
> http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com 


---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com

_______________________________________________
Any views or opinions presented in this email are solely those of the author
and do not necessarily represent those of Ai Squared.

For membership options, visit
http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/rod_hutto
n%40hotmail.com.
For subscription options, visit
http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com
List archives can be found at
http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com

_______________________________________________
Any views or opinions presented in this email are solely those of the author 
and do not necessarily represent those of Ai Squared.

For membership options, visit 
http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/archive%40mail-archive.com.
For subscription options, visit 
http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com
List archives can be found at 
http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com

Reply via email to