高级会员
注册日期: 06-11
帖子: 14579
精华: 1
现金: 224494 标准币
资产: 234494 标准币
|
【转帖】custom entities and multiple inheritance
custom entities and multiple inheritance
custom entities and multiple inheritance
i am trying to create a class combining the features of oddbpolyline with an own class of mine. i took a look at the documentation, at excustobjs example and at previous threads about custom classes. i use dwgdirect 1.14.02.
creating the new class with its constructor is straightforward, but isn't much useful since createobject must be called when creating most oddb objects. then an exception arises: i guess my own class lacks the necessary methods to work properly.
however, when i try to even implement a test createobject - say, like that found in
the problem is elsewhere... i think!
even after removing the inheritance of my own class, the problem still shows. looking back into the doc, i have noticed i stepped over the fact that odrx_dxf_define_members needs the shared library of the class to implement. dwgdirect reference, developer's guide, creating dwgdirect custom objects and applications cites (btw, notice the typo ):
quote:
note that the application name here, excustobjs, must agree with the name of the shared library that contains the implemenation for this object (excustobjs.drx in this example).
so, the new question is: can custom objects be implemented just by using shared libraries? i confess i am not much familiar with them and, in order to save time, i wish to know if i can go with a traditional approach.
thanks for your attention.
mirko pontrelli.
entity "appname" should be the same as drx name, for it to be dynamically loaded if necessary. that is - if there is a custom entity of the given type in a drawing, dd tries to load corresponding drx which will register that entity in class dictionary (by calling ::rxinit()), and will make possible further work with it. if there would be no such drx, the custom entity will be loaded as proxy, and will not be very useful.
one drx may contain code for several entities.
the differences between drx and simple dll is that it should export module definition.
look for example in "examples\excustobjs\excustobjsmodule.cpp"
please ignore anything command related, if you don't need commands.
vladimir
quote:
if there would be no such drx, the custom entity will be loaded as proxy, and will not be very useful.
yeah, but i haven't even managed to create that entity.
quote:
the differences between drx and simple dll is that it should export module definition.
although i can find tons of documentation about dlls on the internet, i can find none about drx - well, it's a photoshop tutorial extension. can you suggest a good start point, vladimir? i've never approached to libraries other that .a ones. sounds like i need to update.
just growing up.
drx is just a dll with certain symbols exported.
study the sample excustobjs, that is the only reasonable starting point. if you are not very familiar with dlls, read about them first.
vladimir
ok, got it. thanks for your support & bye!
|