Lying Cursor

[MikeHalloran]

2009.5.0 XP32 4Gb

Maybe it's because I'm working with big models, but I'm getting really tired of the Solidworks cursor misrepresenting what's going on.

E.g., I save a file, and the cursor changes to an hourglass.
Okay, fine, it should do that; it's busy.
A minute or two later, the cursor changes back to an arrow.
I can move it, and I can click it,
... but SW is not really ready to respond to those clicks,
... until a minute or two later.

So, why should the cursor become an arrow long before SW is actually ready to do something?


Mike Halloran
Pembroke Pines, FL, USA

 

[ctopher]

I think it is a Windows issue, not SolidWorks.
Are you saving to a server, using wireless? It could be a slow connection.

Chris
SolidWorks 09 SP4.1
ctopher's home
SolidWorks Legion

 

[MikeHalloran]

I'm saving to a server, that used to be a dedicated, isolated CAD server.

Since moving across town to headquarters, it's still dedicated to CAD, but I don't think the network is divided, e.g. by a switch, so everyone's traffic is on the same wire.

However, it doesn't seem to be traffic- sensitive; same thing occurs in the middle of the night.

Damn, now I gotta start learning about Windows.




Mike Halloran
Pembroke Pines, FL, USA

 

[MikeHalloran]

Okay, so I read up on it.

Windows handles the details of changing the cursor, but Windows does not decide when to do so; the application has to specifically call the Windows API to change the cursor to an hourglass, and call the API again to change it back to whatever it was.

So Solidworks' programmers are being, uh, optimistic in deciding when it's time to restore the cursor.



Mike Halloran
Pembroke Pines, FL, USA

 

[takedownca]

Then I guess we're stuck being pessimistic about believing the cursor.

 

[MikeHalloran]

If it were FOSS, that's what I'd do.

For commercial software, I reserve the right to bitch about stupid bugs in public.



Mike Halloran
Pembroke Pines, FL, USA

 

[007bondy]

here here

 

[SBaugh]

Been seeing it here since I have been using a 32bit system opening and saving large assemblies over the network. Seems to be a 32 bit issue. Its not happening on our 64bit machines.

Scott Baugh, CSWP

http://www.scottjbaugh.com

"If it's not broke, Don't fix it!"

faq731-376