* I'd still recommend against using this whenever possible, but there
are cases where it's useful.
* Added sorting by columns, and a new column with the window title.
* Fixed the refresh button being off the edge of the layout.
* Auto-fill as much space as possible with the list of processes.
* Added a find-as-you-type filter, which works by PID, exe name or
window title.
* We make shaders into fake resources with IDs, so they can be
identified individually (for replacement, fetching reflection data,
and things like that). This is a little but ugly but worth it for the
simplicity it will provide everywhere else.
* The sliceFace passed in via the replay interface is still in 0-n range
with n being the top level mip dimension. We just change the drop-down
so that it only lists the number of slices at that mip, and scales up
accordingly.
* This means we only jump to the 'active' mip or slice when switching to
a new draw with some texture on output. This still lets us
automatically follow through a mip generation chain or cubemap
rendering, but when looking at a particular slice or mip on a texture
it doesn't get reset when switching textures around.
* Rather than exclusively always opening at the default directory, it
will only do that until a capture has been successfully saved - then
it will re-use that previous directory. This is only remembered for as
long as RenderDoc is open, thereafter it will revert back to the dir
specified in the options.
* The exact contents depend on the API - on D3D11 this is the bytecode
blob, on Vulkan it's the SPIR-V. On OpenGL it is just a concatenation
of all the source files passed in sequence.
* If there's no replay context we can still use the live connection to
copy and delete captures remotely. Try to use that whenever possible
and warn the user when it's not possible (i.e if the program has been
closed and there's no replay context, we have no way to access the
files anymore).
* If the user tries to open a remote log without a replay context,
prompt them either to swithc to a replay context on that host or to
save the log locally.
* This can happen if the program is closed, and no remote replay context
is active. Unlikely locally, the UI cannot natively save or delete
temporary captures.
baldurk