It’s easy to say 12% of computers are macs … “what about the rest of us 88% windows users aren’t we more important?” this isn’t a measuring contest, but if it were wouldn’t the more accurate comparison be _% Dell _% HP _% Acer _% Apple. don’t make the mistake of underestimating how many designers use macs. there is an often dismissed group of users that are able to get every other piece of software on the mac EXEpt Autodesk. pc’s are here for good, and those who prefer shouldn’t switch. No one is asking for anyone to jump ship. changes of the sort that would break binary compatibility for ObjectARX applications), therefore one could reasonably conclude that no full-blown Mac port is imminent. It’s also clear that the Mac build still has limitations, and some of these limitations might require significant changes (i.e. It’s clear from the type, quantity, and quality of changes that Autodesk has successfully built at least a limited AutoCAD executable for OS X (both 32 and 64 bit).
In this case, we do want to export the AcEdInputPoint symbol attributes to exclude symbols we don’t want to export. On OS X, we will export all symbols by default and will use GCC #if defined(_WINDEF_) || defined(_ADESK_MAC_)Īnd in acedinpt.h there’s a telling comment: The evidence comes in the form of code comments and changes made to the files so that they work with the GCC compiler and the Mac OS X libraries.įor example, acedads.h conditionally declares a global function to return the main window handle as follows: The ObjectARX 2011 SDK header files contain clear evidence of a native Mac port in the works. There have been rumblings and rumors for a while now about a native Mac OS X port of AutoCAD.
0 kommentar(er)
