the shramov/leaflet-plugins Google Layer used to work with Leaflet 0.5.1. However, with Leaflet 0.6.4, it freezes when using pinch zoom in the iOS Simulator 6.1. Zoom buttons and double click zoom work fine.
To reproduce the issue, simply download the repo at https://github.com/shramov/leaflet-plugins and apply the corresponding Leaflet version to the examples/google.html and load in iOS Simulator
I know that this plugin is not supported by Leaflet, but I was looking for help on how to debug this since it only happens with pinch zoom. I'm wondering what breaking changes could have been done to the zoom animation since Leaflet 0.5.1. I think the plugin is trying to trigger a zoom before the end of the zoom animation. Any help would be appreciated.
Link to issue: https://github.com/shramov/leaflet-plugins/issues/62
Thanks,
Nick,
Check to see what your options are when you are instantiating the L.map object. Pinch/zoom was freezing up for me on a variety of mobile devices with
zoomAnimation: false
in my options. When I changed it to true, the freezes went away. I believe that there are a number of bugs in 0.6.4 related to animation, with this one being the worst. For myself I have reverted back to 0.5.1. I like the animation options that 0.6.4 provides, but it seems that they are not yet fully baked.
This is not a "fix". However, the pinch zoom does NOT crash if I add a polyline for example.
Related
Hi I'm new here and I want to make a WebAR application using A-Frame. I know the basics and all that but one major problem I'm having is being able to walk around in the scene using ARCore running in Chrome. Is this even possible? I found a WebVR application from 6 years ago that solved the problem of positional tracking but the code's so depreciated it doesn't work anymore. I would prefer using ARCore for tracking but if nothing else marker based tracking will work too.
Edit: here's the depreciated code on github https://github.com/AVGP/goggle-paper
Doesn't use ARCore but instead marker based tracking. Better than nothing I suppose.
As of today, support for ARCore via the web (and thus A-Frame) is only available on Chrome browser with some Android devices.
Here are some great examples of working projects that you can build from:
https://github.com/chenzlabs/aframe-ar
https://aframe-ar.glitch.me/
New features such as image tracking are only available on Chrome Canary (experimental). See this example for image marker tracking:
https://arimg.glitch.me/
And associated documentation:
https://github.com/immersive-web/marker-tracking/blob/main/explainer.md
I want to know what disabling CSSOM View Scroll Coordinates flag in chrome://flags does and how can i replicate this behavior using code in my ReactJS app.
Additional information :
It seems after Chrome 85 update, ag-grid RTL support breaks and the grid is not able to scroll the content and sometimes the cells becomes white, i had to dig very deep into the past questions and try a lot of far fetched solutions to find what i have.
I found out that disabling CSSOM View Scroll Coordinates in chrome://flags will fix the bug!~ but the problem is i don't want to force my users and teach them to do this just so my app works, so i thought what ever disabling CSSOM View Scroll Coordinates does, maybe i can replicate it using css code or some other code
I have already reported this issue in ag-grid's git-hub but i'm still waiting for them to offer a solution in the mean time if i can get this to work only using code, it would be great as i have a lot of users which are not able to use my app just because of this simple bug ..
Thank you.
I am trying to implement zoom and panning in oxyplot Linear series but it does not recognise the zoom or panning.
I am using IsZoomEnabled = true, IsPanEnabled = true in both the axis.
Am I missing anything?
This is a very old issue that has not yet been resolved.
Update: I found another issue link and tested work of OxyPlot.Core 1.0.0 with Xamarin.Forms project. And zoom works fine!
Answering my own question if this can help anyone who is looking for a solution.
I have removed OxyPlot.Core 2.0 and only used OxyPlot.Xamarin.Forms nuget package across PCL, Android, and IOS .
This solved the zoom and panning issue that I have been facing in OxyPlot.Core package.
framers!
My VR app brings up a 3d photo menu, where I can select what kind of stereographic view works for my app. Some a frame apps (like Mozillas a frame painting app) do show in 3d. How do I ensure that my aframe shows in 3d?
My code is here: vr-hangman.glitch.me .
I would post a snippet but no part of the code stands out as having a bug.
When I use Chrome DevTools to fake a phone, I'm getting the error shown in this bug report: https://github.com/aframevr/aframe/issues/2385
I've figured out part of the answer, and resolved the bug above. I forked a glitch project to start out with, and it had an old version. However, my app still appears to be incompatible with the Samsung Internet VR experience.
So I forked an old A-Frame VR snippet on Glitch, so it was outdated with that bug.
Samsung Internet doesn't support "async function* runGame()" as a snippet. Even though it still updates the display.
I'm using OpenLayers with Google Layer, and I have a strange behaviour about vectors on the map.
On mobile (Android), when doing a multitouch event on the map (zoom), vectors move and zoom as the touchmove event is active. But when the touchend event is trigger, vectors are refresh at the right place and with their real size.
This is not happening with OpenstreetMap layer. I also tested some web pages implementing OpenLayers & Google Layer & a vector layer on my mobile, and they all have the same issue. Any idea why ?
I tested this one, if someone want to reproduce : http://www.macfh.co.uk/Test/Google_with_OpenLayers.html With a multitouch event, marker is moving/zooming, and then go back to its initial place.
I already took care about the sphericalMercator specifity, so I think it's not the problem.
Thanks in advance !
Tiles positionning for google layers is done through their api, which doesn't allow to make pinch zoom work the same way it’s done for all others layers: Pinch zooming doesn't work with google layers.
If you want pinch zoom to work, you should consider using layers with direct access to tiles (OSM, Bing, …). And your mobile will thank you for the decrease of number of scripts to load ;).