Strategies to keep replacing a .NET .NET table after a long period of non-use?

Question

I am working on a simple alt-tab replacement program. It is implemented in C # as a hidden WPF window that is brought to the forefront using the global keyboard hotkey.

For the most part, this works fine, and the application window appears immediately after pressing the hotkey. However, if a lot of time has passed since the user activated the window, it can slowly “rotate” and display 3-5 seconds. I guess this has something to do with Windows paging application memory to disk.

Are there any good strategies to keep the app responsive after long periods of inactivity?

(Since it is open source, you can see the full full code if that helps.)

Answer 1

Why don't you just use a timer in your code that fires once a minute, and execute some code in this tick timer handler. This should support an active process.