Leaderboard

Not for lisp, but one thing cool about PIP, is it tracks versioning. When you upload a package to PyPi, your package should include a README.MD and a PROJECT.TOML. the toml might look like. requires-python = ">=3.14.0,<3.15.0" dependencies = [ "wxPython>=4.3.1,<4.4", "pywin32; sys_platform == 'win32'", "debugpy>=1.8.0", "pydantic_settings", ] PIP keeps track of every detail for every project and notifies of potential conflicts. Also, it will install dependencies, I.e. Python for AutoCAD requires wxPython, the system will download the modules for you, and also any dependencies wxPython requires. For lisp, something like this would be valuable. dependencies = [ “LM:ODBX 1.2” ... ] Then, have a command in AutoCAD to help manage I.e. Command: PYPIP [List/Install/Remove/Update] <list>: Package Version Editable project location ----------------- ---------------- ------------------------- annotated-types 0.8.0 appdirs 1.4.4 ast_serialize 0.6.0 asttokens 3.0.2 build 1.5.0 cad-pyrx 3.1.6.5712 M:\Dev\Projects\PyRxGit cfgv 3.5.0 click 8.4.2 colorama 0.4.6 debugpy 1.8.21 all of the packages could be streamed into a .bundle for auto loading

Just a question we had laptops that were used outside no internet access, we had two CAD Icons so they would start the correct profile for "in office" and "out of office", how would your system cope with that ? Would the second profile go looking for the VCID ?

Did you check if anything in this thread helps? Delete all Wipeouts within a Drawing including Blocks - Page 2 - AutoLISP, Visual LISP & DCL - AutoCAD Forums Are they actually Wipeouts or could some be text masks, dimension background masks, Hatches, etc.? Could you post an example drawing of exactly what objects you need removed? When I get time, I'll try a shot at what you have already, but an example drawing would help a lot as I don't use Wipeouts a whole lot.

From my experience, GitHub and APPLOAD really serve two different purposes. I usually keep my LISP routines on GitHub so I can access and update them easily. But when I'm actually working in CAD, APPLOAD is still the quickest way to test a routine. For frequently used routines, I add them to the Startup Suite so they load automatically. The problem is that a useful LISP can sit on GitHub and still be almost invisible to CAD users. People usually discover routines through forums, recommendations, or someone sharing the code. Good documentation and simple examples make a huge difference in whether people actually use them. I think GitHub is excellent for maintaining the code and tracking improvements. CAD forums are still important for getting that code in front of people who need it. Ideally, I'd use GitHub for distribution and version control, and APPLOAD for everyday use.

@indiancad @Javier Longa there may be a way of using Array if a new UCS OB is used to orient the grid. In the changed rotation need to rotate the block as well. A question @Javier Longa " since I have no programming knowledge whatsoever" then how did you come by the code ? It is considered good manners to acknowledge who wrote the code, if known, or mention Author unknown.