Since I was one of the people that discussed, back in 2009, the idea of automatically switching power schemes for certain programs, i.e. the anti-sleep/High Performance/Gaming Mode features, I thought it was time I actually tried it, with my newly updated lasso 3.84 installation...
I use a Lenovo Thinkpad notebook w/Windows 7 x86. Lenovo has its own UI to the Windows 7 power scheme infrastructure, a bit nicer and more complete than the Windows default, but the power scheme UIs are completely coordinated, so that things can be changed using either programs(s): new or changed power schemes defined in one are adjustable in the other, and the settings for each scheme are specified separately for battery and for mains power use.
Using the command-line powerfg.exe tool, this is the list of my current power schemes:
powercfg.exe -LIST:
Existing Power Schemes (* Active)
-----------------------------------
Power Scheme GUID: 0209ab81-db53-41d8-93f6-c58ad4d1c8e2 (Timers Off (Screen Off
))
Power Scheme GUID: 03164b9c-9ce5-45af-aab2-95d5f6dac850 (Maximum Performance)
Power Scheme GUID: 1019336e-8043-4773-a667-495b611fa1a0 (Video Playback)
Power Scheme GUID: 381b4222-f694-41f0-9685-ff5bb260df2e (Balanced)
Power Scheme GUID: 52853127-4e7d-4d08-b3ff-4d1b0a2ea218 (Maximum Battery Life)
Power Scheme GUID: 542e37df-1e59-4eb2-9b88-17fdfbc30e79 (Power Source Optimized
)
Power Scheme GUID: 56f5379d-bf83-434f-aa78-3465ffe2ef16 (Energy Star) *
Power Scheme GUID: 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c (High performance)
Power Scheme GUID: a1841308-3541-4fab-bc81-f71556f20b4a (Power saver)
Power Scheme GUID: ab21624c-83e6-4daf-b02b-75836c9302a1 (Timers off (Presentati
on))
Power Scheme GUID: dc3d28ca-1084-412c-a160-ae0ec9e136a8 (Intervideo WinDVD)
And these are some of the various features that can be configured for each power scheme: (powercfg.exe -ALIASES)
a1841308-3541-4fab-bc81-f71556f20b4a SCHEME_MAX
8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c SCHEME_MIN
381b4222-f694-41f0-9685-ff5bb260df2e SCHEME_BALANCED
fea3413e-7e05-4911-9a71-700331f1c294 SUB_NONE
238c9fa8-0aad-41ed-83f4-97be242c8f20 SUB_SLEEP
29f6c1db-86da-48c5-9fdb-f2b67b1f44da STANDBYIDLE
9d7815a6-7ee4-497e-8888-515a05f02364 HIBERNATEIDLE
94ac6d29-73ce-41a6-809f-6363ba21b47e HYBRIDSLEEP
d4c1d4c8-d5cc-43d3-b83e-fc51215cb04d REMOTEFILESLEEP
7516b95f-f776-4464-8c53-06167f40cc99 SUB_VIDEO
3c0bc021-c8a8-4e07-a973-6b14cbcb2b7e VIDEOIDLE
90959d22-d6a1-49b9-af93-bce885ad335b VIDEOADAPT
17aaa29b-8b43-4b94-aafe-35f64daaf1ee VIDEODIM
aded5e82-b909-4619-9949-f5d71dac0bcb VIDEONORMALLEVEL
f1fbfde2-a960-4165-9f88-50667911ce96 VIDEODIMLEVEL
0012ee47-9041-4b5d-9b77-535fba8b1442 SUB_DISK
6738e2c4-e8a5-4a42-b16a-e040e769756e DISKIDLE
4f971e89-eebd-4455-a8de-9e59040e7347 SUB_BUTTONS
7648efa3-dd9c-4e3e-b566-50f929386280 PBUTTONACTION
96996bc0-ad50-47ec-923b-6f41874dd9eb SBUTTONACTION
5ca83367-6e45-459f-a27b-476b1d01c936 LIDACTION
a7066653-8d6c-40a8-910e-a1f54b84c7e5 UIBUTTON_ACTION
e73a048d-bf27-4f12-9731-8b2076e8891f SUB_BATTERY
637ea02f-bbcb-4015-8e2c-a1c7b9c0b546 BATACTIONCRIT
9a66d8d7-4ff7-4ef9-b5a2-5a326ca2a469 BATLEVELCRIT
d8742dcb-3e6a-4b3c-b3fe-374623cdcf06 BATACTIONLOW
8183ba9a-e910-48da-8769-14ae6dc1170a BATLEVELLOW
54533251-82be-4824-96c1-47b60b740d00 SUB_PROCESSOR
bc5038f7-23e0-4960-96da-33abaf5935ec PROCTHROTTLEMAX
893dee8e-2bef-41e0-89c6-b55d0929964c PROCTHROTTLEMIN
0e796bdb-100d-47d6-a2d5-f7d2daa51f51 CONSOLELOCK
501a4d13-42af-4429-9fd1-a8218c268e20 SUB_PCIEXPRESS
ee12f906-d277-404b-b6da-e5fa1a576df5 ASPM
(Some of these may not have any kind of UI.)
I pretty much only use "Energy Star", "Maximum Battery Life", and "Presentation (Timers Off)", which I've customized to do the "right thing" when on AC or DC depending on their intent. Simple.
Some observations on how Lasso 3.84 deals with this:
1) When the Process Lasso UI is started (I never autostart the UI, just the Process Governor), the Main menu enumeration of power schemes does not show the tick against the current active power scheme:

