Second DWLs created at 9:03, third at 9:04.last at 9:09.) This was without changing the drawing tab of the DWG I was actively viewing. I set my SAVETIME sysvar to 2 minutes for this test and opened 8 DWGs (read-only) at 9:00. I say other condition because additional testing of these files also indicates that if someone opens a series of DWGs all at once, a couple different results are possible:ġ) If the DWGS tabs are not actually viewed, the first DWG in the tab list creates DWLs after the SAVETIME has elapsed, the other DWGs each take an additional minute to be created. If this is as intended, we'll deal with it accordingly but beyond that, wouldn't it seem like unexpected behavior if the DWL files are NOT created upon opening read-only but only after an autosave (or other condition)? It may just be coincidence, but this was not common before switching to version 2019. Now we are finding inconsistent warnings when files are open read-only. Crude to be sure, but has been largely effective until recently. It is not checking if the file is "locked" but only warns that someone else has it open. We have old 3rd party programs that use the WHOHAS dwl files to warn that someone has the DWG open before running.
I noticed posts at other forums where other users may have experienced files mysteriously locking but all solutions seem to point to a network connectivity (or other glitch) and had not mentioned anything regarding Autosave or SAVETIME settings. Is this as intended? This behavior does create a problem when multiple users are trying to use the same file, even if one is only viewing it but also has it open for some time beyond our standard SAVETIME setting. ", the dwl file pair shows up on the network, even though it is open as read-only. We tested on multiple machines and it happens without exception: as soon as the command line echos an "Automatic save to. Has anyone had similar experience with this?Ī little testing has shown that both dwl files (dwl and dwl2) are not created when the DWG is initially opened, however after the autosave time has lapsed (in accordance with the SAVETIME system variable setting), the files are created, even though the user is still only viewing as read-only.
I looked at some older forum posts and found similar dwl file problems (with and without solutions) but none seem to fit my scenario: We recently started to notice problems with the dwl2 files (and dwl files as well) showing up on our network when the DWGs are opened as read-only, but only after an autosave has passed.
0 kommentar(er)
