We have old 3rd party programs that use the WHOHAS dwl files to warn that someone has the DWG open before running. It is not checking if the file is "locked" but only warns that someone else has it open. Crude to be sure, but has been largely effective until recently. Now we are finding inconsistent warnings when files are open read-only. It may just be coincidence, but this was not common before switching to version 2019.
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)?
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:
1) 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. (e.g. - I set my SAVETIME sysvar to 2 minutes for this test and opened 8 DWGs (read-only) at 9:00. First DWG in tablist has DWLs at 9:02. 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. [EDIT: After further testing, the "tablist" is actually the order in which the DWG files were opened. Reordering the tabs does not change the order of DWL creation.]
2) After the SAVETIME has passed, any DWLs are created immediately if they are actively viewed (by clicking on its tab) and any other ones not actively viewed are created a minute at a time going through the tab list in order (skipping the DWGs that already exist).
Yes, they are harmless temp files but this behavior does not seem to be intentional. And for purposes of actually using WHOHAS to see which files are open, this behavior seems unreliable at best.
