Author Topic: ARX, DBX sharing classes  (Read 1887 times)

0 Members and 1 Guest are viewing this topic.

It's Alive!

  • BricsCAD
  • Needs a day job
  • Posts: 7033
  • AKA Daniel
ARX, DBX sharing classes
« on: April 27, 2009, 05:38:22 AM »

I have a couple of classed that both my DBX and ARX modules need to reference, is there any problem with me putting the classes in the DBX? Or should I just create a library  :mrgreen:

MickD

  • Gator
  • Posts: 3420
  • (x-in)->[process]->(y-out)
Re: ARX, DBX sharing classes
« Reply #1 on: April 27, 2009, 06:06:38 AM »
I don't think it matters that much but generally custom object class def's and your class functions such as world draw and file in/out will be in the dbx and your custom editing (or UI) of the entity code will be in your arx...so, if the classes are only to help the UI I'd put them in the arx.
hth
Forth is like the Tao: it is a Way, and is realized when followed.
Its fragility is its strength; its simplicity is its direction - Michael Ham

Lao Tzu: To attain knowledge, add things
every day; to obtain wisdom, remove things every day.

It's Alive!

  • BricsCAD
  • Needs a day job
  • Posts: 7033
  • AKA Daniel
Re: ARX, DBX sharing classes
« Reply #2 on: April 27, 2009, 06:12:31 AM »
Thanks Mick

Im going to try making static lib to put all the classes that both modules need, Im trying to avoid circular references

MickD

  • Gator
  • Posts: 3420
  • (x-in)->[process]->(y-out)
Re: ARX, DBX sharing classes
« Reply #3 on: April 27, 2009, 06:27:17 AM »
If they are helper classes to be used in both that sounds like the go :)
Forth is like the Tao: it is a Way, and is realized when followed.
Its fragility is its strength; its simplicity is its direction - Michael Ham

Lao Tzu: To attain knowledge, add things
every day; to obtain wisdom, remove things every day.

It's Alive!

  • BricsCAD
  • Needs a day job
  • Posts: 7033
  • AKA Daniel
Re: ARX, DBX sharing classes
« Reply #4 on: April 27, 2009, 09:49:20 PM »
Ok, the static library works great, kind of weird getting all the projects to build in the right order.
Once I figured out how to use Visual Studios property sheets, it was a snap to get all the paths setup


edit: Here is a link on using property sheets
http://msdn.microsoft.com/en-us/library/a4xbdz1e(VS.80).aspx
« Last Edit: April 27, 2009, 09:53:31 PM by Daniel »