> But why do that? If the application is processing, it should modify the cursor itself, no?
Doesn't seem to. I did a test, had it loop through a 25 page doc. It never
did change the cursor on it's own. It pretty much used all of Word's
processing to run the macro. (I couldn't work on any other opened doc while
the macro ran).
The Screen.Cursor worked, until I stuck a Doevents in the loop to allow for
some freedom. That seemed to reset the cursor. I was hoping for a way to just
set the cursor for the current window (active doc).
> hth,
>
> -Peter
Peter - 22 Jan 2005 00:21 GMT
> > But why do that? If the application is processing, it should modify the
> cursor itself, no?
[quoted text clipped - 7 lines]
> some freedom. That seemed to reset the cursor. I was hoping for a way to just
> set the cursor for the current window (active doc).
System.Cursor is the only one I know of.
I suppose you could set it after the doevents, too, but that's starting to get into the realm of kludgey hacks.
What about an API call?
Now we're getting into the realm of diminishing ROI. :-P
-Peter
Conradish - 22 Jan 2005 02:31 GMT
Yea, I suppose I could do that. I thought I better ask though, in hopes I was
missing something a lot simpler. Thanks for your help though. I did learn
about the Cursor.
> What about an API call?