What are the major changes introduced in Objectify v6, Can someone explain what is the changes related to the cursor and iterator in objectify v6 .?
Related
We are upgrading from v2 of tilelayer to v3. In v2 we had access to 30 default schemes/styles from Here.
normal.day
hybrid.day
normal.traffic.day
etc.
It looks like in v3 we only have access to 4.
explore.day
explore.night
explore.satellite.day
satellite.day
Is it possible to get or create the other styles, particularly the traffic styles?
This is entirely related to the version you are using:
If you have upgraded to version 3.0, you can use this tool:
https://demo.support.here.com/examples/v3/mrs_options
Where you will be able to change to the exact schema you are looking for and play with the parameters such as "Tile Type".
But, if you are using version 3.1, you must check the following tool:
https://demo.support.here.com/examples/v3.1/simple_raster_map
Where you can see the implementation of these "schemes" and "styles" is a bit different, this is by selecting the view you are looking for.
We hope this is helpful for you.
Just a quick note:
This is only available for users who have a developer here account.
So it seems that the RTDB sdk for Unity is missing the atomic increment function that is available in the other SDKs..
this guy -> database.ServerValue.increment(1);
I've noticed all that it is doing is setting the database reference to this object
{
'.sv': {
increment: 5
}
}
I have tested setting this object manually myself as the value for the database reference.. and it works as expected!
My question is..
Is that okay to do? Will that possibly break in the future while i have my app live? Or will i have time to update it to something new if they DO change it?
Yup, writing the sentinel value yourself is fine. We can't guarantee it won't ever break, but the specific value is actually documented for the REST API - so it'd require a major version upgrade if that were to ever change.
There is an open feature request #649 to add it to the SDK, so I'd recommend also chiming in there.
My department is planning to switching to using NMT V3 soon, but we will need the dictionary feature (adding glossary and Do-Not-Translate list) for training.
This might have been asked before but I don't see any recent post asking for it, would you be able to advise when this feature will be released? A rough estimation will do (2019 Q1 for example)
Many thanks,
Simon
The dictionary feature should be available in Custom Translator within the next month. Please be sure to follow the Microsoft Translator blog (http://aka.ms/TranslatorBlog) and Twitter (http://aka.ms/TranslatorTwitter) to stay up to date with major Translator releases.
This is a general question on how Features should be created when we have components that could potentially be used in multiple features.
Suppose a context (c1) takes a view (v1) and is added to a feature (f1). Now let's say v1 has potential use somewhere else and i want to create a new feature (f2) to include it in...but the Features module doesn't give you the option to do so. The only thing i can do is cloning v1 into v2 and use that in f2.
I may be shortsighted, but I think that if f2 needed v1, then just add the other components that would make up f2 and put them in f1...because more likely than not, those two features would be closely related (see One big feature...), at least enough to warrant using the same view (which in turn could include the same node types, roles, etc...)
I guess i'm just curious, has there been a case where you've created a feature with a view, and then needed to have a different feature using that same view?
The easiest solution in your case is to add a dependency from f2 to f1 to make sure that you have your v1 available.
You can't add v1 in f2 a second because your view would be defined twice and features would create a circular dependency.
Otherwise, to create reusable components, you should clone your view to make sure that you have "everything" you need in one same feature.
Does anyone know why I might get the following error in Google Maps API V3?
a.coord[jc] is not a function
I am updating from v2 and I get the error when placing certain markers on the map... The marker objects all appear to be similar enough to make this work, but some cause this error.
Thanks.
We need more code than that. Please supply all the code you are using to create and access the marker.
Also V3 is very different to V2 so you will not be able to use the same code.