I've held discussions with developers over this, and it is possible for them to install a software switch that toggles the UI between Windows and OS X styles. In Windows, all UI elements are held within a master MDI window in OS X, they can be anywhere, which I find really irritating. The user interface will most likely differ from how you are used to seeing the CAD program. Others will work, such as LISP and C-style languages, because they are not specific to Windows.ĭifferent UI. In particular, you won't get ActiveX, COM, VBA, or VSTA on OS X, because they are proprietary to Windows. Some applications programming interfaces will be missing from the CAD program, for the same two reasons as above. You will find some commands missing, and there are two reasons for this: (1) the CAD vendor didn't have time to implement all of them before shipping Version 1 of his Mac software and/or (2) the OS X operating system does not support the function, such as OLE.įewer APIs. But the majority of us are used to a locked-to-Windows CAD system, and should you switch to Mac, you'll find these differences:įewer Commands. None of this will come as a surprise to those of you who already use multi-OS CAD systems, such as ArchiCAD or Vectorworks.
(Let me get out of the way my impression of the hardware and operating system produced by Apple: both are truly dreadful.)Īnyhow, back to CAD on the Mac. If you are used to only CAD on Windows, I thought I'd give you a head's-up on what will be different. Several CAD vendors are on the verge of releasing the OS X version of their software for the Macintosh line of personal computers, and I've been able to try out some of them on a new acquired MacBook.
0 kommentar(er)
