|
See reader questions & answers on this topic! - Help others by sharing your knowledge
Welcome to the comp.cad.autocad AutoLISP FAQ
by Reini Urban <rurban@x-ray.at>
Autolisp is a scripting language for AutoCAD, a well known CAD package.
This AutoLISP FAQ is posted to comp.cad.autocad, alt.cad.autocad and
the *.answers groups monthly. Some AutoCAD FAQ's are at
http://www.autodesk.com/support/autocad/ but not posted to
comp.cad.autocad. The contents and the samples apply to all
releases of AutoLISP since Release 10, including Visual Lisp, Vital Lisp
and ACOMP. There's no special AutoLISP newsgroup.
Best are comp.cad.autocad and autodesk.autocad.customization,
but please don't bother comp.lang.lisp.
Source code of all functions in this FAQ is in FAQ-CODE.LSP
(for location see [A.1]), there's also a Winhelp file.
Thanks to all who have contributed. Corrections and contributions
always welcome.
Please see http://xarch.tu-graz.ac.at/acadwiki/RulesToLiveBy
This is part 1/2 of the AutoLISP FAQ v2.28, which consists of:
AutoLISP FAQ (part 1/2) - General
AutoLISP FAQ (part 2/2) - Samples, code
| changes, + new in items from this version to the last posted version,
intermediate personal comments and uncertainties in <..>
-----------------
Table of Contents
-----------------
part 1: General
[0] The Future of AutoLISP? Should I learn it or VB instead?
[0.1] What changed with AutoCAD 2000?
[0.2] We cannot create ARX anymore?
[1] Where can I find AutoLISP routines on the Internet?
[1.1] Are the comp.cad.autocad articles stored somewhere?
[1.2] Autodesk's SDK
[2] What are the best books to learn AutoLISP?
[2.1] Online AutoLISP documents, Winhelp [deleted]
[2.2] AutoLISP Coding Style
[3] How do I debug AutoLISP programs?
[3.1] Native AutoLISP debuggers
[3.2] Modular style, TRACE
[3.3] BREAK function, debug-print
[4] How can I protect my AutoLISP programs? Security
[4.1] Kelvinate
[4.2] Protect
[4.3] Kelvinate and Protect
[4.4] Convert
[4.5] ACOMP
[4.7] Lisp2C
[4.6] Vital LISP Professional
[4.8] Visual Lisp by Autodesk
[5] AutoLISP compilers
[5.1] ACOMP
[5.2] Vital LISP Professional
[5.3] Visual Lisp by Autodesk
[5.4] Better ones: Common Lisp and Scheme
[6] AutoLISP editors and other tools
[6.1] AutoLISP editors
[6.2] Analyzers, Packager and Parenthesis checkers
[6.3] Pretty Printers
[7] AutoLISP problems and bugs
[8] Sorting with AutoLISP
[9] Recursion
[10] Iteration with MAPCAR,...
+ [11] S::STARTUP, My LISPs aren't loading at startup anymore
[12] How to AUTOLOAD my programs?
[13] How can I pass a variable number of
arguments to a LISP function?
[14] How can I avoid stack overflows?
[15] (command "ROTATE3D") does not work! Why?
[16] Lisp programs operating over multiple drawings
[17] How to export Visual Lisp functions to AutoLISP/AutoCAD?
--
[A] Disclaimer, Notes from the authors
[A.1] FAQ Locations
part 2: Samples, code
[20] General Helper functions
[20.1] List manipulation
[20.2] String manipulation
[20.3] symbol->string
[20.4] AutoCAD entity access
[21] Sample Lisp programs
[21.1] Globally change text, polylines, layer utils, date stamp
[21.2] Plot dialog from within LISP. Using DDE or ActiveX
[21.3] (entmod),(entmake) Layers, without (command "_LAYER"...)
[21.4] How to select multiple files in LISP? (as in FILES-Unlock)
[21.5] Replace multiple blocks
[21.6] (vports), VIEWPORT entity, pixel conversion
[21.7] Select all visible objects: zoom coordinates
[21.8] How to write XYZ data of selected objects to a file?
[22] Block Attributes
[22.1] How to access block attributes?
[22.2] How to MODIFY block attributes? DATESTAMP.LSP
[22.3] How to UPDATE block attributes?
[22.4] How to ENTMAKE a Block Complex Entity in AutoLISP
[23] Polylines
[23.1] How to access polyline VERTICES?
[23.2] How to JOIN multiple lines to polylines?
[23.3] Change WIDTH of multiple polylines
[23.4] Create a polyline or spline: with (ENTMAKE) or (COMMAND)
[23.5] How to calculate the LENGTH of polylines?
[23.6] How to revert the polyline direction?
[23.7] How to get the CENTER of a polyline?
[24] Circle/Arc Geometry: BULGE conversion, some trigonometry
[25] DCL: listboxes with tabs or monotext font
[26] EED Extended Entity Data: Get and Store
[26.1] Select objects on their EED with (ssget "X")
[26.2] Get EED from an object
[27] How to break a command in LISP?
[27.1] How to do an unlimited number user prompts?
[28] How to decode ACIS internal geometry with LISP
--
[A] Disclaimer, Notes from the author
+ [A.1] FAQ Locations
[B] Acknowledgements
[C] Recent Changes
User Contributions:Comment about this article, ask questions, or add new information about this topic:Section Contents
Part1 - Part2 - Single Page [ Usenet FAQs | Web FAQs | Documents | RFC Index ] Send corrections/additions to the FAQ Maintainer: rurban@xarch.tu-graz.ac.at (Reini Urban)
Last Update March 27 2014 @ 02:11 PM
|
comp.cad.autocad AutoLISP FAQ (part 1/2) - general
Search the FAQ Archives
N - O - P - Q - R - S - T - U - V - W - X - Y - Z
comp.cad.autocad AutoLISP FAQ (part 1/2) - general
( Part1 - Part2 - Single Page )[ Usenet FAQs | Web FAQs | Documents | RFC Index | Counties ]
Throughout time, we can see how we have been carefully conditioned to come to this point where we are on the verge of a cashless society. Did you know that the Bible foretold of this event almost 2,000 years ago?
In the book of Revelation 13:16-18, we read,
"He (the false prophet who deceives many by his miracles--Revelation 19:20) causes all, both small and great, rich and poor, free and slave, to receive a mark on their right hand or on their foreheads, and that no one may buy or sell except one who has the mark or the name of the beast, or the number of his name.
Here is wisdom. Let him who has understanding calculate the number of the beast, for it is the number of a man: His number is 666."
Referring to the last generation, this could only be speaking of a cashless society. Why so? Revelation 13:17 states that we cannot buy or sell unless we receive the mark of the beast. If physical money was still in use, we could buy or sell with one another without receiving the mark. This would contradict scripture that states we need the mark to buy or sell!
These verses could not be referring to something purely spiritual as scripture references two physical locations (our right hand or forehead) stating the mark will be on one "OR" the other. If this mark was purely spiritual, it would indicate both places, or one--not one OR the other!
This is where it comes together. It is amazing how accurate the Bible is concerning the implantable RFID microchip. Here is information from a man named Carl Sanders who worked with a team of engineers to help develop this RFID chip:
"Carl Sanders sat in seventeen New World Order meetings with heads-of-state officials such as Henry Kissinger and Bob Gates of the C.I.A. to discuss plans on how to bring about this one-world system. The government commissioned Carl Sanders to design a microchip for identifying and controlling the peoples of the world—a microchip that could be inserted under the skin with a hypodermic needle (a quick, convenient method that would be gradually accepted by society).
Carl Sanders, with a team of engineers behind him, with U.S. grant monies supplied by tax dollars, took on this project and designed a microchip that is powered by a lithium battery, rechargeable through the temperature changes in our skin. Without the knowledge of the Bible (Brother Sanders was not a Christian at the time), these engineers spent one-and-a-half-million dollars doing research on the best and most convenient place to have the microchip inserted.
Guess what? These researchers found that the forehead and the back of the hand (the two places the Bible says the mark will go) are not just the most convenient places, but are also the only viable places for rapid, consistent temperature changes in the skin to recharge the lithium battery. The microchip is approximately seven millimeters in length, .75 millimeters in diameter, about the size of a grain of rice. It is capable of storing pages upon pages of information about you. All your general history, work history, criminal record, health history, and financial data can be stored on this chip.
Brother Sanders believes that this microchip, which he regretfully helped design, is the “mark” spoken about in Revelation 13:16–18. The original Greek word for “mark” is “charagma,” which means a “scratch or etching.” It is also interesting to note that the number 666 is actually a word in the original Greek. The word is “chi xi stigma,” with the last part, “stigma,” also meaning “to stick or prick.” Carl believes this is referring to a hypodermic needle when they poke into the skin to inject the microchip."
Mr. Sanders asked a doctor what would happen if the lithium contained within the RFID microchip leaked into the body. The doctor replied by saying a terrible sore would appea (...)