All Activity

Thanks @SLW210 if you go to MS Word and just say make 5 paragraphs you can Number or Alpha each of those paragraphs. So adding or removing auto redoes the item. I then added a new indent label using Hexagon TTF and removed the period so got the hexagon labels to appear. My idea was to make a TTF with a character like "A" but it makes a hexagon enclosed "1" so can do 1-26. 27-52 is lowercase. In Word use A-Z as items in Cad appear as numbers. The lisp code will make either a dxf or pdf of 1-9 and A-Z for testing. I think need to adjust sizes as I think that was part of problems with fontforge. make num in hexagon.lsp

Dont forget about DUMPIT.lsp that shows the properties via VL. I use it often reveals lots of info. DumpIt.LSP

At a glance a couple of comments; Dont use "X" in the ssget. so you can select one or more objects. Ok the reason the objects array backwards is because of the arc direction, I tested by arraying objects two times and pick an arc on both ends and yes array went wrong way for one end pick. So there is a way around it, select an end you imply a direction, so use a pause to select path. Dont use the ssget to get path object. Rather use Entsel or even getpoint. My take on the task. (defun c:AUTOHPA ( / objLayer objSS pt pathCurve pathLength items) (setvar "CMDECHO" 0) (setq objlayer (cdr (assoc 8 (entget (car (entsel "\nPick an object for layer name ")))))) (princ "\nPick objects to Array ") (setq objSS (ssget (list (cons 8 objLayer)))) (if (= objSS nil) (progn (alert "No objects selected that match layer name \nWill now exit")(exit)) (progn (setq items (getint "\nEnter how many items ")) (setq pathCurve (entsel "\nPick path near an end for direction ")) (setq pt (cadr pathCurve)) (setq path (vlax-ename->vla-object (car pathcurve))) (setq pathLength (vlax-curve-getDistAtParam path (vlax-curve-getEndParam path))) (princ pathLength) (command "._ARRAYPATH" objSS "" pt "M" "D" "I" items "") (princ "\nArray completed successfully using layers.") ) ) (setvar "CMDECHO" 1) (princ) ) (c:AUTOHPA)

@Steven P "For each new installation you typically need to populate the startup suit though - the settings are saved as (typically) a Windows Registry key - and it is possible to have a LISP to add modify registry keys... just need to find the key location..." I've tried using lisp to add the items into the Startup Suite window via the registry. Unfortunately, I've not been successful in populating the Startup Suite window using this automated method. Perhaps you can share your lisp routine that is successful in getting this to work.

So I am not so sure about BricsCad But yes, in AutoCAD there is a pop-up from the Appload dialogue - bottom right corner - 'startup suit' that loads things on opening each drawing (Usually LISPs). For each new installation you typically need to populate the startup suit though - the settings are saved as (typically) a Windows Registry key - and it is possible to have a LISP to add modify registry keys... just need to find the key location. In AutoCAD it is not a tricky task with 5 or 6 mouse clicks for each LISP for each time you have a new installation to change the startup suit. You can also save LISPs to trusted locations - load on demand - but this falls down that each user would need a local copy of the code, a central store in the company shared drives is better. If you do that then all that needs entering into the startup suit is a single LISP file, and this file contains the load on demand code, for example: (Defun C:ZA ( / ) (Load "F:\\AutoCAD\\AutoCAD LISPS\\ZOOMS.lsp") (C:ZoomAll)) Here the user uses the Alias or shortcut ZA, which loads the LISP file Zooms and runs ZoomAll - Having an alias like this will always load in the latest version, typically takes milliseconds to load the file - the time it takes to move the mouse a bit. Instead of ZoomAll use ZA and you will only get the newest copy when a drawing opens but it is faster (and usually sufficient considering the number of times a LISP has major updates made) Whoever manages the company LISPs (if anyone does) only has to save the file somewhere shared and add to the LISP in the startup file once the LISP is validated and approved everyone has access next time they start AutoCAD. Probably teaching your granny to suck eggs there... sorry!

@Steven P So it is "APPLOAD" - meaning the lisps files are loaded on startup, not as "autoload" that only load the lisp the first time you type the command - load on demand? and can you save this "startup suit" to a file and use it on other computer or you must do it manually on a new machine?

curve direction reverse using pedit I have tried but not working. I think script is not working because of default base point selection.

