You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running in time critical rendering situations such as drag and drop, waiting for v-sync can result in stuttering/lagging behind. Unfortunately, with waiting for v-sync being the default for CanvasAnimatedControl, this makes these scenarios almost impossible to implement with a satisfying user experience.
Below a comparison between calling Present with a parameter larger than 1 and calling it with 0 being passed:
Because of that, I would like to propose an option on CanvasAnimatedControl such that we can disable vsync and are able to use it in scenarios such as drag and drop. I would be more than happy to (help) implement this if this proposal gets approved.
Proposed API:
namespace Microsoft.Graphics.Canvas;publicsealedclassCanvasAnimatedControl{/// <summary>/// Determines the sync interval used by CanvasAnimatedControl. Defaults to 1. /// See https://microsoft.github.io/Win2D/WinUI2/html/M_Microsoft_Graphics_Canvas_CanvasSwapChain_Present_1.htm for more context./// </summary> publicintSyncInterval{get;set;}=1;}
The text was updated successfully, but these errors were encountered:
When running in time critical rendering situations such as drag and drop, waiting for v-sync can result in stuttering/lagging behind. Unfortunately, with waiting for v-sync being the default for CanvasAnimatedControl, this makes these scenarios almost impossible to implement with a satisfying user experience.
Below a comparison between calling Present with a parameter larger than 1 and calling it with 0 being passed:
Because of that, I would like to propose an option on CanvasAnimatedControl such that we can disable vsync and are able to use it in scenarios such as drag and drop. I would be more than happy to (help) implement this if this proposal gets approved.
Proposed API:
The text was updated successfully, but these errors were encountered: