Topic: Problem with OBJECTDBX and locked files.

[roy_043]

I am running into an issue with OBJECTDBX and locked drawings (because they are opened by a different user or in another instance of BricsCAD).

My problem is that:

Code: [Select]

(vla-open odbxObject fileName)Does not produce an error. Which seems strange to me. Maybe this is a BricsCAD issue?
And:

Code: [Select]

(= (strcase (vla-get-name odbxObject)) fileName)Returns T.

But the locked drawing has in fact not been opened. The limits are wrong and only layer "0" exists. Apart from the name it seems that the open drawing is the ODBX 'default' drawing.

How can I avoid this confusing situation?

[Bhull1985]

AutoCAD uses the DWL file extension to handle all of this, what's brisCADs alternate version of this system?
If there's nothing......pretty huge oversight.

[roy_043]

To clarify: You cannot open a locked file in BricsCAD for editing. I don't know how this is accomplished but I am unaware of .dwl files. And as I have mentioned in my first post: The locked file is in fact not opened, it only appears that way.

[roy_043]

A workaround to check for this issue:

Code: [Select]

(/= (vla-get-lastsavedby (vla-get-summaryinfo odbxObject)) "")Not very reliable as you can use (vla-set-lastsavedby).

[Bhull1985]

(because they are opened by a different user or in another instance of BricsCAD).

But the locked drawing has in fact not been opened.

Not trying to be a pain but I think that's somewhat contradictory with what your latest post said.
Autodesk does the DWL method to make sure that you cannot rename a file that's in use or whatnot.
Also it's easy to tell who's working on what if you track these dwl files

[Marc'Antonio Alessi]

I am running into an issue with OBJECTDBX and locked drawings (because they are opened by a different user or in another instance of BricsCAD).

My problem is that:

Code: [Select]

(vla-open odbxObject fileName)Does not produce an error. Which seems strange to me. Maybe this is a BricsCAD issue?
And:

Code: [Select]

(= (strcase (vla-get-name odbxObject)) fileName)Returns T.

But the locked drawing has in fact not been opened. The limits are wrong and only layer "0" exists. Apart from the name it seems that the open drawing is the ODBX 'default' drawing.

How can I avoid this confusing situation?

Maybe:
(vl-catch-all-error-p (vl-catch-all-apply 'vla-Open (list odbxObject fileName)))

[roy_043]

@ Bhull1985:
I don't see any contradictions. Note: I am talking about opening a dwg using OBJECTDBX.

@ Marc'Antonio Alessi:
The problem is that there is no error to catch.

[Bhull1985]

And as I have mentioned in my first post: The locked file is in fact not opened, it only appears that way.

"(because they are opened by a different user or in another instance of BricsCAD)."

[MP]

Pseudo code solution:

if file file can be opened for append:
    close file
    open via objectdbx
else:
    copy file to temp folder
    open via objectdbx
    flag in doc's dictionary as temp file copy

[Patrick_35]

Hi

Try this

Code: [Select]

(defun its_ok(file / dwg)
  (and (findfile file)
       (setq dwg (open file "a"))
    (not (close dwg))
  )
)

(its_ok "c:/test/drawing.dwg")
ps : Time to write and test the example and the response arrives

@+

[Marc'Antonio Alessi]

My tests with Bricscad V14 - DOSLib 9.0.1:

Code: [Select]

>>> File opened in Bricscad and NOT read only
: (DOS_FILE "C:\\Temp\\pippo.dwg")
("pippo.dwg" 350357 2.01402e+007 8)
: (DOS_OPENP "C:\\Temp\\pippo.dwg")
T
: (vl-file-systime "C:\\Temp\\pippo.dwg")
(2014 2 4 6 17 8 19 0)
: (its_ok "C:\\Temp\\pippo.dwg")
nil


>>> File read only and NOT opened in Bricscad
: (DOS_FILE "C:\\Temp\\pippo.dwg")
("pippo.dwg" 300352 2.01402e+007 9)
: (DOS_OPENP "C:\\Temp\\pippo.dwg")
nil
: (vl-file-systime "C:\\Temp\\pippo.dwg")
(2014 2 4 6 17 8 53 0)
: (its_ok "C:\\Temp\\pippo.dwg")
nil


>>> File read only NOT and NOT opened in Bricscad
: (its_ok "C:\\Temp\\pippo.dwg")
T


[roy_043]

@ Bhull1985:
OK:
"(because they have been opened by a different user or in another instance of BricsCAD)"
Would have been better linguistically.

@ MP and Patrick_35:
Thank you, that solution works.

@ Marc'Antonio Alessi:
The drawings in my tests are not read only if they have not been opened in BricsCAD.

[roy_043]

There was indeed a problem with BricsCAD. This has been fixed in version 14.2.06:

SR44023 - LISP: opening a locked or invalid drawing file did not trigger a Lisp error. Applications should use (vl-catch-all-apply) when using the "Open" method on an ObjectDbx object.

[Lee Mac]

There was indeed a problem with BricsCAD. This has been fixed in version 14.2.06:

SR44023 - LISP: opening a locked or invalid drawing file did not trigger a Lisp error. Applications should use (vl-catch-all-apply) when using the "Open" method on an ObjectDbx object.

The BricsCAD support never ceases to amaze me 

[roy_043]

The BricsCAD support never ceases to amaze me 

1+
BricsCAD support is exemplary.

[Marc'Antonio Alessi]

There was indeed a problem with BricsCAD. This has been fixed in version 14.2.06:

SR44023 - LISP: opening a locked or invalid drawing file did not trigger a Lisp error. Applications should use (vl-catch-all-apply) when using the "Open" method on an ObjectDbx object.

The BricsCAD support never ceases to amaze me 

1+