* On the welcome screen, make it much more clear if the version is
already installed. If it's not installed, give a tiny summary of what
RenderDoc actually is.
* This seems way more reliable and smaller than shipping a compiled .dll
* For some reason I didn't find this method before (I only knew that
you could ship the loose files which wasn't a good solution).
* I doubt anyone will notice the file->open filter unless they look for
it so it's no good for 'discovering' the image viewing capability, but
it might be convenient for people who know about it.
* This allows you to hook into processes that are difficult to launch
directly with the existing functionality in RenderDoc.
* This is rather risky, as it modifies the AppInit_DLLs registry key to
inject a small shim dll that checks for the desired process and injects
the full renderdoc.dll. If that registry key got left, or if there was
some incompatibility with the shim dll, you could have problems. It
should only ever be used as a last resort if there's no other way to
capture.
* This might be the wrong thing to do, I've changed my mind on this a dozen
times. I think most people will want these, and I don't think it's a bad
thing to include it as the default setting - people can still go to
customise and unselect it. I thought most people would do custom and then
opt-in since most will want it, but I suspect (from watching people run
the installer) that most people hit typical, and so don't get these.
baldurk