Lee you legend you seem to answer practically everything I ask.
What about creating objects though? Will the functions you mention be able to create and use external (non-autocad) COM objects - either in process or out?
Are you sure ALL the vl-* functions work irrespective of the system? What about functions such as vl-file-copy? Are all of them implemented directly in C++ without referencing any system libraries - if so how would they interoperate with system security?
what about the vlax-ldata-* functions? Do these really use ActiveX - all they do is work on dictionary objects inside the DWG..
Anyhow, the acid-test would be to actually try them on a mac..
Hi,
I'm surprised the vl-registry* functions work on Mac, as far as I know there's no registry on Mac OS.
Anyhow, the acid-test would be to actually try them on a mac (or for that matter BCad on Linux) to see if they work or not.Bricscad is introducing a system called Fast-Com to by-pass the com-dependency of lisp functions. Their goal is to implement the VL* functions in Bricscad for Linux and Mac. Because there are (speed) advantages to Fast-Com, this system is also being used in Bricscad for Windows. I don't know to what extent this project is finished, but Fast-Com was introduced during the V12 life-cycle.
Even the V11 worked on LinuxIt may actually be the case that Fast-Com was introduced earlier. I checked for the presence of the (lisp$enablefastcom) function (available in V12.2.18 but not in V11) and just assumed from this that Fast-Com was introduced in V12.