![]() When you call CreateFromCoreCursor with a Custom CoreCursor, the method forwards on to the constructor for InputDesktopResourceCursor (with a null module name b/c CoreCursor only supports the current module unlike InputCursor), which succeeds or fails dependent on the output of LoadCursor. are reserved by system resources (in the current executable module), which is why you see it loading syscursors at those IDs and failing with less generic IDs. Why when creating a new CoreCursor with CoreCursorType.Custom, and a uint resource Id am I seeing build-in cursors?īeta Was this translation helpful? Give feedback. res file and try to create a CoreCursor using that resource Id, I get a System.Runtime,InteropServices.COMException: The Specified resource name cannot be found in the image file. ![]() If I change the resource id of one of the cursors to, say, 200, recreate the. res file works in a UWP application, so I know the problem is not with the resources. Indeed, as I play with the resource id value, setting it to values in the range I see a variety of 'standard' cursors including some that are not in the CoreCursorType enumeration. However, the effect of the code above is to simply load a built-in cursor. Var t = InputCursor.CreateFromCoreCursor(cursor) Var cursor = new CoreCursor(Windows.UI., 102) 102 is the resource id of a cursor in the. Private void OnPointerPressed(object sender, PointerRoutedEventArgs e) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |