Status Update
No update yet.
Comments
[Deleted User] <[Deleted User]>
that way will be cool and user friendly.
jg...@google.com
jg...@google.com
Also having the option to either pan or zoom with the scroll wheel would be useful.
[Deleted User] <[Deleted User]>
"Add the ability to scroll using the mouse wheel, add it to default UI, and
let developers disable it."
that way will help user for zoom in & zoom out easier..
let developers disable it."
that way will help user for zoom in & zoom out easier..
jg...@google.com
I need mouse wheel to operate zooming in and out.
I have wait for several weeks already.
develop from Beijing China
I have wait for several weeks already.
develop from Beijing China
[Deleted User] <[Deleted User]>
Mousewheel zooming please! :)
jg...@google.com
I can see that this issue is "Acknowledged", but is there any way to see when it
will be released?
will be released?
je...@google.com
ap...@google.com
When an issue in this tracker changes status (like from Acknowledged->Fixed), you'll
receive an email saying so. We generally don't reveal timelines for feature requests.
receive an email saying so. We generally don't reveal timelines for feature requests.
ap...@google.com
Pamela, for being fair: this is not feature request. This is backward compatibility
issue.
I think this is the only one blocking issue for migrating from GMap API v2 to v3.
issue.
I think this is the only one blocking issue for migrating from GMap API v2 to v3.
je...@google.com
#9, this is definitely not the only feature missing in v3. The overview page states
"The initial launch has a smaller feature set than that available in the V2 API."
"The initial launch has a smaller feature set than that available in the V2 API."
jg...@google.com
#8 I appreciate the quick answer, right now I'm about to choose to either develop a
new site on the old v2 or the new v3 api, the site is scheduled to be in production
within this year, what are the pros and cones i have to consider?
new site on the old v2 or the new v3 api, the site is scheduled to be in production
within this year, what are the pros and cones i have to consider?
gs...@yahoo.com
I'd recommend going with v2 API for now. It is the safer choice. I recently strated a
project with v3 and had to port back to v2 in a hurry because I ran into compatibility
issues with IE.
project with v3 and had to port back to v2 in a hurry because I ran into compatibility
issues with IE.
Description
<androidx.viewpager2.widget.ViewPager2
android:paddingEnd="20dp"
android:paddingStart="20dp"
android:clipToPadding="false" />
the padding is also applied to overscrollIndicators, which makes them not stick to the view bounds. please check the GIF attached