* IronPython >= 2.7.5, if installed, adds a *global* redirect so all
programs (like renderdoc) that tried to reference the 2.7.4 they
provided will instead get redirected to 2.7.5. Whether or not it even
exists.
* We can point the platform plugins path at the application dir for
qwindows.dll for example, but there's no equivalent for image format
plugins which we need for qsvg.dll. So instead we shove them all under
an explicit qtplugins path.
* Also now that we have this, copy qsvg.dll into the distribution.
* Even if we don't have pyside2 to treat qwidgets as full objects and
access their methods and data, we still need to be able to pass around
the QWidget* as an opaque pointer to be able to use the API properly.
* This change falls back to just using SWIG's default opaque pointer
wrapping and unwrapping when pyside2 isn't available.
* Any work that might use Qt needs to happen on the UI thread, so when
running a python script on the python thread we need to invoke across.
We wrap the main ICaptureContext interface to block invoke onto the UI
for any function calls that aren't just returning internal data.
* The error handling code will be OK if a NULL parameter was passed in
but during cleanup it will go through tempdealloc, so we need to check
that the pointer is actually valid.
* QShortcut falls down on duplicates. It can have activatedAmbiguously
events, but these happen in arbitrary order and the shortcuts on
menu items just swallow the ambiguous activate so it's not useful.
* Instead we just let MainWindow pick up ShortcutOverride events and
consult a mapping of which shortcuts to use. We can use a smarter
selection method to choose the more 'local' shortcut if two shortcuts
that conflict exist.
There are a few places where the logical 'and' operator
was used to check if a given flag is enabled however
that is not the correct operator.
The binary 'and' operator should be used where
the enum acts as a flag.
* This really isn't ideal as it means the python module will only work
with that specific major.minor version of python, when it could in
theory work with any python version above 3.2 or so, depending on what
features are used.
* Since we're not distributing these modules yet though, add this
linking to support -Wl,--no-undefined.
* glGetQueryObjecti64vEXT was used twice as an alias.
* Added missing glIsQueryEXT alias.
* Removed the query related methods from the unhandled block.
* This fixes a bug with replay proxies where looking at the last bound
buffer type lead to buffers being created with insufficient flags on
the local replay.
* It will also handle the case where a buffer is used as e.g. both
vertex and index and needs to have the flags for both specified.
* This is a grey area between valid and invalid. Technically we're still
passing a valid IDXGIOutput to the functions, but in practice the
function will then probably turn around and cast it to an internal
concrete type which it no longer points to, and explode.
baldurk