( ( ( (How do I suppress WaitCursor) ) ) )
-
Guys I'm at a loss! I don't want wait cursor to be displayed in my app at all. How can I suppress it totally or change the picture of the WaitCursor to Arrow (default) cursor - so that anytime wait cursor is invoked it would show the arrow, hence show no change. And why doesn't Cursor.Current = Cursors.Arrow; work. It's supposed to set the current cursor, but it does nothing! Any help is appreciated!
-
Guys I'm at a loss! I don't want wait cursor to be displayed in my app at all. How can I suppress it totally or change the picture of the WaitCursor to Arrow (default) cursor - so that anytime wait cursor is invoked it would show the arrow, hence show no change. And why doesn't Cursor.Current = Cursors.Arrow; work. It's supposed to set the current cursor, but it does nothing! Any help is appreciated!
That all depends on what's causing the wait cursor. If it's a web browser control on your form, then no, you can't stop the wait cursor from happening. The browser control is what' setting the cursor to Busy. So long as the cursor is over that control, it'll show up Busy. Changing the image of the cursor, as in your workaround, would require changing the image system-wide. A practice I greatly discourage. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
-
That all depends on what's causing the wait cursor. If it's a web browser control on your form, then no, you can't stop the wait cursor from happening. The browser control is what' setting the cursor to Busy. So long as the cursor is over that control, it'll show up Busy. Changing the image of the cursor, as in your workaround, would require changing the image system-wide. A practice I greatly discourage. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
"Changing the image of the cursor, as in your workaround, would require changing the image system-wide. A practice I greatly discourage." I agree. That would be sloppy. Yes, the WebBrowser control is causing it to fire the cursor change, so how can I prevent that. Can I derive from the WebBrowser control and change it there? There's got to be a way to do this!!!!
-
"Changing the image of the cursor, as in your workaround, would require changing the image system-wide. A practice I greatly discourage." I agree. That would be sloppy. Yes, the WebBrowser control is causing it to fire the cursor change, so how can I prevent that. Can I derive from the WebBrowser control and change it there? There's got to be a way to do this!!!!
peshkunta wrote:
Yes, the WebBrowser control is causing it to fire the cursor change, so how can I prevent that.
There's no way to prevent it. You could create you own class from the WebBrowser class, but you still wouldn't be able to prevent the cursor from changing because it's not the class code that's changing the cursor. It's the Internet Explorer object code that's doing it, and there's no way you can change that. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
-
peshkunta wrote:
Yes, the WebBrowser control is causing it to fire the cursor change, so how can I prevent that.
There's no way to prevent it. You could create you own class from the WebBrowser class, but you still wouldn't be able to prevent the cursor from changing because it's not the class code that's changing the cursor. It's the Internet Explorer object code that's doing it, and there's no way you can change that. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome
-
peshkunta wrote:
The WebBrowser object is a control. Why couldn't I make a custom web browser control???
You could, but doing so would require writing your own browser. You could largely bypass doing so by using the firefox codebase, but would inject the GPL into your code as a result.
-
The WebBrowser class in .NET is a WRAPPER for the IE COM object. In order to supply this functionality, you'd have to write your own web browser class, supplying all the HTML rendering code, but does not wrap the IE COM control, which is entirely possible. Just creating a new class, inheriting from the existing WebBrowser class, will not allow you to do what you want, since you're inheriting from the WebBrowser class, you're also inheriting the COM object that it wraps. RageInTheMachine9532 "...a pungent, ghastly, stinky piece of cheese!" -- The Roaming Gnome