.NET
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Documentation on DBX?

9 REPLIES 9
Reply
Message 1 of 10
Anonymous
597 Views, 9 Replies

Documentation on DBX?

Is there any examples / documentation on ObjectDBX.
This is the technology that allows you to edit multiple files without
opening them?


--
Dave
9 REPLIES 9
Message 2 of 10
Anonymous
in reply to: Anonymous

No, its undocumented. The only place to find info if you're not in ADN is
either this ng, or the vba ng.

--
----
Ed
----
Message 3 of 10
Anonymous
in reply to: Anonymous

bummer
So for object dbx should it be done in VBA or .net?

--
Dave

"Ed Jobe" wrote in message
news:5221509@discussion.autodesk.com...
No, its undocumented. The only place to find info if you're not in ADN is
either this ng, or the vba ng.

--
----
Ed
----
Message 4 of 10
Anonymous
in reply to: Anonymous

dbx is not going to dictate that, your needs will.

--
----
Ed
----
Message 5 of 10
Anonymous
in reply to: Anonymous

explain more please

--
Dave

"Ed Jobe" wrote in message
news:5221880@discussion.autodesk.com...
dbx is not going to dictate that, your needs will.

--
----
Ed
----
Message 6 of 10
Anonymous
in reply to: Anonymous

e.g. your developer only wants to use .net. Since ObjectDBX will work in
either, you get to choose based upon your project needs.

--
----
Ed
----
Message 7 of 10
Anonymous
in reply to: Anonymous

Since RealDWG (the new name for ObjectDBX) is pretty much a subset of
ObjectARX, the ObjectARX docs should work for most items. The stuff that
won't be documented is things like creating your own application host to
interact with ObjectDBX.

By and large, you should be able to use RealDWG from either classic C++ or
.NET (using the wrapper assemblies and objects). Note that RealDWG must be
licensed from Autodesk.

If you're satisfied running your application to "edit multiple files without
opening them" from inside of AutoCAD (e.g., ARX/LOAD or NETLOAD), then you
don't need RealDWG.

Dan

"Ed Jobe" wrote in message
news:5221509@discussion.autodesk.com...
No, its undocumented. The only place to find info if you're not in ADN is
either this ng, or the vba ng.

--
----
Ed
----
Message 8 of 10
Anonymous
in reply to: Anonymous

I've been utilizing ObjectDBX via AutoLISP since R2002. What do you want to
know?
Message 9 of 10
Anonymous
in reply to: Anonymous

Well for example I have 2 projects in mind.
One is a xref renamer.
Scan a project including all subfolders and find all the references to a
drawing.
Then rename that drawing and have the program update all the sheets to the
new name.
The xref manager works nice for paths, but not .dwg names.
It could run inside autocad, doesn't matter to me.

Another application would be to take every drawing on a drive and do a
search and replace.
Say all your drawings were under F:\Job and you wanted to move everything to
P:\Project.
Using the reference manager would take months. I'm thinking of a ObjectDBX
application could
do this in hours if it could scan an entire drive.

One big problem with my company is each office uses different drive letters.
We expand our company
by purchasing companies. When we take over we allow the purchased company
to continue with their
existing server structure and standards. This makes collobration between
offices a huge problem.

These are just 2 examples.

I have a grasp of lisp but my developer wants to only work in dotnet because
its new and cool. So I need
to learn how to talk dotnet. I have no desiger to be a coder but I need to
direct him in what I want done.

--
Dave

"James Buzbee" wrote in message
news:5222302@discussion.autodesk.com...
I've been utilizing ObjectDBX via AutoLISP since R2002. What do you want to
know?
Message 10 of 10
Anonymous
in reply to: Anonymous

A simple (vlax-dump-object ..) from AutoLISP reveals all Properties and
Methods available:

; IAxDbDocument: IAxDbDocument Interface
; Property values:
; Application (RO) = Exception occurred
; Blocks (RO) = #
; Database (RO) = #
; Dictionaries (RO) = #
; DimStyles (RO) = #
; ElevationModelSpace = 0.0
; ElevationPaperSpace = 0.0
; FileDependencies (RO) = #
; Groups (RO) = #
; Layers (RO) = #
; Layouts (RO) = #
; Limits = (0.0 0.0 12.0 9.0)
; Linetypes (RO) = #
; ModelSpace (RO) = #
; Name = "S:\\KB Styles\\KB-Layers.dwg"
; PaperSpace (RO) = #
; PlotConfigurations (RO) = #
; Preferences (RO) = #
; RegisteredApplications (RO) = #
10c72904>
; SummaryInfo (RO) = #
; TextStyles (RO) = #
; UserCoordinateSystems (RO) = #
; Viewports (RO) = #
; Views (RO) = #
; Methods supported:
; CopyObjects (3)
; DxfIn (2)
; DxfOut (3)
; HandleToObject (1)
; ObjectIdToObject (1)
; Open (2)
; Save ()
; SaveAs (2)


As you can see, pretty much everything is availble as if the document was
opened by AutoCAD. So your XREF program could easily access the Blocks
collection and revise saved paths easily. Your programmer should easily be
able to convert AutoCAD VBA into VB.NET - I mean if I could write a similar
program in plain AutoLISP then surely the mighty DON NET won't be a problem!

jb

Can't find what you're looking for? Ask the community or share your knowledge.

Post to forums  

Autodesk DevCon in Munich May 28-29th


Autodesk Design & Make Report

”Boost