BricsCAD is a almost perfect clone for AutoCAD, but many users are missing the GeomCal functionality. This problem is solved with the Lisp-application CADCAL, which can be downloaded for free from www.archtools.de/cadcal.zip. CADCAL brings the same functionality as GeomCal, including the possibility to use GeomCal calculations in Lisp like in (cal "PLT(end,end,/3)"). You can get an overview of CADCAL at www.archtools.de/cadcal.html.

CADCAL has some more functions than GeomCAL, i.e. PGR(<p1>,<p2>) which divides the distance between P1 and P2 in the Golden Ratio, oder PCG(<p1>,<p2> ... <pn>) which returns the center of gravity of a polygon over all points in the function's argument.

And now CADCAL also can be used with a dialog and a history od previously calles math expressions. The dialog is called with the command DDCAL and should be self explaining. The history is stored inside the dwg and will be restored when you reopen the dwg. All results of all math expressions in the history are stored too and can be recalled. DDCAL can be called transparently from any running CAD command, and the results of the calculations as well as the recalled results of previous results from the history list can be used directly as input to the running command. The ZIP also contains a demo DWG file with a history of CADCAL expressions for a first view at this functionality.

CADCAL is programmed in Lisp only, and therefore should work in AutoCAD, BricsCAD and all similar CAD applications as well. CADCALs parser first translates the string containing the math expression into an evaluable Lisp expression. The user can do this too using the CC-STR->LISP function, i.e. using (CC-STR->LISP "PLD(end,end,100)"). Because any math expression needs only one single translation within the same DWG-Session, CADCAL is rather fast. In AutoCAD overall CADCAL is about 5 to 10% slower than GeomCal, and in BricsCAD because the very fast Lisp interpreter CADCAL is about 10 times faster than GeomCal.

The DDCAL functionality is new and therefore CADCAL is still in beta stadium. Please let me know what you think of CADCAL. If you have any ideas for additional functionality, then please let me know.

You need your alignment to have a common point on both alignments then it should work automatically. I would then remove the labelling of the alignment at fixed chainage near the intersection point if necessary.
eg 20.85 remove 20.00.

PS CIV3D etc.

@HOSNEYALAA, thank you for your reply.

No need for example drawings, you may have the following texts in the drawings (i.e. glass1, glass2, brick1, brick2, steel1, steel2, wood), the mentioned lisp will list and table all the above texts, but if I want to list and table only glass than the lisp need to give a search/find option.

For now my only option is to have the listed table and to delete all other unwanted text manually.

The mode is the most common number that appears in your set of data. To find the mode count how often each number appears and the number that appears the most times is the mode.

https://www.ncl.ac.uk/webtemplate/ask-assets/external/maths-resources/statistics/descriptive-statistics/mean-median-and-mode.html#:~:text=Mode-,Definition,most%20times%20is%20the%20mode.

Mode: The most frequent number—that is, the number that occurs the highest number of times.

https://www.khanacademy.org/math/statistics-probability/summarizing-quantitative-data/mean-median-basics/a/mean-median-and-mode-review

Seems 'mode' is not an Cardinal value, just the number that appears most . . nor an analysis of the other numbers.

. . . so my expectation would be to return a single number, or a list if there are multiple modes

Having two modes is called "bimodal".

Having more than two modes is called "multimodal".

I s'pose the handling of a list with an equal amount of each number would depend on the use case.


//--
edge cases can be a killer.

I think I must be missing something here, here is the code I have:

Code - C#: [Select]

1.      activeDoc.SendStringToExecute("_.qsave\n", false, false, false);
2.  

The above line doesn't execute until after your code returns control to AutoCAD. Unless it's being called from the application context, I would use the Editor's Command() method.