Conversation
In certain scenarios (alt+tab) the device is lost, this was caught in the old version too Scenarios like voluntary reset (e.g. change of settings) were not covered
|
+1 |
* Add option to skip d3d9 because of performance impact * Fix GAPIProxyGrabber destructor trying to call overriden virtual free() * Fix grabberType changed too often during SettingsWindow setup * Properly cleanup and create D3D10Grabber because stop() does not stop it from injecting Conflicts: Software/src/SettingsWindow.ui
|
Actually, works for me with some extra hooking and compilation fixes. However, when fullscreen app has a resolution that differs from one Prismatik was launched against, hooking doesn't work: |
|
Indeed. I did not change that part, that's what the current master does too. One could add a mechanism to scale the image to the resolution prismatik expects |
|
Actually this is what GrabberBase::reallocate is for: |
|
In theory, whoever originally wrote the D3D10Grabber does not use the screensWithWidgets (and therefore the reallocate mechanism): I do not think the GrabberBase can handle a scenario where the screens returned by screensWithWidgets have a resolution different from the resolution the widgets are specified in. The grab mechanism can handle offsets but not entirely different sizes: https://github.com/woodenshark/Lightpack/blob/master/Software/grab/GrabberBase.cpp#L158 |
3 participants
Not tested on other platforms or with MinGW build
Includes #40