Handling of depth buffers for stereoscopic systems
Splitting @cabanier's question into a new issue:
How is a single depth buffer going to work with stereo? Will each eye have its own depth buffer?
The way I thought about it is that XRDepthInformation that we return must be relevant to the XRView that was used to retrieve it. In case of a stereo system w/ only one depth buffer, there would be 2 options: either reprojecting the buffer so that each of XRViews gets the appropriate XRDepthInformation, or exposing an additional XRView that would be used only to obtain the single depth buffer (but then it'd be up to the app to reproject, there are some XRViews for which XRDepthInformation would be null, and we are creating a synthetic XRView so maybe not ideal). If we were to require the implementation to reproject the depth buffer, how big of a burden would that be?
I have the same problem
same but on windows10
I managed to get this to work on Windows 10 - the Path environment variable needs to include the path to the gpg.exe file - in my case, this was C:\Program Files (x86)\GnuPG\bin
The installation file still does not work so...
as @Albirew says, the extracted pidgin_gpg.dll needs to be copied to the plugin folder, but this is your personal pidgin plugin folder (part of your Roaming profile) at
C:\Users\[your username]\AppData\Roaming\.purple\plugins
Please note, AppData is a hidden folder and not usually visible by default. After doing these two steps, the plugin shows up in the plugins section of Pidgin.
I've extracted *.dll file and put into my \AppData\Roaming.purple\plugins, in pidgin's plugins, the plugin has appeared, but settings of this file into pigin are not working, and plugin generally doesn't work. What to do? Help please. Plugin is 0.9 version.
I tried again from scratch, and my installation worked fine. Just wondering... did you configure your own public / private key pair for your address using GPG? The following is all the configuration screen offers - it is a way to choose the key you want to use.

To solve this problem you could create a registry key HKEY_LOCAL_MACHINE\SOFTWARE[Wow6432Node]\GNU\GnuPG\Install Directory with REG_SZ value which consists the path to GnuPG
the extracted pidgin_gpg.dll can you please share the dll? how did you extract it ?
It's a long time ago, but as far as I remember the installation file can be treated like a zip file, try extracting using 7zip or similar?
Yes it worked with 7zip, but the dll don't work