Fixed
Status Update
No update yet.
Comments
il...@google.com
al...@gmail.com
What do you mean by "share"? You mean take a screenshot of it?
You can already have a reference to the MapView simply by instantiating it on your own. Please do not forget to forward events (onCreate, onPause, etc.) to it.
You can already have a reference to the MapView simply by instantiating it on your own. Please do not forget to forward events (onCreate, onPause, etc.) to it.
jo...@gmail.com
For taking a screenshot you normally use a Bitmap to be drawn on by the view. This does not work with the API v2 as it uses OpenGL. Thus the outcome Bitmap is a just black.
vy...@gmail.com
It's possible via android build-in command like what eclipse DDMS "screen capture" did. The problem is the authority to execute the command.
Hope the next release can enhance this to take screen capture on google map v2.
Thanks...
Hope the next release can enhance this to take screen capture on google map v2.
Thanks...
il...@google.com
Yes, this was exactly what I was trying to do a few minutes ago. Didn't work.
Please guys, add such a functionality!
Please guys, add such a functionality!
vy...@gmail.com
I am developing an application in which this is a necessary and pivotal function; if this action is not possible then the majority of the app would be useless. Currently, the app uses Google Maps API v2, and I would really hate to have to downgrade back to Google Maps API v1 for this one function.
wk...@google.com
wk...@google.com
wk...@google.com
i am developing an application in which this is a necessary .
wk...@google.com
il...@google.com
Re #2: I don't know what the MapsV2 lib does internally, but it has no GLSurfaceView in the client's app. I suspect they render it in another app and bit-copy over the results into a private, from plain SurfaceView derived view that you can access in your app. I'd really like to see this to get https://code.google.com/p/robotium/issues/detail?id=462 supported.
do...@arctouch.com
#9 - we essentially use a GLSurfaceView. It's a slightly modified version, though, so gets obfuscated by proguard.
il...@google.com
Doubles are not a supported format for Android XML values. You can use argType="float"
gv...@gmail.com
We added GoogleMap.snapshot:
https://developers.google.com/maps/documentation/android/reference/com/google/android/gms/maps/GoogleMap
Note that the bitmap returned by snapshot cannot be sent off the device - use it for things like thumbnails or in notifications. See the docs for more complete information on how you can use snapshots.
Note that the bitmap returned by snapshot cannot be sent off the device - use it for things like thumbnails or in notifications. See the docs for more complete information on how you can use snapshots.
ju...@hotmail.com
Thank you very much!
il...@google.com
Many thanks!
Description
Version used: 1.0.0-alpha01
Devices/Android versions reproduced on: N/A
When specifying arguments for and a navigation action, there are only 4 options: "inferred, string, integer, reference"
Some arguments in my app use Boolean and Long and SafeArgs seem to only support "string" or "integer" (even if I manually put app:type="long"... it does not know what "long" is and falls back to "string")
Please add support for more types... especially Long and Boolean (you can "put" a lot more types into a Bundle)
I know I can manually add args to a bundle and then navigate... but I really want to use Directions from SafeArgs