2) When I configure wmplayer.exe to be an "anti-sleep" process, Lasso changes the power scheme first, then presents the dialog to configure the anti-sleep processes. However, it chose the "Power Source Optimized" power scheme:

This scheme by default does have various system idle timers activated for both AC and DC use (at least on the Lenovo), so it's not a good choice for "anti-sleep" (how does it make this choice anyway?). So here is my recommendation on this point: either a) add a new panel to the initial configuration Lasso wizard which allows the user to choose which power scheme is deemed the "anti-sleep" one (you could add a considerable amount of intelligence to the panel by using the Windows power APIs to enumerate the idle timers for each scheme and alerting the user when a chosen "anti-sleep" scheme defines idle time-outs) or b) when Lasso is installed, define a custom power scheme--name it something obvious like "Process Lasso Anti-sleep"--with idle timers disabled (just make sure the user can still change the power scheme defaults via the right user permissions on the scheme) and use that for the anti-sleep scheme (and uninstall it when Lasso is uninstalled).
3) When I tried configuring the High Performance process list, Lasso changed the power scheme to "Maximum Battery Life" before presenting the executable choice dialog:

which is completely *not* high performance. Again, I'm not sure how it chooses this scheme, and I think I would prefer one of the alternative choice mechanisms I discussed in (2) above.
4) The tick mark on the "Active Power Scheme" sub-menu can have toggle-like behaviour in conjunction with other programs setting power schemes: let's say I've selected "Balanced" from the sub-menu, which is not one of the Microsoft-provided power schemes enumerated in the Lenovo power manager UI. When I change to a scheme which is enumerated in both applications, say "Maximum Battery Life", via the Lenovo Power manager UI, then Lasso removes the tick mark from the former scheme, but does not detect the new scheme:

5) However, when I change the power scheme a second time in the Lenovo application, it does put the sub-menu tick mark on the right scheme. Then, if I change the scheme right away via the Lasso sub-menu, say from "Presentations" to "Energy Star", then Lasso fails to remove the tick mark from the former power scheme and adds a second, correct tick-mark to the new scheme:

Now, it is philosophically possible that I live in "parallel worlds" (well, it might be a theory among certain nerds who spend their Sunday afternoons testing software...), but this kind of thing will confuse most people. It's probably best solved by having a thread that continually monitors changes in the Windows power scheme state (something in the registry, perhaps?) and call back into the Lasso UI to make the appropriate changes. Such an arrangement will track power scheme changes, no matter what the source.
Finally, when I once more change the power scheme via the Lasso sub-menu, *both* tick marks are removed, as in (4) above, it requires another activation of the same (or different) sub-menu item to display the proper tick mark once more.
Anyway, all these power scheme changing features will be very welcome, once they work. (Maybe they work for others, but not for me right now.)
As always, I'm impressed with the quality of the software: everything else seems to work as advertised (quickly tested, of course).