Fantastic program, thanks again for the recent fixes. I am loving this thing.
One idea I had for eye candy was to have a close animation similar to the open one, but in reverse when you just close the program without selecting an icon.
Not sure if this is worth doing, because it may slow down the launching of apps or introduce bugs.
But here's a thought on how it could be implemented.
Right now I assume that the apps are launched similar to this
Process p = new Process();
p.StartInfo.WorkingDirectory = sDir;
p.StartInfo.FileName = sFullPathToExeIncludingApp;
if (bHaveArgs)
{
p.StartInfo.Arguments = arguments;
}
p.Start();
But, instead it could be followed with a WaitForExit, such as:
Process p = new Process();
p.StartInfo.WorkingDirectory = "
\\Windows";
p.StartInfo.FileName = "
\\Windows\\Cam1.exe";
if (bHaveArgs)
{
p.StartInfo.Arguments = arguments;
}
p.Start();
p.WaitForExit();
Then follow this with some code to do the animation.
But, that make it so no other app could launch until the last launched was terminated.
So, each time an app was launched, a new thread would first need to be spawed to launch the app.
I have not done much with threading since college so, I did a google on it. Looks pretty easy to spawn a thread.
http://msdn.microsoft.com/en-us/library/7a2f3ay4(v=vs.80).aspx
To avoid the hassles of thread saftey, it could just launch another exe when the app terminates that shows the animation.
-----
In the end, I don't think this is going to look good, since yiou won't have the image of the app at the state just befor termination. You could use the icon image. Or you could just wait a little after launch (There is a WaitForExit that takes a milliseconds parameter) , take a screen capture. Then do the wait for exit. But, doing the screen capture is going to affect perfromance.
But, right now, the app is so snappy and bug free that I would rather not see this, if it affected performance or introduced any bugs.
