Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lots of lagging when using touch drag and drop. #448

Closed
las-nsc opened this issue Jul 7, 2022 · 3 comments
Closed

Lots of lagging when using touch drag and drop. #448

las-nsc opened this issue Jul 7, 2022 · 3 comments
Milestone

Comments

@las-nsc
Copy link

las-nsc commented Jul 7, 2022

Describe the bug
We have implemented drag and drop using this library and tested it with mouse without any significant issues (except this), but when it was deployed to the target hardware which uses touch, there was semi-random and significant lagging issues where it could take minutes to drag something across the screen.

To Reproduce
Unfortunately I can't share our code to demonstrate the issue, but I have tried to diagnose the issue myself by using the source for this library. Running performance diagnostics shows the majority of time spent on the System.Windows.DragDrop.DoDragDrop method, which seems to block the UI thread due to its synchronous nature and can't be offloaded to another thread due to needing access to the dragged item template. One thing I did try is to add CacheMode = new BitmapCache(); to the DragDropPreview which might have improved things a little, but I am still seeing noticable lagging occasionally.

Expected behavior
No significant lagging with touch, same as mouse.

Screenshots
It would have to be a video, but not sure if I can share. TBD

Desktop (please complete the following information):

  • OS: Windows 10 Pro
  • Version 21H2

I'm not sure why the issue is only noticable when using touch and not mouse, and it doesn't seem to be directly caused by anything this library is doing itself (particularly as the touch code doesn't seem to do anything much different to mouse), but is core to how the library works. Has anyone seen this sort of issue before and have a workaround?

@las-nsc las-nsc added the Bug label Jul 7, 2022
@las-nsc
Copy link
Author

las-nsc commented Jul 7, 2022

Having looked closer at other issues, I believe this is a duplicate of #418, being fixed by #444

@dxh-sc
Copy link

dxh-sc commented Jul 20, 2022

I have same issue

@punker76 punker76 added this to the 3.2.0 milestone Aug 30, 2022
@punker76 punker76 added Duplicate and removed Bug labels Aug 30, 2022
@punker76
Copy link
Owner

Duplicate of #418

@punker76 punker76 marked this as a duplicate of #418 Aug 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants