I hava a panorama view with multiple panorama items. In one of these panorama items I have a grid within a ScrollViewer. The grid is too large in terms of width.
The problem is that if the user slides the panorama view gets triggered and changes the panorama item, althrough the the scroll viewer should actually scroll horizontally (until the end of the grid).
However, if the user slides very slowly, the panorama view does not get triggered and only the scrolling takes place. This is the intended behaviour.
Thank you very much
You can use isHitTestVisible property.
//Disable panorama scrolling
MyPanorama.IsHitTestVisible = false;
//Enable panorama scrolling
MyPanorama.IsHitTestVisible = true;
Use this in a ManipulationStarted listener. That is, when the use starts scrolling horizontally, you can temporarily make IsHitTestVisible to be false.
Related
I am working on an Angular webapplication and I want to be able to zoom in my agm-map with ctrl+scrollwheel, without scrolling the page up and down. At the same time I want to be able to scroll the page normally when not pressing ctrl, because the map covers a lot of the screen and it would be awkward to scroll past it otherwise.
At first the problem was to only get the map to scroll when ctrl was pressed. Following documentation (https://developers.google.com/maps/documentation/javascript/interaction) and comments from other developers this was achieved by setting gestureHandling to cooperative and scrollWheel to null.
Now I can scroll the page normally even when hovering over the map by scrolling without pressing ctrl and still use the scrollwheel to zoom in and out within the map when pressing ctrl. But whenever I do the later the whole page scrolls up or down a bit as well.
I tried to forego setting scrollwheel to null in the agm-map, but then the map doesn't need me to use ctrl anymore despite gestureHandling still being set to cooperative and the webpage still scrolls when zooming in the map. I tried the same setup in other views of the Webapp to see if the problem occurs consistently and it does. It also happens in both Chrome and Firefox. I tried to stop eventPropagation but I wasn't sure how to do it so it only stops when I also press ctrl.
Besides this issue everything I have set up in the map works fine (Some polygons and buttons. The bounds are set dynamically).
<div class="mapContainer mt-4">
<agm-map [scrollwheel]="null" [gestureHandling]="'cooperative'" [latitude]="mapLat" [longitude]="mapLng" [fitBounds]="mapBoundsLiteral" [mapTypeControl]="true" [mapTypeId]="'satellite'" [streetViewControl]="false" #map>
[...]
</agm-map>
</div>
I'd expect the page and map to act exactly like it does in the first demo in the documentation as I use the same attributes where they seem relevant. This means the page should scroll normally when using just the scrollwheel but shouldn't scroll when I zoom the map with ctrl+scrollwheel, but the page always scrolls.
In my GWT application I use a DialogBox like this:
DialogBox dialog = new DialogBox(autoHide, true);
dialog.setText("Hello GWT DialogBox");
dialog.setGlassEnabled(true);
dialog.center();
dialog.show();
My whole page is very long and it scrolls vertically.
This works fine, the dialog pops up and the rest of the page is darkened. When scrolling (with mouse wheel) outside the dialog box nothing happens, which is fine. But when scrolling inside of the dialog box, the whole page scrolls away including the dialog box itself. This feels very wrong.
It is even possible to use scrolling inside the dialog box to scroll the dialog box out of the visible area and then there is no way to scroll it back, because scrolling outside of the dialog box does not do anything.
How to prevent the page from scrolling when using the mouse wheel inside the dialog box?
dialog.setModal(true);
might work. This discards all the events that do not affect the DialogBox, aka scroll that is affecting the underlying page.
WAIT NEVER MIND, DOESN'T WORK
The Page will still scroll if the mouse is within the DialogBox.
Found this though:
https://www.mail-archive.com/google-web-toolkit#googlegroups.com/msg62527.html
Might be useful.
I have found a strange issue with my windows phone 8 application using a panorama control.
Each panorama item is created dynamically using a templateselector and view models as itemsource.
In one of the panorama items I have a Listpicker. Once it's activated the panorama control scrolls back to the first panorama item. I was able to temporary fix the problem by setting the height of the view to 1000. Unfortunately, the same issue occurs when I set a hidden loading view visible.
It seems as the problem occurs when the layout is updated?
Any ideas on what could be causing this behavior?
When you navigate to a page with LongListSelector where items have already been loaded (items are already present in itemsSource), the focus, by default is on top most item. You can scroll down to view other items.
In my application, I have a requirement to focus on bottom most item and user can scroll up to view other items.
One solution is to call ScrollTo function on bottom most item. Here, user can see the list being loaded and then change of focus from top to bottom most element. So, the user experience becomes very bad.
Is there any seamless way to do it?
I think ScrollTo is most efficient for a LongListSelector. But if you need to have the experience more seamless you might want to wait/halt your app with a loading screen while the LLS is populated and the focus is changed to the bottom. Async commands or a simple loading status bar could do the trick.
Am trying to display AppBar for entire html page in my Metro app.Whenever I click on the other items of the page, immediately AppBar is disappearing.Can anyone give me advice to set my AppBar remain constant for entire page in Metro App.Here am using appbar.winControl.show();.
For JavaScript: appBar.sticky = true;
For XAML: AppBar.IsSticky = true;
This will keep your AppBar on the screen even if you click elsewhere on the page. But remember that the design guidance is for a transient AppBar that will light-dismiss (disappear when you touch somewhere else). Here is the guidance for when it should be sticky, from the guidelines and checklist for app bars:
Do set the app bar's dismissal mode to sticky when displaying contextual commands.
If you have contextual commands on an app bar, set the mode to sticky while that context exists and turn off the sticky mode when the context is no longer present (such as when a photo is deselected). In sticky mode, the bar doesn't automatically hide when the user interacts with the app. This is useful for multi-select scenarios or when the context involves interaction such as manipulating cropping handles. The bar stays visible while the user performs the actions. The user can still hide the bar by swiping the top or bottom edge of the screen and they can show it again with an edge swipe.
Finally, here is the JS reference for the sticky property.