| 2010-07-29 08:04 | #1 | |
|---|---|---|
Hennie Maartens | Hello all I'm new here, considering migrating to Brics due to overwhelming sales hype. Before I download over 90 megs of trial version, maybe this forum can be of assistance. First, how is the menu file structured: similar to Autocad namely a simple ASCII file which can easily be be customised I hope ? Second, how successful is the lisp interpreter. I have over 3 decades of lisp development. I need to know if lisp code has to be reworked or not. Please make me privvy to the collective forum wisdom. Thanks | |
| 2010-07-29 08:19 | #2 | |
Vaidas Guogis | Hello Hennie, I'm using the same MNU file for Bricscad and AutoCAD. Generally LISP works without changes. In my codes I made only minor updates for DCL management and Text calling commands. Also, LISP engine in Bricscad is quite faster and I hope you truly will enjoy about porting. | |
| 2010-07-29 21:09 | #3 | |
John Gaunt | I migrated in 1998 and I can echo Vaidas' comments at that time, I have not been near Acad since to personally find any differences. A number of minor changes have been made in line with changes in Acad (like "per" instead of "perp") which can mislead someone coming from an earlier Acad version - these are basically only mirroring differences between Acad versions and sometimes don't make much sense. I don't blame Bcad for that. They use the same menu structure. Literature (in both, I believe) tends to direct the user toward using the in-built editing method which works on the CUI file initially created from the MNU file. Bcad (originally Intellicad) had a previous version of the same process using files with ICM extention IIRC. Because the migration was not pretty I went back to using and editing the MNU as, I believe, many Acad users still do. Actually I now use the factory menu and append my own MNU - too hard merging internal customisations with possible changes in the factory menu. MNU has been the constant right from the original Acad. | |


