I can't seem to figure out how to get the Unity Audio Manager to see the GVR Audio Spacializer.
I have had the SDK installed and everything works by the GVR Audiosource stuff.
SDK seems to be missing parts of the library:
DllNotFoundException: audioplugingvrunity
GvrAudio.Initialize (.GvrAudioListener listener, Quality quality) (at Assets/GoogleVR/Scripts/Audio/GvrAudio.cs:73)
GvrAudioListener.Awake () (at Assets/GoogleVR/Scripts/Audio/GvrAudioListener.cs:38)
I'm on a mac, not sure why it's looking for a DLL
Ensure building for Android and have imported all the GVR audio bits (including x86).
OP also asked on forum and a Google employee answered then OP resolved (posting answer + notes here for any others that find this question first like I did):
https://forum.unity3d.com/threads/gvr-audio-spatializer-plugin-missing-in-unity.446017/
Related
Recently I've started to work with Maven JavaFX11 (openJFX11) and I noticed that there are many issues with javadoc in NetBeans. After some research I found that there is a bug with NetBeans that doesn't download the source+docs dependecies the right way (I mean it downloads it, but the next step to make it work is that you rename the source+docs files
issue & solution right here
But after I did that I noticed another docs issue and I have not found any similar topic on this so i dont know if it's just me or somebody have/had the same problem
When i type something like this:
private Label label;
label.[something...]
It only shows some of the docs.
It describes object Label the right way
After I type the dot, it only tells me about like 1/5 of the docs. Let me show you simple example.
And here is example of one that works
I looked into the javafx docs (.jar) and opened the Note.html and there ARE as the same things as in the docs they have on their websites, including all the methods, etc.
So... Dont you know, where the problem might be? I'm using the openJFX 11
It looks like you have encountered a known issue. See these NetBeans Bug Reports:
NETBEANS-1396 Maven: Downloaded javadoc / sources not attached to artifact with classifier.
NETBEANS-2197 Missing code completion and Javadocs in maven projects with classifier.
Also see these OpenJFX issues:
How to add javadoc in Netbeans #44
Attached Javadoc does not follow Maven convention #6
The fix is being implemented through a pull request for NetBeans 1396.
That fix is already included in NetBeans 11.3 which has a target release date of "January 15, 2020".
I have an Android QR code reading app that runs on a cheap phone with no autofocus. QR code that I must read is small and on camera preview looks blurry. The one app able to read this code is NeoReader.
Does everybody know good free libraries to read QR codes?
I know that:
ZBar (it's ok but not works with blurry code)
ZXing (this Barcode reader not reads the required code; don't tried to integrate)
NeoReader SDK (not free)
My init code for ZBar:
scanner = new ImageScanner();
scanner.setConfig(0, Config.ENABLE, 0);
scanner.setConfig(Symbol.QRCODE, Config.ENABLE, 1);
scanner.setConfig(0, Config.X_DENSITY, 1);
scanner.setConfig(0, Config.Y_DENSITY, 1);
If none of the four above is an option (or even if they where!) I would strongly suggest using Googles own library found in Google Play services under the namespace com.google.android.gms.vision.barcode. It scans the codes locally, fast and robust, and you have full control of the source code in just a few classes.
For a simple example check out Android QR Code Reader Made Easy. That should get you up and running in no time! There's also further reading linked at the end of the post for advanced examples.
I was working on harbuzz old one. now a new version of harbuzz-ng has came. now this structure is completely changes in comparison of old code. Without API docs its really hard to work/use this library. I google about it but didnot find any relavent details.
How can i start using it. Any test program to understand the input and output for this library.
If anybody have a test /hello world type from or any reference docs for API please share.
Some good and simple examples are listed on Harfbuzz wiki, 1, 2
I suggest you a higher level library, Pango if you need layout things like line wrap and I guess you would find better doucmentation for it than HarfBuzz itself.
You may have a look at State of Text Rendering also.
adding to the above examples i have also made and collected some sample harfbuzz examples which you can find it here
this link https://lazka.github.io/pgi-docs/HarfBuzz-0.0/index.html might aid you
I would say you should read all Harfbuzz mail archives
plus go to harfbuzz github acc try reading pr and issues threads.
at last due to scarcity of documentations,the only doc you got is the sourcecode itself :P
My Qt program (using qt v5.0.2) contains a QWebView in which the user is supposed to login using their email address and a password.
Everything works fine on Windows (tried on w7 and server 2008) but on Mac (10.7.5) I have encountered an annoying issue.
When pressing alt-2 (key combination for #) nothing happens.
I have spent countless hours testing and trying to find any info on the net about it, but I really can't find anything about it.
Is there any workaround? Fix? Or is this even a known issue?
Edit:
As noted in comments below, my keyboard is European/Swedish.
It's a genuine Qt Bug. I reported it as https://bugreports.qt-project.org/browse/QTBUG-34981
Today we found the code responsible for it in
./qtwebkit/Source/WebKit/qt/WebCoreSupport/EditorClientQt.cpp
Around line 480 it says
#ifndef Q_WS_MAC
// We need to exclude checking for Alt because it is just a different Shift
if (!kevent->altKey())
#endif
shouldInsertText = true;
Apparently, Q_WS_MAC isn't defined on Mac Builds at this time - I think it's been deprecated in favor of Q_OS_MAC.S
Simply changing the statement to
shouldInsertText = true;
when compiling on Mac fixed the problem for us.
I recently found a method (ByteArray.clear()) that FlexBuilder complains is possibly undefined; however, the method is in fact documented in the Flex LiveDocs. It must have been added in a later version of the SDK than I have installed. I'm not asking about this particular method, but I'm giving it as an example of the documentation issue that I'm trying to resolve. My questions are:
How can I determine what version of the SDK or Flash player that a method or property was added in?
How can I tell which versions of the SDK are supported on which Flash player versions?
I want to be able to determine from the documentation, instead of compiler or runtime errors, what SDK and Flash player versions are needed to support newly added methods.
With Java I look for the #since javadoc tag when I need to know this, but I can't find an equivalent feature in the Flex docs.
Often, the documentation will say that a given property is available as of Flashplayer version x.y.z Unfortunately, even though you may be looking at the documentation, and the documentation may CLAIM that a function exists (and in the case of the ByteArray most certainly does exist), sometimes the compiler is just buggy and throws a hissy-fit.
Your best bet is to make sure that you have the most recent version of the Flex dev. kit and make sure you are publishing for the most recent major release ( Flash >= 10 ). That being done, rely on the documentation here: http://livedocs.adobe.com/flex/3/langref/index.html.
After that it is the "cross your fingers and pray" method. Sorry.
Based on what James suggested you could use this code:
try
{
// Use the clear method if the flash player supports it (10+)
this.swf['clear']();
}
catch (e:Error)
{
// Must be flash player 9 or lower so free the variable
this.swf = new ByteArray();
}
There may be a better way to clear/free a ByteArray's memory in older player versions, so let me know if there are.
ByteArray is a Flash Player class, not a Flex class. The Flash Player APIs are implemented in the runtime so they are tied to specific releases of Flash Player. Usually the ASDoc specifies when an API was added. But in this case it seems that it doesn't. So here are a few things to try:
Get around the compiler error (might result in a runtime error if you are using a version of FP that doesn't have the clear method): byteArray['clear']()
Change the version of FP used in Flex to 10 to see if maybe this was added in FP 10 and for some reason that wasn't specified in the ASDoc.
Flex uses a playerglobal.swc file as stubs for the FP APIs. It's possible that SWC doesn't include something it should. In which case you should file a bug.