This might be a nice feature... but I think it will cause LCDStudio to use quite a bit of resources itself. In order to find the most expensive process I'd have to query every process and sort (descending order)... every second. I guess even Task Manager does this. I'll try it and let you know what happens.Secondly, a built-in kill would seem to suggest you're using a G15. I also use one, but this would be a bit useless to most users who aren't using one. I could just make it a hot key you can set in the options. Ooo! That would give me a reason to make an options screen!

...acronym: AMD Anyhow, I guess the possibilities are limitless. However, I'd suggest you don't turn this plug-in into an LCD-based Task Manager. Displaying information would be welcome, like selecting a process and displaying CPU usage or memory utilisation, but that's as far as I would take it.Notice that Task Manager consumes quite some resources itself, too.And you're quite right about G15 and the rest of us. Really, we don't want to turn our LCDs into tiny menu-displaying units...

No, I don't have to use every feature, but it might make an interesting plug-in too resource-heavy to use.If Dan should want to make a separate full-blown Task Manager plug-in, he can be my guest. As long as he makes sure not to overload the basic AppMonitorDlx with such a functionality.Other than that, any new plug-in is welcome.

I think he could just add some "CheckBox"es to the property page he were thinking about, so that if someone doesn't want the heavy stuff the plugin won't neither calculate them nor expose them to LcdStudio

I hope I were clear (I'm sleepy, the English-able part of my brain may not be functioning properly)

Wouldn't it be just simpler to make two plug-ins? That way, the heavy version one wouldn't even be loaded by LCDstudio. That way we could even have a smaller memory footprint for people that wouldn't need it.Oh, and don't worry about your English. We got the message!

means that those variables would just be ignored by an IF statement (probably) which would only result in a larger DLL not the memory footprint when not actived. (At least I know so, if not my apologies) This way it would be much easier to update the core stuff (updating one class library instead of two).

the power of admining. But i actually do agree a little with you aswell spock. If the checkboxes doesnt make the plugin skip the whole deal, if you know what i mean, i think you should make another separate task manager plugin.

Children! heheWell, I have to say that while those are good arguments, I do still agree with spock. I would rather make a separate plugin that would function as a task manager type program. The original intention of this plugin was only to give the current process name so that I could add screen to the playlist depending on which program was currently in the foreground. It's gone a little beyond that, but I don't want to lose sight of the original intention.Anyway, it's the day after Thanksgiving here and I've got pretty much nothing to do today. So after I play World Of Warcraft (how I wish it wasn't against the EULA to make a plugin for that game...) for awhile, I'll see where I can get with the task managing idea

Oh! gotta love ya for that. Well, my original statement that it would be in just one plugin was mostly based on the fact that i thought you would rather have it that way, since it seems to me that it is much more work to do two plugins than one. But if you have the time, why not? i can sureley come upp with another dozen or so things you can do plugins for, if you have the time