It also takes non-development time to get a Graphics Designer to create your custom cursors - but even that should be a small amount of time. This is maybe a whole workday (8 hours) (at most) to handle cursors in your application code. Then in your UI code, you just monintor the mouse move event, you get the current location of the mouse and you just do a small bit of logic to determine if mouse is over "this area" then display cursor X, else if it is over "that area" then display cursor Y and so on. You then register that Cursor object in memory, and whenever you want to display that cursor object, you call the SetCursor function and send in a memory pointer to your custom cursor image. ![]() Using this function you can tell it to set the cursor to one of the predefined / managed / native Windows Cursors - or you can create a custom cursor object from any image file. ![]() Not only does it NOT require some kind of license code to be able to interact with the User32.dll, but it doesn't matter what programming language you are using, to change the cursor displayed on the user's screen, you have to use the User32.dll function. In Windows there is a 'SetCursor' function in the User32.dll. ![]() TLDR: windows does not charge to access the API that allows the application to change the cursors AND the amount of development work to display a custom cursor is minimal.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |