Hi all,
The ClientInformation.Overlap seems to grab what ever process launched an application even if the ClientInformation.Overlap is deep within a Function or Sub routine. On the two occasions I have fallen fowl of this, one in the Goldwave script, and the second in Replay Media Capture I have caught the splash screen by associating my test overlap script as a specific application script and both splash screens have had no children and a completely obscure name which sounds nothing like the applications I was working on, something like: "windows form 10" followed by letters and numbers. Sometimes you are better writing your own test routines as I too find thins like the treeview app gives far too much information, but that's just my view and I don't expect everybody to agree.
Regards.
Martin Webster.
I.T. Director for Kirklees Visual Impairment Network.

On 23/03/2015 14:04, Rick Thomas via Scripting wrote:
HiAaron and Chip:
Aaron: Got things working up to a point in the script.
I have a plan to set a boolean when the ErrorList is selected from the
MenuItem, otherwise block the events that focus etc the errorlist window.
Chip:
I may have missed something but here are my Text Editor settings for the
Visual Basic Text Editer:
Where did you find that item but in the Visual Basic Editor I have the
following relevant settings:
Menu Bar>Tools>Options>TextEditor>All Languages>Basic>
General>
Autolist Members Unchecked
Parameter Information Unchecked
Enable Virtual Space Unchecked

VB Specific
Pretty Listing  (Reformatting of code) Unchecked
Enable Outlining Mode Unchecked
Enable Error Corrections Unchecked
Where did you find the item you set to avoid the issue of the ErrorList
poping up all the time and are you running Windows 8.1 and WE 9.1?
I did not have the problem in WE 8.4 and perhaps it may not occur in Windows
7.
Rick USA

-----Original Message-----
From: Scripting
[mailto:[email protected]] On
Behalf Of Aaron Smith via Scripting
Sent: Monday, March 23, 2015 9:00 AM
To: Chip Orange; Window-Eyes Scripting List; 'LBX'
Subject: RE: Visual Studio Project: Desktop, Overlap and Accessible Object

ClientInformation.Overlap for Visual Studio is most likely going to be the
splash screen that comes up when you launch it. You'd need to set up a
routine that would go looking for the window you really want, and when you
find it, set  ClientInformation.Overlap to it (this is the number one reason
why ClientInformation.Overlap is read/write).

Aaron

--
Aaron Smith
Web Development * App Development * Product Support Specialist Ai Squared *
725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * www.aisquared.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 Ai Squared Technical
Support Team.

-----Original Message-----
From: Scripting [mailto:scripting-
[email protected]] On Behalf Of Chip
Orange via Scripting
Sent: Monday, March 23, 2015 7:31 AM
To: 'LBX'; 'Window-Eyes Scripting List'
Subject: RE: Visual Studio Project: Desktop, Overlap and Accessible
Object

You know, when I setup my VS 2013, even though I don't really know it,
I found a configuration option where I could disable this window (I'm
pretty sure), and that's why when I was trying it out, I wasn't seeing
the problems Rick was.

I actually mentioned to Rick that it did much better without the
VS2008 app running, but this is probably because I disabled this
window for dynamic hints etc.

Chip


-----Original Message-----
From: LBX [mailto:[email protected]]
Sent: Sunday, March 22, 2015 1:20 PM
To: Chip Orange; Window-Eyes Scripting List
Subject: Re: Visual Studio Project: Desktop, Overlap and Accessible
Object

Hi Rick,

     Yes, I think you are seeing what always happens in the studio
messaging.
Remember that there is always that dynamic screen that displays
everything for a sighted user.

     You get errors, hints and all that stuff that gets placed in the
appropriate column on the screen.
     Yes, Windoweyes seems to pick up things all the time a sighted
user never sees. I have had a sighted friend over on many occasions to
fix things and Windoweyes is saying stuff that is not even on the screen.
     As I had mentioned to you privately, MSAA some times does not
work, but as Chip has said, filtering out that move to that screen
only, or others in the future, will at least quiet down the screen.
     Hmmm, this sounds like a good app update for the studio, keep on
plugging away on it.

         Bruce

Sent: Sunday, March 22, 2015 12:24 PM
Subject: RE: Visual Studio Project: Desktop, Overlap and Accessible
Object


Before messing with msaa Rick, since it's the Error window you are
concerned with at the moment, leave your logger as it is, and do
something which causes the error window to steal focus as it's been
doing, and then log the info for the .over of the error window.

