Printable View
Hey all.
I used my custom cursor package for Windows.
"Hand" cursor is set for all buttons in a VB.NET form application project. But they refuse to follow system cursor pack. Despite of other cursors (Text beam, No, resize, etc.) which work properly.
I just noticed that "Hand" cursor in VS could be not the same as "Link" cursor in System control panel.
How can I rectify it?
Perhaps you could provide a series of steps that we could follow to reproduce the issue.
Is this a vb.net question? It looks more general Windows related.
I interpreted it as saying that a change had been made in Windows that was expected to be respected in VB code but wasn't.Quote:
Originally Posted by Peter Swinkels
Thanks all for cooperation.
Okay, I will provide some evidences and more details of my vb/win problem: (Via phone)
Current cursor package is look like this: (General cursors are following main/default mouse settings)
Attachment 181486
Even some particular cursor (which were commanded to follow) are actually working.
Attachment 181487 -> Attachment 181488
But in "Hand" case or some say "Link" (Which link "is not a property of..." in set of cursors) looks like this:
Attachment 181489 -> Attachment 181490
Link or hand, whatever it is, is not following the Windows cursor pack. How can I fix it?
Ah... bottom line, VB isn't respecting the Schema cursors.
What happens if you use the "No" cursor for the CheckBox?
Does it then use the right cursor?
-tg
Yes sir, it does.Quote:
Originally Posted by techgnome
Actually I tested here:
I think a hidden header code to make equal the Cursor.Hand and Cursor.Link would rectify the matter which I am not aware of.Quote:
Originally Posted by pourkascheff
No codes were applied. Only control properties (visually) has been changed.Quote:
Originally Posted by jmcilhinney
Exactly what it is.Quote:
Originally Posted by jmcilhinney
(looking at the Cursors Class source code) it appears the hand cursor and half a dozen other cursors are not mapped to the system cursors. They are hard coded as resources in the System.Windows.Forms.dll assembly.
If you can find the .cur file for the hand cursor you want to use, you could copy it to your project and access it as:Code:ConnectionStatus.Cursor = New Cursor("Your Path\To\yourhand.cur")
Stop trying to provide as little information as possible and starting making the effort to help us help you. It would appear that you also made some changes in Windows so how about you do as I asked and provide a series of steps that we can follow to reproduce the issue? Frankly, I don't care any more. If you're going to make us drag every bit of information out of you then why should we bother?Quote:
Originally Posted by pourkascheff
@jmcilhinney: At least he isn't dumping a lot of irrelevant info - I know some people may never had to chance to learn proper english but it's even more trouble to figure out what people want when they write in broken english.
@pourkascheff:
And, there is no need to take pictures with your phone: https://www.screentogif.com/. If that's too much trouble: https://www.businessinsider.nl/how-t...onal=true&r=US.