Jason,
I put a copy of the paper here:
www.globaldialog.com\~jroderick\CP21-3.zip
The c: issue is explained in the help file:
"There are two similar styles that can be used to program AutoLisp code to
handle the ObjectDCL events. But first, to answer a question some of you
may have, you will notice that ObjectDCL calls its events as C:xxx defun'd
functions. This is done because of the limitation ObjectARX imposes on
mechanisms to call AutoLisp functions from some ObjectARX dialog boxes.
Rather then setup ObjectDCL to defun some events as C:xxx and others as xxx,
C:xxx is used as the standard. The first programming style defines all the
event defun's inside the main defun. This allows the program to be created
free of global variables. The second style allows global variables to be
used instead to organize information between the main defun and the event
defun's."
If you look at my example in the AU paper, I actually localize the event
c:defuns. I tend to be anal about stuff like this ;)
When I was doing the CDG thing, I used ObjectDCL for CDGPurge. Since I have
dropped the website I have been thinking of just releasing the code as an
ObjectDCL example and letting people have fun with it.
HTH,
Joel
"Jason Piercey" wrote in message
news:412e48be_1@newsprd01...
> Hi Joel,
>
> I'd like to take a look at it, if you don't mind.
>
> Off the top of my head, some trouble I had with it
> was lack of documentation, and why on earth you
> need *all* of your functions defined like a command
> (with the c: prefix) That just doesn't make any
> sense to me.
>
> Thanks for the offer.
>
> --
> Autodesk Discussion Group Facilitator
>
>
> "Joel Roderick" wrote in message
> news:412e4453_1@newsprd01...
> > Jason,
> > You may find the AU class material I did to be useful. It walks you
> through
> > step by step on creating a project. Not sure if they still have them up
> on
> > the website, so if you need it, let me know.
> >
> > Joel Roderick
>
>