I see now. There is such a thing as a persistent reference, which you can
tie to an object using vba. Once this was done, then possibly a start-up
routine could look at these references and if something has changed between
the objects, then code could run. I don't have much experience with this
sort of thing, I've only played around with the persistent references out of
curiosity. Without knowing exactly what sorts of things you want to
accomplish, I can't offer much more than that. I would be interested in
hearing more about your project though, feel free to post add'l info and
some minds greater than mine might see a clear path for you.
Kevin
"markP" wrote in message
news:8F98B6B4DC8BCB3A7162BA074DAC876B@in.WebX.maYIadrTaRb...
Kevin,
a persistent event is apparently a figment of my imagination per the above
replies to my orig. post.
Since you're offering to help I assume you know what an event is. ie attach
an event to an object.
The 'persistence' issue is that I would like that event to remain connected
to that object after the dwg is saved, closed, and reopened.
Which vba events do not do.
The corollary to lisp is that there is a thing called a reactor in lisp
which is basically what is called an event in vba, i.e. attach a routine to
an object and specify a condition which if it occurs to that object, should
call that function. These reactors also disappear on closing of the dwg
except there is an option to make them persistent which option does not seem
to exist for events in vba.
My original idea for a workaround (see re: post "How to make events
persistent" mar 6) was to save entity data in ldata, xdata, or dictionary
and then reattach events each time dwg was opened. I thought it was
probably another of my many dumb ideas until it was re-iterated by Mike
Weaver in this thread and commended by Henk afterwards, so maybe it's not so
dumb.
Now to figure out how to do it....
Or more to the point, if it's so convoluted to have to do such a simple
thing in vba, am I embarking down the wrong road by trying to learn vba as
preparation for writing a routine to use in my work which will be around two
years in the writing (given my slow learning abilities) and which will
necessitate much saving of information on possibly many objects in the
drawing and many various events or reactions necessary???
Should I be learning objectarx instead??/
I tried starting to learn c++ in preparation to learning Objectarx a couple
years ago and am still trying to get through the second book and have not
even begun to write c++ routines yet, it's soooo deep to my shallow mind!!!
Any help appreciated,
Thanks
Mark
Kevin Terry wrote in message
news:04833F67E6EA5E2CFD7448144DF91B45@in.WebX.maYIadrTaRb...
> Maybe you can help those of us completely vacant in lisp understand a
little
> more so possibly we can help you - can you explain a little what a
> persistent event is? Like, what does it do?
>
