Re: Windows - window status (Running vs Not Responding)

2008-04-12 Thread rdahlstrom
On Apr 11, 11:18 pm, Ross Ridge <[EMAIL PROTECTED]> wrote: > rdahlstrom <[EMAIL PROTECTED]> wrote: > >Basically, I'm looking for something similar to the Process.Responding > >property in System.Diagnostics... > > You probably want to use IsHungAppWindow(): > > IsHungAppWindow Function > >

Re: Windows - window status (Running vs Not Responding)

2008-04-11 Thread Tim Golden
Ross Ridge wrote: > rdahlstrom <[EMAIL PROTECTED]> wrote: >> Basically, I'm looking for something similar to the Process.Responding >> property in System.Diagnostics... > > You probably want to use IsHungAppWindow(): Brilliant! So simple when you find out. Thanks. (Added to my list of things I

Re: Windows - window status (Running vs Not Responding)

2008-04-11 Thread Ross Ridge
rdahlstrom <[EMAIL PROTECTED]> wrote: >Basically, I'm looking for something similar to the Process.Responding >property in System.Diagnostics... You probably want to use IsHungAppWindow(): IsHungAppWindow Function You call the IsHungAppWindow function to determine if Mic

Re: Windows - window status (Running vs Not Responding)

2008-04-11 Thread Mike Driscoll
On Apr 11, 3:22 pm, Tim Golden <[EMAIL PROTECTED]> wrote: > Mike Driscoll wrote: > >http://www.informit.com/articles/article.aspx?p=19489&seqNum=4 > > > If you're better than I am, you can probably translate this to the > > Python equivalent. Zenoss also has some monitoring software that's > > open

Re: Windows - window status (Running vs Not Responding)

2008-04-11 Thread Roger Dahlstrom
On Apr 11, 3:46 pm, Tim Golden <[EMAIL PROTECTED]> wrote: > rdahlstrom wrote: > > On Apr 11, 1:45 pm, rdahlstrom <[EMAIL PROTECTED]> wrote: > >> Does anyone know how to determine the window status (Running or Not > >> Responding)? I've tried various methods with no success... > > >> This would be

Re: Windows - window status (Running vs Not Responding)

2008-04-11 Thread Roger Dahlstrom
On Apr 11, 3:54 pm, Mike Driscoll <[EMAIL PROTECTED]> wrote: > On Apr 11, 2:10 pm, rdahlstrom <[EMAIL PROTECTED]> wrote: > > > On Apr 11, 1:45 pm, rdahlstrom <[EMAIL PROTECTED]> wrote: > > > > Does anyone know how to determine the window status (Running or Not > > > Responding)? I've tried various

Re: Windows - window status (Running vs Not Responding)

2008-04-11 Thread Roger Dahlstrom
On Apr 11, 3:46 pm, Tim Golden <[EMAIL PROTECTED]> wrote: > rdahlstrom wrote: > > On Apr 11, 1:45 pm, rdahlstrom <[EMAIL PROTECTED]> wrote: > >> Does anyone know how to determine the window status (Running or Not > >> Responding)? I've tried various methods with no success... > > >> This would be

Re: Windows - window status (Running vs Not Responding)

2008-04-11 Thread Tim Golden
Mike Driscoll wrote: > http://www.informit.com/articles/article.aspx?p=19489&seqNum=4 > > If you're better than I am, you can probably translate this to the > Python equivalent. Zenoss also has some monitoring software that's > open source Python code. I'm afraid that article only allows you to d

Re: Windows - window status (Running vs Not Responding)

2008-04-11 Thread Mike Driscoll
On Apr 11, 2:10 pm, rdahlstrom <[EMAIL PROTECTED]> wrote: > On Apr 11, 1:45 pm, rdahlstrom <[EMAIL PROTECTED]> wrote: > > > Does anyone know how to determine the window status (Running or Not > > Responding)? I've tried various methods with no success... > > > This would be on a variety of Windows

Re: Windows - window status (Running vs Not Responding)

2008-04-11 Thread Tim Golden
rdahlstrom wrote: > On Apr 11, 1:45 pm, rdahlstrom <[EMAIL PROTECTED]> wrote: >> Does anyone know how to determine the window status (Running or Not >> Responding)? I've tried various methods with no success... >> >> This would be on a variety of Windows systems, but all at least XP, >> and mostly

Re: Windows - window status (Running vs Not Responding)

2008-04-11 Thread rdahlstrom
On Apr 11, 1:45 pm, rdahlstrom <[EMAIL PROTECTED]> wrote: > Does anyone know how to determine the window status (Running or Not > Responding)? I've tried various methods with no success... > > This would be on a variety of Windows systems, but all at least XP, > and mostly server 2003. Everyone w