Hi Aaron. I had conducted the tests, created the documentation and was posting
when I read Ron's message. At the time it didn't hit me that it included a
work-around unless there was another post after that. I'll check it out this
morning as I am working backward through my e-mails right now. I
thanks again for the help.
Rick USA
- Original Message -
*From:* Ron Parker <mailto:r...@gwmicro.com>
*To:* gw-scripting@gwmicro.com <mailto:gw-scripting@gwmicro.com>
*Sent:* Wednesday, April 06, 2011 4:06 PM
*Subject:* Re: External Script MSAAEvent Probl
- Original Message -
From: Ron Parker
To: gw-scripting@gwmicro.com
Sent: Wednesday, April 06, 2011 4:06 PM
Subject: Re: External Script MSAAEvent Problem continued
On 4/6/2011 3:48 PM, RicksPlace wrote:
I will actually run one more test, in that one everything will be the same
On 4/6/2011 3:48 PM, RicksPlace wrote:
I will actually run one more test, in that one everything will be the
same as it now stands without modification except I will make the
Global MyMSAAEventSource variable private to see if that stops the
bleeding of the ConnectEvent from my VBScript into
Hi Doug et al:
The script that does not seem to be working is a VB.net script created in the
VB.net IDE which is almost identical to the Visual Studio IDE but for only
VB.net language applications.
I have not tried any other external languages like java or Python which do not
run under the Micr
It affects all MSAA events, but only for external scripts.
On 4/6/2011 3:13 PM, Doug Lee wrote:
So just to clarify, am I correct in saying that (1) this issue only
affects onFocus, or does it affect all MSAA events? And (2) does it
affect only external scripts, or also hosted VBScripts and
Jav
Hey Rick
Just to be curious, what kind of external application are you writing?
From: RicksPlace [mailto:ofbgm...@mi.rr.com]
Sent: Wednesday, April 06, 2011 12:18 PM
To: gw-scripting@gwmicro.com
Subject: Re: External Script MSAAEvent Problem continued
Thanks Ron. I know you guys
Subject: Re: External Script MSAAEvent Problem continued
We're looking into this. As of right now, we can't rule out the possibility
that a bug has crept into the implementation of WatchEvent. If so, we'll of
course fix it and see what we can do about developing a workaro
So just to clarify, am I correct in saying that (1) this issue only
affects onFocus, or does it affect all MSAA events? And (2) does it
affect only external scripts, or also hosted VBScripts and
Javascripts?
On Wed, Apr 06, 2011 at 03:06:56PM -0400, Ron Parker wrote:
Yep, this is definitely ou
Yep, this is definitely our bug. This worked at one time, but at some
point before the release of WE 7.0, something in the internal
architecture got changed and that method didn't get updated. Which
wouldn't normally be a problem, or at least not a problem anyone would
find out about, but the o
We're looking into this. As of right now, we can't rule out the
possibility that a bug has crept into the implementation of WatchEvent.
If so, we'll of course fix it and see what we can do about developing a
workaround you can use until the fix hits the streets.
On 4/6/2011 11:31 AM, RicksPl
11 matches
Mail list logo
