Hi Vincent,

I have had the same experience myself where a coding snack no longer works.

I'm afraid that some of the older coding snacks were written before the advent of W7. Changes to the O/S will have broken those particular items. Since many users still employ older systems I assume that those 'snacks' remain for their benefit. You could try posting a request for someone to rewrite this item, always assuming that the functions are still available for manipulation.

Sorry that this one doesn't work for you but at least you now know that it's not an issue for you alone.

There is a lot more free material available that will work for you.  I hope you can have fun with some of that.
 

-cranioscopical (August 26, 2013, 08:44 AM)

You are not saying that anyone else has had this problem with CAPshift, in particular, right?

What is the appropriate forum to place a request for someone to look into this?

Thanks -- Vincent

I think this might be a better forum than I chose at first.

CAPshift doesn't seem to work in Windows 7.  All the stuff in the menu that operates on the selected text does nothing.

Is this well know?

Thanks -- Vincent

My memory is that setting any Force option will keep it from being "tamed", because taming by definition means changing its priority to a lower level.

So normally if one sets a process to "Force Below Normal" you are telling Process Tamer: "don't bother watching this and assigning it a low priority when it hogs the cpu, instead just always keep it below normal priority".

Can you give me an example case of when you'd want it forced to something AND at the same time want PT to watch it and reduce its priority to something else when it starts using too much of the cpu?

-mouser (August 12, 2010, 06:39 PM)

And, also, the original post in this thread defined the bug that this thread is about as (my words):

He used ProcessTamer to force Notepad to Below Normal. Then ProcessTamer lowered its priority due to very heavy usage. Then ProcessTamer raised its priority back to Below Normal when the abnormality cleared up.

And, then the bug, ProcessTamer kept raising the priority forever.

That's why I thought it was established that forcing priority only set a high limit and ProcessTamer would lower it as needed for CPU Smoothing.

Thanks -- Vincent