Object DBX Customization

Is anyone interested in a developing a DBX app to manipulate drawing layers for a fee? The host app would be in VB. Email me privately if you have this expertise and you are available for some work. I will detail the requirments.

 

I am guessing the knowlege you use to write that app comes from these NG.
Do you mean to sell the prog when finished or do you mean you will pay the person for helping develop it?
Terry Dotson is the man for DBX...

LouCancilla <>
|>Is anyone interested in a developing a DBX app to manipulate drawing layers for a fee? The host app would be in VB. Email me privately if you have this expertise and you are available for some work. I will detail the requirments.
|>
|>

James Maeding
Civil Engineer/Programmer

 

Nothing against Terry, but I think "a man" is more appropriate.
There are other folks who know plenty about ObjectDBX, like Mr.
Tanzillo, Mr. Bell, Mr. Stein ...

Just an FYI, aside from not supporting commands or functions
that are application / editor based and/or user interactive based,
most properties and methods supported by the IAcadDocument interface
are supported by the IAxDbDocument interface (see listings below).
The syntax is mostly the same as for IAcadDocument. I say mostly
because there is the odd method that may take a different number
of parameters, e.g. 'SaveAs.

As for "Manipulate layers for a fee" it is a free market, but laugh
out loud, I have a hard time taking that serious, as any coder with
a semblance of activex experience could do it with nary an extra
effort once / she realizes there's no more magic than "normal"
visual lisp coding (or vb if that's your preference).

; IAcadDocument: An AutoCAD drawing
; Property values:
; Active (RO) = -1
; ActiveDimStyle = #<VLA-OBJECT IAcadDimStyle 03da9374>
; ActiveLayer = #<VLA-OBJECT IAcadLayer 03daae34>
; ActiveLayout = #<VLA-OBJECT IAcadLayout 03daab84>
; ActiveLinetype = #<VLA-OBJECT IAcadLineType 03daa964>
; ActivePViewport = AutoCAD: No active viewport in paperspace
; ActiveSelectionSet (RO) = #<VLA-OBJECT IAcadSelectionSet 03d90144>
; ActiveSpace = 1
; ActiveTextStyle = #<VLA-OBJECT IAcadTextStyle 03daa674>
; ActiveUCS = AutoCAD: Null object ID
; ActiveViewport = #<VLA-OBJECT IAcadViewport 03daa494>
; Application (RO) = #<VLA-OBJECT IAcadApplication 00b5e51c>
; Blocks (RO) = #<VLA-OBJECT IAcadBlocks 03daa624>
; Database (RO) = #<VLA-OBJECT IAcadDatabase 03db2ac4>
; Dictionaries (RO) = #<VLA-OBJECT IAcadDictionaries 03daa224>
; DimStyles (RO) = #<VLA-OBJECT IAcadDimStyles 03daa914>
; ElevationModelSpace = 0.0
; ElevationPaperSpace = 0.0
; FileDependencies (RO) = #<VLA-OBJECT IAcadFileDependencies 03db29c4>
; FullName (RO) = ""
; Groups (RO) = #<VLA-OBJECT IAcadGroups 03daa814>
; Height = 639
; HWND (RO) = 591814
; Layers (RO) = #<VLA-OBJECT IAcadLayers 03daa0b4>
; Layouts (RO) = #<VLA-OBJECT IAcadLayouts 03daa064>
; Limits = (0.0 0.0 420.0 297.0)
; Linetypes (RO) = #<VLA-OBJECT IAcadLineTypes 03dabc54>
; ModelSpace (RO) = #<VLA-OBJECT IAcadModelSpace 03daa014>
; MSpace = AutoCAD: Invalid mode
; Name (RO) = "Drawing1.dwg"
; ObjectSnapMode = 0
; PaperSpace (RO) = #<VLA-OBJECT IAcadPaperSpace 03dabe74>
; Path (RO) = "C:\\Documents and Settings\\puckettm\\My Documents"
; PickfirstSelectionSet (RO) = #<VLA-OBJECT IAcadSelectionSet 03d916d4>
; Plot (RO) = #<VLA-OBJECT IAcadPlot 03daa8ec>
; PlotConfigurations (RO) = #<VLA-OBJECT IAcadPlotConfigurations 03daba54>
; Preferences (RO) = #<VLA-OBJECT IAcadDatabasePreferences 03db29f4>
; ReadOnly (RO) = 0
; RegisteredApplications (RO) = #<VLA-OBJECT IAcadRegisteredApplications 03dab594>
; Saved (RO) = 0
; SelectionSets (RO) = #<VLA-OBJECT IAcadSelectionSets 03d90194>
; SummaryInfo (RO) = #<VLA-OBJECT IAcadSummaryInfo 03db2994>
; TextStyles (RO) = #<VLA-OBJECT IAcadTextStyles 03dabe24>
; UserCoordinateSystems (RO) = #<VLA-OBJECT IAcadUCSs 03dab2e4>
; Utility (RO) = #<VLA-OBJECT IAcadUtility 03d91264>
; Viewports (RO) = #<VLA-OBJECT IAcadViewports 03dab164>
; Views (RO) = #<VLA-OBJECT IAcadViews 03dab294>
; Width = 1026
; WindowState = 3
; WindowTitle (RO) = "Drawing1.dwg"
; Methods supported:
; Activate ()
; AuditInfo (1)
; Close (2)
; CopyObjects (3)
; EndUndoMark ()
; Export (3)
; GetVariable (1)
; HandleToObject (1)
; Import (3)
; LoadShapeFile (1)
; New (1)
; ObjectIdToObject (1)
; Open (2)
; PurgeAll ()
; Regen (1)
; Save ()
; SaveAs (3)
; SendCommand (1)
; SetVariable (2)
; StartUndoMark ()
; Wblock (2)

;========================================================================

; IAxDbDocument: IAxDbDocument Interface
; Property values:
; Application (RO) = Exception occurred
; Blocks (RO) = #<VLA-OBJECT IAcadBlocks 03dc3114>
; Database (RO) = #<VLA-OBJECT IAcadDatabase 03db9cc4>
; Dictionaries (RO) = #<VLA-OBJECT IAcadDictionaries 03dc3024>
; DimStyles (RO) = #<VLA-OBJECT IAcadDimStyles 03dc4d34>
; ElevationModelSpace = 0.0
; ElevationPaperSpace = 0.0
; FileDependencies (RO) = #<VLA-OBJECT IAcadFileDependencies 03db9c64>
; Groups (RO) = #<VLA-OBJECT IAcadGroups 03dc4e44>
; Layers (RO) = #<VLA-OBJECT IAcadLayers 03dc4c14>
; Layouts (RO) = #<VLA-OBJECT IAcadLayouts 03dc4944>
; Limits = (0.0 0.0 420.0 297.0)
; Linetypes (RO) = #<VLA-OBJECT IAcadLineTypes 03dc4734>
; ModelSpace (RO) = #<VLA-OBJECT IAcadModelSpace 03dc48f4>
; Name = "c:\\crud.dwg"
; PaperSpace (RO) = #<VLA-OBJECT IAcadPaperSpace 03dc44b4>
; PlotConfigurations (RO) = #<VLA-OBJECT IAcadPlotConfigurations 03dc4394>
; Preferences (RO) = #<VLA-OBJECT IAcadDatabasePreferences 03db9c94>
; RegisteredApplications (RO) = #<VLA-OBJECT IAcadRegisteredApplications 03dc42d4>
; SummaryInfo (RO) = #<VLA-OBJECT IAcadSummaryInfo 03db9c34>
; TextStyles (RO) = #<VLA-OBJECT IAcadTextStyles 03dc5e74>
; UserCoordinateSystems (RO) = #<VLA-OBJECT IAcadUCSs 03dc5d94>
; Viewports (RO) = #<VLA-OBJECT IAcadViewports 03dc4044>
; Views (RO) = #<VLA-OBJECT IAcadViews 03dc45a4>
; Methods supported:
; CopyObjects (3)
; DxfIn (2)
; DxfOut (3)
; HandleToObject (1)
; ObjectIdToObject (1)
; Open (2)
; Save ()
; SaveAs (2)

privately if you have this expertise and you are available for some work. I will detail the requirments.

 

yep, if you know the object model, dbx is nothing special. I better take down that picture of Terry from my wall.
Only problem is I dont know what Tony or Robert or the others look like...

Just make sure you register the dll needed to do DBX stuff.
See other threads on this.

It sounds like Lou wants to hire someone to do it.
We are so used to people asking for free stuff that we just get confused when you offer to pay.
Problem is those that know it learned from the NG's anyway...

"michael puckett" <>
|>Nothing against Terry, but I think "a man" is more appropriate.
|>There are other folks who know plenty about ObjectDBX, like Mr.
|>Tanzillo, Mr. Bell, Mr. Stein ...
|>
|>Just an FYI, aside from not supporting commands or functions
|>that are application / editor based and/or user interactive based,
|>most properties and methods supported by the IAcadDocument interface
|>are supported by the IAxDbDocument interface (see listings below).
|>The syntax is mostly the same as for IAcadDocument. I say mostly
|>because there is the odd method that may take a different number
|>of parameters, e.g. 'SaveAs.
|>
|>As for "Manipulate layers for a fee" it is a free market, but laugh
|>out loud, I have a hard time taking that serious, as any coder with
|>a semblance of activex experience could do it with nary an extra
|>effort once / she realizes there's no more magic than "normal"
|>visual lisp coding (or vb if that's your preference).


James Maeding
Civil Engineer/Programmer

 

Excuse me Michael, but I think your comments serve to
demonstrate that you are not all that familiar with
ObjectDBX ActiveX programming.

ActiveX programmers who are limited to that API, are
not able to do the job properly.

For example, if they save the drawing, they loose the
thumbnail bitmap. If they change text that does not
have the default justification, the text is incorrectly
positioned the next time it is plotted or opened in the
editor, and requires an explicit update to fix it. You
can't save an AxDbDocument to any .DWG file version other
than the native version of the AutoCAD release you're
accessing it through.

These are only a few of the problems (there are others
but it would take more time than I can devote to get
into them in detail).

Fortunately, my solutions suffer from none of this.

--
http://www.caddzone.com

AutoCAD based Security Planning Solutions:
http://www.caddzone.com/securityplanning

AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005
http://www.acadxtabs.com

 

Good evening Tony,

There are certainly some shortcomings in the ObjectDBX
object model and it is good that you raise some of these
issues and limitations.

However, within the vanilla product lies a vast sea of
possibility and productivity you are dismissing. For
example, many folks use the technology as a POWERFUL
scanning and reporting engine, and as such, thumbnails etc.
are of moot want or concern.

Of course, you know this, but pretend to know precisely how
I and others use the technology, suggesting we could not
possibly be productive, or "Code Complete" without using
your add-on products, which incidentally are not free,
correct?

Well sorry Tony, I know this will be difficult for you to
accept, but you simply assume too much and are mistaken. I
use ObjectDBX on a daily basis and am very pleased with the
results I am achieving, processing drawings in the thousands
with each run.

While you are free to use this thread as a thinly veiled
opportunity to pump your products, it is amusing that you
think anyone with functioning grey matter will equate a post
that fails to provide an encyclopedic listing of the
differences between the two noted document models as a
testimonial that the author of the post is "not all that
familiar with ObjectDBX ActiveX programming".

*Right*.

I suppose this is where I'm supposed to lash out in response
but I simply don't see how that benefits anyone, so:

"Cheers, I hope you enjoyed the game, I sure did"

!!! WOO HOO !!! GO FLAMES GO !!!

 

Forgive / ignore if you can, my previous post in this thread
(which I tried to delete unsuccessfully). Full of Flames bravado,
and of myself, I answered from my ego; I should never do that.
Thank you for the information.

 

without using your add-on products, which incidentally

Correct!

It is the simple, undeniable fact that my tools allow
one to achive things that are entirely beyond the reach
of the average ActiveX programmer, that is what gives
them their value.

I can understand why you would jump to that conclusion,
given that it is your own lack of understanding of those
problems, that prevents you from realizing that my product
does not solve all of them (I have other tools that are not
publicly available, that does solve all of them however).

For this particular request (which obviously is not
a read-only application), the limitations that I
raised are something that the customer should not
have to accept under any circumstance, or simply
because someone doesn't know how to use the right API,
or because they view the need to license third party
tools like those I offer, as beneath them.

In case you didn't know this, it was I who first
discovered and disclosed the existence of ObjectDBX
ActiveX, and demonstrated how to use it. At that point,
it was completely unknown and undocumented, to even
most at Autodesk (who had no intention of documenting
or disclosing it), never mind you, or others mentioned
in this thread.

The satisfying part of this, is the solace I take in
knowing that unlike yourself, I will never have to tell
those who I am solving problems for, that in order to
enjoy the benefits of ObjectDBX, they will have to loose
their thumbnails, or endure various other detrimental
effects caused by limitations of ObjectDBX ActiveX, some
of which you aren't aware of.


--
http://www.caddzone.com

AutoCAD based Security Planning Solutions:
http://www.caddzone.com/securityplanning

AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005
http://www.acadxtabs.com

 

Wow!, excuse me, but was that English?#*....

I think I just entered the 'Verbal Zone'. dododdoddo.....

 

Tony, you must realize it takes a lot of time to investigate how to use your stuff, I have only seen some and decided
the drawbacks of generic dbx in lisp or VB were not a big deal.
People that just need info from the drawing can go a long ways without your tools.
Having said that, the stuff I enjoy the most is when someone extends the power of our environment.
We need to hear where we are "settling" and could be going further so keep the rebuttals going.
I'm sure Michael was just standing some ground which we all do but with eyes open for learning opportunities...

One thing, are we missing the boat by using generic ObjectDBX? Are you saying the real power is in the version that
does not require acad?

"michael puckett" <>
|>Forgive / ignore if you can, my previous post in this thread
|>(which I tried to delete unsuccessfully). Full of Flames bravado,
|>and of myself, I answered from my ego; I should never do that.
|>Thank you for the information.
|>
|>
|>> Excuse me Michael, but I think your comments ...
|>

James Maeding
Civil Engineer/Programmer

 

That's your misconception or limitation. Many licensees
of my 'stuff' have no such problems figuring out how
to use it, and they can email me anytime they need a
clarification or example.

That depends on your standards. I charge people money
for solutions. I would look pretty dumb if I did that,
and told them that they had to accept such rediculous
limitations, and consider any notion to the contrary,
highly unprofessional.

So, it depends on whether one is interested in taking
all the credit for the solutions they deliver, verses
delivering the best possible solutions. You point of
view appears to be designed to serve the former, not
the latter.

--
http://www.caddzone.com

AutoCAD based Security Planning Solutions:
http://www.caddzone.com/securityplanning

AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005
http://www.acadxtabs.com

 

Situations where you just need info from a drawing work just fine with generic dbx calls.
Now that my neck is out, feel free to chop it since I have not done extensive dbx programming <g>.
I have, however, inspected the objects available when doing these progs and I use activex type calls in other progs a
lot.
Feel free to point out areas your tools extend this though.

On the credit subject, I am not interested in credit, just making slick tools.
When I say a drawback is not a big deal, its because that drawback did not affect me at all.
I do go the extra mile when quality is at stake.
You have to admit though, if you are offering powerful tools, they will take time and thinking to investigate and use.
You are providing solutions for picking apples high on the tree and many people are not there yet.
I thought your stuff was easy to understand, I just have too many other things going to do a lot of dbx requiring tools.
thx

"Tony Tanzillo" <>
|>
|>> Tony, you must realize it takes a lot of time to
|>> investigate how to use your stuff.
|>
|>That's your misconception or limitation. Many licensees
|>of my 'stuff' have no such problems figuring out how
|>to use it, and they can email me anytime they need a
|>clarification or example.
|>
|>> I have only seen some and decided the drawbacks of
|>> generic dbx in lisp or VB were not a big deal.
|>
|>That depends on your standards. I charge people money
|>for solutions. I would look pretty dumb if I did that,
|>and told them that they had to accept such rediculous
|>limitations, and consider any notion to the contrary,
|>highly unprofessional.
|>
|>So, it depends on whether one is interested in taking
|>all the credit for the solutions they deliver, verses
|>delivering the best possible solutions. You point of
|>view appears to be designed to serve the former, not
|>the latter.

James Maeding
Civil Engineer/Programmer