Also, this will tell you if the error window really is getting focus like
you think.
If it is, what you will ultimately want to do is to start learning
about filtering MSAA events, so that you can filter this constant
change of focus (if that's what is happening), so window-eyes doesn't
see it, and then next, you'll need to allow your apps msaa events to
still see the focus change to the error window so that you can correct
it (put the focus back to where it belongs).

I'm not really convinced focus is staying on the error window, since a
sighted person could not keep typing into their code if the focus kept
moving away from the code window, so you probably won't need to
correct it; but it could be popping over there for a quick
millisecond, in which case, you would just want to stop window-eyes from
noticing that.
Hth,

Chip


-----Original Message-----
From: Scripting
[mailto:[email protected]]
On Behalf Of Rick Thomas via Scripting
Sent: Sunday, March 22, 2015 7:12 AM
To: 'Window-Eyes Scripting List'
Subject: Visual Studio Project: Desktop, Overlap and Accessible Object

Hi: Connecting to the Desktop did get things at least firing.

The Overlap Window OnChildFocus first hits the Desktop, then the
Visual Studio Start Page and again the Desktop.

I pull a a Accessible object when the Visual Studio window is the
overlap for future analysis.

Now I will see if MSAA offers me anything using the Accessible Object?
Does that sound right?

Here is the output for the 3 OnChildFocus events and below it my code:

Now I could use some comments on what to try next to ensure things are
working...



This has 2 sections so you can jump to a heading by find on "Section:

It is really quite short but thought I would set up in case gets
longer in the future.



Section: Logger Output

Desktop OnChildFocus fired

OverlapWindow Properties:

Title: desk top

Name: Program Manager

ModuleName: SHELL32

ClassName: Progman

IsValid: True

Status: 2

Visible: True

overlapWindow Was not set to overlapObj

Desktop OnChildFocus fired

OverlapWindow Properties:

Title: Start Page - Microsoft Visual Studio

Name: Error List - Microsoft Visual S

ModuleName: DEVENV

ClassName: HwndWrapper[DefaultDomain;;b2b0d600-6857-4bfe-8b10-
1dfaf378

IsValid: True

Status: 1

Visible: True

accOverlap Accessible is set for overlapObj

Desktop OnChildFocus fired

OverlapWindow Properties:

Title: desk top

Name: Program Manager

ModuleName: SHELL32

ClassName: Progman

IsValid: True

Status: 2

Visible: True

overlapWindow Was not set to overlapObj



Section: AppCode

' VS2013

Option Explicit

Dim logFSO: Set logFSO = CreateObject("Scripting.FileSystemObject")

Dim myMSAAEventSource : Set myMSAAEventSource = MSAAEventSource

myMSAAEventSource.Process = ClientInformation.ApplicationProcess

Dim accOverlap



Dim Desktop

Set Desktop = ClientInformation.Application.DesktopWindow

ConnectEvent Desktop, "OnChildFocus", "OnChildFocus"

Sub OnChildFocus( wObj)

Logger( "Desktop OnChildFocus fired")

Dim overlapObj

Set overlapObj = wObj.Overlap

Logger( "OverlapWindow Properties:")

Logger( "Title: " & overlapObj.Title)

Logger( "Name: " & overlapObj.Name)

Logger( "ModuleName: " & overlapObj.ModuleName)

Logger( "ClassName: " & overlapObj.ClassName)

Logger( "IsValid: " & overlapObj.IsValid)

Logger( "Status: " & overlapObj.Status)

Logger( "Visible: " & overlapObj.Visible)

If (overlapObj.IsValid) And _

(overlapObj.ModuleName = "DEVENV") Then

Set accOverlap = overlapObj.Accessible

Logger( "accOverlap Accessible is set for overlapObj")

Else

Logger( "overlapWindow Was not set to overlapObj")

End If

End Sub



Sub Logger( LogLine )

Const ForAppend = 8

Dim LogFile: Set LogFile = logFSO.OpenTextFile(
"c:\VSScriptFolder\Logger.txt", ForAppend, True)

LogFile.WriteLine(LogLine )

LogFile.Close

End Sub

' EndOfFile:

-------------- next part -------------- An HTML attachment was
scrubbed...
URL:
<http://lists.window-eyes.com/private.cgi/scripting-window-
eyes.com/attachme
nts/20150322/15b31f66/attachment.htm>
_______________________________________________
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/lists3717
%40comcast.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

_______________________________________________
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/asmith%40aisquared.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/ofbgmail%
40mi.rr.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/webstermartin%40yahoo.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