I have problem when i am using leaflet library 1.0.3 and it works fine and show no error or warning when it is 0.7.7 i have using following libraries:
angular 1.5.8
angular material 1.1.3
angular-leaflet-directive 0.10.0
leaflet - 1.0.3
My map is visible properly even the marker cluster is working fine but in developer tool it is showing me error like these
Unfortunately angular-leaflet-directive is already quite old, the latest release version v0.10.0 dates from 2015, when Leaflet was still in 0.x.x version.
There are breaking changes when upgrading to Leaflet version 1.x.x.
Since you seem to say that your app still behaves correctly, except for the error in the browser console, then either you can live with it, or downgrade to Leaflet 0.7.7.
You can also get ride of angular-leaflet-directive and directly use Leaflet 1.x.x with AngularJS.
Related
I am working on a project in MixedReality using mainly MRTK and its features. I found out that MRTK can use QR codes to read data, and I wanted to use it and try multiples ideas.
The problem is that, currently, is seems any QR feature is nonexistent in my project.
I Installed the NuGet package Microsoft.MixedReality.QR and its corresponding Microsoft.VCRTForwarders.14 package, as indicated in
https://localjoost.github.io/Reading-QR-codes-with-an-MRTK2-Extension-Service/
But anything I try in code, from my project, will tell me in the console window that the namespace could not be found, and all cascading items (properties, classes, functions) could not be found either, none of them.
It is weird since everything should be installed and up to date ( I verified this directly in Visual Studio and everything is there).
Any kind of help would be much appreciated, thanks !
For Unity projects, you need to import NuGet for Unity to install Mixed Reality QR NuGet package. Meanwhile the tutorial you are referring is not an official document. Some types/classes are defined by the author and are not included in Microsoft.MixedReality.QR namespace.
Please refer to the new QR sample on https://github.com/yl-msft/QRTracking and all the C# API references are listed on QR Code tracking API reference
I've been developing an app that uses QRcode on the hololens as well. I ran into that issue before, and the console seemed to throw that error for me because I was using the wrong version of the MRTK services in the Microsoft Mixed Reality Feature Tool. I would recommend using version 2.6.1 for all your services. Do you by any chance have a problem where "QR tracking is not supported" for the Unity Project you are building?
I have a popup in code written in Kony visualizer V8, I want to export all of them and import it to Kony Visualizer V9.
Note: Kony Visualizer V9 doesn't support the normal popups and I don't need to create it from scratch.
This is the popup's image inside the Visualiser V8:
Had a similar requirement recently and as V9 doesn't support HBOX or VBOX, created a component for popup and used that in UI. After changing all popups to components you can upgrade from v8 to v9 without issues.
Also do not use masters as that is also not compatible with V9.
You can use components and reuse them for popups wherever needed.
Gone thru the same situation before. Found that HBOX, VBOX and few other widgets which are used in the old versions are deprecated in the recent versions. Hence all the old widgets should be updated to the latest equivalent widgets.
If the project is mobile application then Temenos has an upgrade tool which will help you in making the changes to the project and upgrade it. But if the project is of Desktop web then we need to manually update the widgets one by one. Once all the deprecated widgets are upgraded then export the project and import the same in latest visualizer.
I am using the latest unity SDK 2.12.0 and Unity 2017.4.
My unity project is available here:
https://github.com/jignesh015/Watson_trial
Please note that you will need an IBM Apikey to access the API functionality.
I followed the following video tutorial for setting up the SDK:
https://www.youtube.com/watch?v=_K62R9Jnxag
While running the ExampleStreaming sample as shown in the video, I'm getting the following log:
[SpeechToText.SendStart()][DEBUG] SendStart() with the following params: {"action":"start","content-type":"audio/l16;rate=22050;channels=1;","inactivity_timeout":-1,"interim_results":true,"max_alternatives":0,"profanity_filter":false,"smart_formatting":true,"speaker_labels":false,"timestamps":true,"word_confidence":true
[SpeechToText.OnListenClosed()][DEBUG] OnListenClosed(), State = DISCONNECTED
[SpeechToText.KeepAlive()][DEBUG] KeepAlive exited.
I have thoroughly searched for this issue. Seems like many people have faced a similar issue, but none of the posts have a satisfactory solution. Can anyone help me with this?
This has to do with the move to TLS 1.2. Only Unity 2018.2 and above support TLS 1.2 using .NET 4.x equivalent Scripting Runtime Version. https://github.com/watson-developer-cloud/unity-sdk#streaming-outside-of-us-south-region
Since you are using Unity 2017.4 you will need to create your Speech to Text instance in US South (Dallas). This is the only region that still supports TLS 1.0.
Alternatively, you can update to Unity 2018.2 or above and switch to Scripting Runtime Version .NET 4.x equivalent.
I created a new WTP project in Eclipse that uses App Engine based on the documentation. I also use Google Clound Endpoints. The issue is that I can't access my API anymore.
http://localhost:8888/_ah/api/discovery/v1/apis returns
{
"kind" : "discovery#directoryList",
"discoveryVersion" : "v1"
}
I also tried to generate the javascript client library but I get an error Not an app engine project. I managed to generate the javascript library with the command line.
Anybody managed to use the new GPE with Endpoints?
Unfortunately, we don't have endpoints working with WTP-style projects as yet (the released version is a preview). We're working on this right now.
I have been having a real hard time getting API Tooling to work in Eclipse 3.4.2. It keeps telling me:
The minor version should be incremented in version 3.4.0.qualifier, since new APIs have been added since version 3.4.0.40001
That being said, I have generated the plugins that are used for the baseline from the exact same code that it is being analyzed against. The API Tools docs say that it compares the current code against the baseline to see if there are any differences. I can't see how there could be differences if the built version is built from the current code.
The way that I tested it:
Create a new eclipse workspace
Create a new Plug-in Project with API Analysis turned on
Add a simple class to that plugin and export the package with that class in it
Build/Export that plugin to some location on your hard drive
Set the workspace baseline to that location and do a full build
You get an error for the project in your problems view.
Thanks,
-One very perplexed user
Looks like this is something that got fixed in 3.5. Too bad my company doesn't want us using 3.5 in case there are any incompatibility issues. (there were 3.3 to 3.4)
My recommendation to anyone who wants to do Eclipse API Analysis is to use 3.5.
First off, I apologize for jumping on a thread late after its "active time" but I am currently running into this exact situation, but with Eclipse Helios 3.6.
From your answer, you noted that something was fixed in 3.5. Are you aware of what this exact fix was AND if you have yet been able to verify that it is working under Eclipse Helios 3.6?
I would really like to have PDE API tooling working but I'm nearing my time allowed on this effort and need to move forward onto some pending tasks.
Thanks!
EDIT: I would have posted this in a followup link but did not see any such links available.