![]() Did you know that BricsCAD for Mac users can thank a far-sighted early 90s Autodesk OS/2 team for the dialog boxes they use today? BLADE is better for DCL programming, too.Įven if you’re AutoCAD-only and not a programmer, you might find my brief ancient history lesson of interest. Again, even if you’re AutoCAD-only, I believe this is worth a watch. I have another appearance scheduled for later today (13 February) in which among other LISPy things, I will be discussing using BLADE for DCL programming. ![]() It’s the best development environment for AutoLISP/Visual LISP that you’re ever going to get. If you’re dealing with LISP code for AutoCAD and/or BricsCAD, you really should be doing it in BLADE. I made another appearance last week describing debugging using BLADE ( YouTube link): Torsten Moses has informed me about yet another bunch of enhancements that are coming very soon to BLADE, so maybe you haven’t heard the last from me on this subject on BricsCAD Unplugged.Īs mentioned previously, In December I made a guest appearance on the BricsCAD Unplugged webcast series to discuss the LISP development environment, BLADE ( YouTube link). It has been an absolute pleasure working with the Bricsys people in putting this series together. If you want to watch all three of the BLADE videos in a row (that’s 1 hour 49 minutes of viewing), Matt Olding has created a YouTube playlist for this series. The rest of the video is dedicated to describing DCL programming and debugging, and I explain how BLADE is the best tool for that job using examples. Did you know that we can thank the far-sightedness of some slightly renegade Autodesk OS/2 developers in the early 1990s for the dialog boxes we use today? Did you know that you could program dialog boxes for AutoCAD for Mac in 1993 but you can’t today? Can you spot the items of interest in the background? If you code in LISP, you’ll love this feature. Here’s the video:īefore I dig into DCL, I start with a brief description of an absolutely brilliant feature that was added to BLADE in V19. With these robust features, it is no wonder why so many companies have been growing STAR*NET networks for 20+ years, providing a big asset to their company.I did my third and final (for now) BricsCAD Unplugged webcast about BLADE last Wednesday. Input data can be given weights to reflect input from old and new instruments, 2D and 3D data and even control points that have long since gone missing. STAR*NET is a practical tool for combining data from total stations, levels, GNSS and gyroscopes. STAR*NET works in 1D (Level), 2D and 3D adjustments and simplifies combining and exporting both ground and grid data. There are importers and conversion utilities for data from all major manufacturers. ![]() STAR*NET provides you with a least squares adjustment solution that works with all your data sources and requirements. From RPLS forums right down to our direct support team, our customers have told us over and over that “STAR*NET does one thing, least squares, and it does it well.” Least squares adjustments are provided by many solutions, though typically as a part of a package that works with proprietary data from proprietary sensors.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |