Script Name

[BIGAL]

@Steven P Under the " <<unamed>>" which is actually the name of the profile being used, look for "General"  and then look at "ACAD" for me that was a support path.

 

Start at "HKEY_CURRENT_USER\\ Software\\AutoDesk\\AutoCAD\\R24.1

 

I found it by searching for a known directory name in the support path, one unique to me.

 

@Fidelojo have a look at this, it is what you need. Very much not everything I have.Lisp files Apr 2024.docx

Edited May 11 by BIGAL

[Fidelojo]

On 5/9/2025 at 2:09 AM, BIGAL said:

Could some please post the equivalent paths for Autocad etc.

Probably this solution by Lee Mac would be good for Autocad, don't really know because I use ZWCad at work but it looks like it could be.

 

Another problem that I found about this approach is that for ZWCad theres no "Startup" location in registry like there is for Autocad, so maybe better approach would be to add 'load' function for main script to acaddoc.lsp/ZWCAD2025doc.lsp or something similar for individual software, something also Lee explained here. I'll try to make it work for ZWCad and post solution here.

 

Also @BIGAL I looked into the Word document you posted, It looks very good but in our firm we have a habit of using keyboard shortcuts for commands so I'm not sure that popup menu would be the best solution for us, but thanks for posting, it looks very good, maybe we will have need in the future to implement something like this.

Edited May 11 by Fidelojo

[Steven P]

Depends how many commands you use, the ones I use every day I remember but some are quite specific, used once a year but save hours and this is where menus come into their own. You can of course have shortcuts and menus

[BIGAL]

There is  no problem with using shortcuts type 47 and my osnaps/osmode are set to 47. You can use numbers if you want. 

 

As I said earlier that there are 130 lisps behind that pop menu. You would never remember all the names. Also it has open block choices by common theme eg CARS, Drainage pits and so on.

 

For a recent client we worked hard at start at the top of a menu and proceed down. Running next step for about half the menu, the remaining half was for optional code.

 

This is drawn using a menu. Each lisp has a single function like draw a window.

[Fidelojo]

15 hours ago, Steven P said:

Depends how many commands you use, the ones I use every day I remember but some are quite specific, used once a year but save hours and this is where menus come into their own. You can of course have shortcuts and menus

You're right, even with this few script that we have in our firm sometimes is almost impossible to remember particular one that you need at the moment. But for now I think I'll stick with just "info dialog" and probably in the future (when more scrips will be needed on daily basis) I will also add an popup and connect to all via main script.

 

11 hours ago, BIGAL said:

There is  no problem with using shortcuts type 47 and my osnaps/osmode are set to 47. You can use numbers if you want. 

 

As I said earlier that there are 130 lisps behind that pop menu. You would never remember all the names. Also it has open block choices by common theme eg CARS, Drainage pits and so on.

 

For a recent client we worked hard at start at the top of a menu and proceed down. Running next step for about half the menu, the remaining half was for optional code.

 

This is drawn using a menu. Each lisp has a single function like draw a window.

Yeah, I understand now, I all the time thought just about my situation in which there is still no need for popup, but yes, with more scripts there will come need to make them more accessible for everyone. Also this project of yours looks awesome, way beyond my level of comprehension of Autolisp and CAD itself, well done, and thanks for showing it, good motivation for someone who just started with Autolisp like me, thanks.