manually arraypath is working fine but only while script running it is not working. At some location of layout it is working and at other location same script is not working. test_01.dwg

I am still not 100% on what the OP is asking for "EXACTLY" though they seem happy with @Romero's latest code. I might have time too look into it later this week. I have used Fontforge a long time ago, I'll see what I can hammer out.

That's an Image, not a drawing. But since you want guesses only, my WAG is the direction of whatever object you are using for the 'curve path".

IIRC, I have just frozen all layers (or use LAYISO is usually easier) except what I need or even create a couple of new layers and only have those on. You can also try tweaking the scale, angle, etc.

Best way to troubleshoot an issue in general is to watch the commandline and history, or in my case, the Text Window. I keep as much screen as possible when working on something, so no commandline ever. Dual screens I can have the Text Window open on the other monitor. Also, Properties can be opened with a Right-Click, so need need for that always on screen, mine is always docked. Is this question about 3D modelling only or just in general? If it's a geometry issue a close inspection usually can detect that if nothing shows in the commandline history. For 3D SECTIONPLANE can check for issues. LIST is handy in some cases, I sometimes use it for LISP uses, but I have various DUMP LISPs too, those can also help detect some issues. If it is a drawing I started, there usually should be no issues with geometry, like open gaps where you expect closed shapes, etc. so exactly what specific issues are you thinking of? LIST is probably behind a look at the Text Window and history, Properties, and a quick glance. But I usually use LIST for a way to quickly copy and paste that information and/or for double checking LISP results et. al.

This group already has 30+ members, welcome all developers, CAD managers, and users to join for CAD usage, technical discussions, development, and plugin sharing.

'Appload' and Startup suit is in the bottom right corner... in AutoCAD.... Must be AutoLoad in BricsCAD

@BIGAL I'm awre of APPLOAD... that's why I asked @Steven P what did it means - is it the use of APPLOAD or other way?

Just type Appload in Bricscad, you will ser the "Load Application Files" click on "Autoload" and the lisp entry will be loaded on startup.

That makes sense! Keeping Properties open is definitely more convenient when checking and changing values repeatedly. I guess LIST is still useful when you want a quick text-based report of an entity, but Properties is more practical for everyday editing.

@Steven P what do you mean by "startup suit"?

FYI, I used to run the LIST command quite a bit to give me information about the object(s) in question. But with the introduction of the Properties command in AutoCAD 2000, I slowly got used to leaving the Properties window opened/docked in the drawing area. Then as an object is selected, it's "properties" would automatically be filled out for me to inspect inside the Properties window. There's no need to run an extra command sequence like the LIST command which then would have to display the information on on a separate Text screen. In addition, the Properties window makes it possible for you to enter new values into those property items that can be modified.

Just thought of another trick I've used in the past. I would let AutoCAD create a brand new outline of the area to be hatched for me with the Boundary command. But in the Boundary Creation window under Boundary set, do not use the default Current viewport setting. But instead click on the New button and then select only the objects that form the hatch area outline. This restricts AutoCAD to only consider those objects selected to generate the new boundary. Leave the Object type as Polyline and usually with this new Pline boundary generated, the Hatch creation completion success rate would increase just a tad more.

The LIST command is useful when I need to inspect an entity’s properties, such as its coordinates, length, radius, or object type. It can help when a drawing looks correct but I need to verify the actual geometry. However, one limitation is that LIST reports geometric data rather than explaining why an operation failed. For example, if a 3D Boolean operation fails, the LIST output alone may not reveal whether the problem is caused by intersecting geometry, invalid solids, or another modeling issue. When troubleshooting a difficult 3D modeling problem, how far do you rely on LIST before switching to other inspection methods?

Good point. Using the object option can simplify things when the existing geometry already defines a usable boundary.

That’s a smart workaround, especially when you’re up against a deadline! Using a polyline on a nonplotting layer seems much easier than trying to fix every tiny gap in the original boundary.

Breaking a complicated area into smaller sections makes sense, especially when only part of the boundary is causing trouble. Mirroring a hatch across a symmetrical part is also a useful workaround I’ll keep in mind.

Interesting point about different hatch patterns behaving differently with the same boundary. I hadn’t considered that moving the geometry or changing the pattern could sometimes help. It shows that the issue isn't always just the boundary itself.