Delayed update? Or screen refresh? Or, what?
Delayed update? Or screen refresh? Or, what?
(OP)
Using SW2007 to read some files produced by older versions, I noticed something that seemed odd. Okay, it scared the crap out of me. I thought I had unintentionally updated the old files, possibly making them unreadable by co-workers. In my third week on the job. Not an auspicous start.
The dialog went something like this:
>File|Open|A.sldxx
>Opening A.sldxx
>File|Close
>Do you want to update A.sldxx?
No.
>Closing A.sldxx
>File|Open|B.sldxx
>Opening B.sldxx
>File|Close
>Do you want to update B.sldxx?
No.
>Closing B.sldxx
>Updating A.sldxx <<<< Yikes! (No cancel button, either!)
... and so on.
I'm a little fuzzy on the details, but the message about updating a file that I thought had already been safely closed, appeared at a time that made no sense whatsoever, but the behavior was consistent.
Later, I checked the dates on the old files; still old.
Now, I'm thinking maybe the Updating window was actually generated _before_ the dialog asking for permission to do so, and not erased when it should have been. I.e., all transactions for file B occluded a zombie window from file A, which became visible when B's real window closed. Or, something else.
Does this ring a bell for anyone?
The dialog went something like this:
>File|Open|A.sldxx
>Opening A.sldxx
>File|Close
>Do you want to update A.sldxx?
No.
>Closing A.sldxx
>File|Open|B.sldxx
>Opening B.sldxx
>File|Close
>Do you want to update B.sldxx?
No.
>Closing B.sldxx
>Updating A.sldxx <<<< Yikes! (No cancel button, either!)
... and so on.
I'm a little fuzzy on the details, but the message about updating a file that I thought had already been safely closed, appeared at a time that made no sense whatsoever, but the behavior was consistent.
Later, I checked the dates on the old files; still old.
Now, I'm thinking maybe the Updating window was actually generated _before_ the dialog asking for permission to do so, and not erased when it should have been. I.e., all transactions for file B occluded a zombie window from file A, which became visible when B's real window closed. Or, something else.
Does this ring a bell for anyone?
Mike Halloran
Pembroke Pines, FL, USA






RE: Delayed update? Or screen refresh? Or, what?
Jeff Mowry
www.industrialdesignhaus.com
Reason trumps all. And awe transcends reason.
RE: Delayed update? Or screen refresh? Or, what?
When a new version of SolidWorks is installed, all the SW files should be updated/converted using the Conversion Wizard before they are opened with the new version. It will speed up opening and saving times considerably and will preclude the messages you have been seeing.
A copy of all the files should be made before converting, or they can be made during the conversion process.
RE: Delayed update? Or screen refresh? Or, what?
Mike Halloran
Pembroke Pines, FL, USA
RE: Delayed update? Or screen refresh? Or, what?
RE: Delayed update? Or screen refresh? Or, what?
No, I haven't posted to every forum. That last time I counted, it was 104. I used to participate regularly in 170 forums on Compuserve, but that's not possible since it went to HTML. I'm not sure it even has that many forums in its current dehydrated state.
Yeah, it looks like I'll be here from time to time. SW does some really cool stuff ... and it does some really strange stuff, too, at least for me.
Mike Halloran
Pembroke Pines, FL, USA