Utility to change behavior of ATX power button (e.g.: launch an app)

**frodobaggins** · 08-17-2005, 02:01 AM

I'll finish this up in the morning, it is working quite well.

**justintime** · 08-17-2005, 07:24 AM

Frodo:

Are you seriously coding this thing? (I'm stoked!)
If so, are you able to completely CANCEL the triggering event? That is the crucial part.

Shutdown I believe power soff completely. Restart on the other hand, will reboot (power back up) right after shutting down.

Actually, in Windows looks like these are called: Turn Off, and Restart. I can see both options when I do start->turn off computer.

**frodobaggins** · 08-17-2005, 03:11 PM

Yes, I am coding this. Yes it will CANCEL the event.

Even though you can choose restart/shutdown, programs
don't know the difference. Same with standby/hibernate.

Now, if someone sends the "force" command along with a shutdown
etc command, the app won't cancel that event, as it's not possible,
but in 99% of the cases the way windows is shutdown, that won't happen.

**justintime** · 08-17-2005, 03:25 PM

Originally Posted by frodobaggins

Yes, I am coding this. Yes it will CANCEL the event..

THANK YOU!

Originally Posted by frodobaggins

Even though you can choose restart/shutdown, programs
don't know the difference. Same with standby/hibernate.
..

Not sure why this is relevant. What 'Program' needs to know the difference, aside from the interceptor utility itself?

Originally Posted by frodobaggins

Now, if someone sends the "force" command along with a shutdown
etc command, the app won't cancel that event, as it's not possible,
but in 99% of the cases the way windows is shutdown, that won't happen.

I think if I understand correctly, we don't have a problem here. The 'shutdown' sequence that would be generated is typically going to be sent by the Opus, which is in fact the same as pressing the Shutdown button on a PC case.
I can see how someone could attempt a forced shutdown via the DOS command 'shutdown -f' but that would never occur via the Opus.

Let me know when you have something to test, I will spend time with it!

**frodobaggins** · 08-17-2005, 03:29 PM

Originally Posted by justintime

Not sure why this is relevant. What 'Program' needs to know the difference, aside from the interceptor utility itself?
!

The interceptor is a program too !

So you only have 3 events.

1. Shutdown/Restart
2. Log Off
3. Hibernate/Standby

**justintime** · 08-17-2005, 04:07 PM

That's what I thought you were refering to.
Quite honestly, I only really will ever need to intercept the hibernate event, so that's cool by me!

How hard would it be to add some code in there to launch apps/scripts also upon RESUMING from the events? Kind of like a whole other tab in the interface, with same configuration items, but relevant to the resume of the 'events'.
So for example, would be great to be able to run a script when I RESUME from a hibernation.

Originally Posted by frodobaggins

The interceptor is a program too !

So you only have 3 events.

1. Shutdown/Restart
2. Log Off
3. Hibernate/Standby

**frodobaggins** · 08-17-2005, 06:46 PM

Originally Posted by justintime

How hard would it be to add some code in there to launch apps/scripts also upon RESUMING from the events? Kind of like a whole other tab in the interface, with same configuration items, but relevant to the resume of the 'events'.
So for example, would be great to be able to run a script when I RESUME from a hibernation.

That's not a problem, however, say you catch the hibernate/standby event, and cancel it. When you cancel it, windows thinks it has resumed, so the resume event fires as well. So you will have to choose one or the other.

**justintime** · 08-17-2005, 06:50 PM

How about something more creative, like putting a timer/delay to launch those apps or scripts (instead of trying to detect the resume from hibernate event)
So, you would for example launch an app with a 10 second delay. This would be enough time for the hibernation to take place. Let's say, 2 seconds passed by, and now the pc is hibernated. When you resume from hibernate, another 8 seconds will pass, and the app/script would be launched.

I know, it's a workaround, but hey, need to think out of the box

Originally Posted by frodobaggins

That's not a problem, however, say you catch the hibernate/standby event, and cancel it. When you cancel it, windows thinks it has resumed, so the resume event fires as well. So you will have to choose one or the other.

**frodobaggins** · 08-17-2005, 06:57 PM

I'll just have it skip the first resume message.
Then it will only fire on the real resume.

**justintime** · 08-17-2005, 07:24 PM

Another alternative.

How about you find a way to differentiate between the 'normal' resumes from hibernate, and the ones you canceled via interceptor?

For example, before canceling the event with interceptor, write a 'True' to a variable.

After detecting a resume from hibernate, read the variable, if True then you do no launching, and set the variable to false. If it is false, then you launch the apps...

Originally Posted by frodobaggins

That's not a problem, however, say you catch the hibernate/standby event, and cancel it. When you cancel it, windows thinks it has resumed, so the resume event fires as well. So you will have to choose one or the other.