Windowscommunitytoolkit: Question - SwipeControl

Created on 19 Feb 2018  路  6Comments  路  Source: windows-toolkit/WindowsCommunityToolkit

I see SlidableListItem XAML Control is deprecated as it is being replaced with Swipe control.

I can't figure out how to use mouse input on the swipe control. In SlidableListItem I used MouseSlidingEnabled="True" but this does not exist in swipe control.

Any ideas or pointers will be appreciated or is a mouse swipe not a feature in swipe control?

Most helpful comment

@skendrot Well, let me clarify the mouse swipe.

Mouse swipe
1) left click mouse
2) move mouse
3) release left click mouse

In summary: one mouse click

Context Menu
1)Right click mouse
2)wait for context menu
3)move to correct item in context menu
3)Left click mouse

In summary : 2 mouse clicks

I use it successfully for filtering items and selecting favorites as in gif below with much greater efficiency than a context menu.

swipe

All 6 comments

I don't believe the SwipeControl supports this functionality. Honestly I don't think the toolkit version should have supported it either. Swiping items with a mouse doesn't make sense. Adding context menus is better suited for mouse input.

Note: This issue would be better suited for StackOverflow or the MSDN forums as it is a question about the SwipeControl and not about a toolkit item. Also please use StackOverflow for any how-to questions related to the toolkit. This is noted in Feedback and Requests of the readme and in the Contributing guidelines. We ask to use SO because SO has much better visibility over closed github items with search engines.

Thanks @skendrot Well from your comments I gather that I'm stuck with no upgrade path to Swipe Control. Would have been nice if the current control does not get deprecated as my users like the current side swipe with mouse. Much faster and easier to use than context menu and it replicates the same functionality for listview in "mobile view"

It is deprecated, but not removed.
Please explain how swipe with mouse is faster and easier when comparing the following steps

Mouse swipe

  1. left click mouse and hold
  2. move mouse left or right (which direction is initially not known)
  3. release mouse click
  4. move to exposed button (which is in the opposite direction from which you just dragged the mouse)
  5. click button

Context menu

  1. right click mouse
  2. move to context menu item
  3. click item

@skendrot Well, let me clarify the mouse swipe.

Mouse swipe
1) left click mouse
2) move mouse
3) release left click mouse

In summary: one mouse click

Context Menu
1)Right click mouse
2)wait for context menu
3)move to correct item in context menu
3)Left click mouse

In summary : 2 mouse clicks

I use it successfully for filtering items and selecting favorites as in gif below with much greater efficiency than a context menu.

swipe

Microsoft use a SwipeControl type arrangement themselves in Outlook which allows interaction via the mouse. I think there a valid scenarios that should a mouse to be used as input for a SwipeControl. Especially for apps that are designed to run across desktops and tablets, it makes sense to allow the interactions with the app to be consistent across devices.

I've created an idea on the Microsoft developer feedback site if anyone else is interested:

https://wpdev.uservoice.com/forums/110705-universal-windows-platform/suggestions/33940351-swipecontrol-should-support-mouse-input

Was this page helpful?
0 / 5 - 0 ratings