Well Doug; this is part of the answer. when I use focusedWindow just as you did, having been in outlook before using immed, it worked fine. in the same immed session however, if I used the .filter method to find what should be the same outlook window, and which says it is the same window when you display it's properties, well when I get the process object from this window instead of focusedWindow, blockEvent fails!
it also fails if I use this window's overlap property to get at the process object. I don't know what this means, but this is a lot closer to the answer. Chip -----Original Message----- From: Doug Geoffray [mailto:[email protected]] Sent: Tuesday, November 03, 2009 1:08 PM To: [email protected] Subject: Re: getting error when trying to block msaa event I just used immed along with the FocusedWindow.Process for example. Doug Chip Orange wrote: when you said this worked fine for you Doug, which process were you using to test with? thanks. Chip -----Original Message----- From: Doug Geoffray [mailto:[email protected]] Sent: Monday, November 02, 2009 3:59 PM To: [email protected] Subject: Re: getting error when trying to block msaa event Chip, I know you said you verified your forProcess variable is a process but I would double check. This works fine for me as long as the process is valid. But if the process isn't valid then I get the error you are getting. How did you verify forProcess is a process and what are you setting it to? Doug Chip Orange wrote: Hi all, I guess this is really to GW: I'm getting an "invalid procedure call or argument" when I try to block an msaa event from another process. I have first verified by displaying the name that my variable does hold a valid process. here are the lines I'm using: set x = msaaEventSource x.blockEvent event_SYSTEM_SOUND, forProcess I also get the error if I don't make a copy of msaaEventSource, but try to execute blockEvent from it. does anyone know why this is? I'm trying to work around another WE problem having to do with possibly MSAA output from this process, this is getting silly! thanks. Chip
