Topic: Compiling multiple lisps into one larger lisp...

[MP]

RTFM is a powerful tool that every competent developer continually uses, and surprisingly, the very thing that frequently prevents casual coders from evolving. No attitude here, just statin' facts.

Oops. Sorry, thought I was logged in; my bad.

= All your lisp are belong to us =

[Dommy2Hotty]

= All your lisp are belong to us =

lol...that's funny stuff....

I don't take offense to anything said...it's understandable...just be warned that if it happens again, I'll have to punchasize your face






just kidding....

[Kerry]

I don't take offense to anything said

.. you're no fun at all !!

[MP]

... I'll have to punchasize your face ...

A wise person once said:

"You can do anything you wish ... you only have to pay the consequences."

[Dommy2Hotty]

I don't take offense to anything said

.. you're no fun at all !!

well, I know I'm a n00b at this stuff...so I expect to be made fun of for stupid questions...

[Dommy2Hotty]

Okay...got it all compiled, works perfectly (to the best of my knowledge).  Just one more question:  Does having the LISP's in a .mnl file take up memory like loading a LISP file thru the acad2004.lsp's Autoload section?  Or does it only load each LISP when it's called by the button?  Just wondering

[Mark]

It all depends on how you set it up in the .mnl file. But if it were me I wouldn't worry about it that much with todays computers and the amount of ram thay have.

[Dommy2Hotty]

It all depends on how you set it up in the .mnl file.

Just like as follows, but with 19 total defun's for the 19 buttons on the toolbar.  Only difference between them is the defun name, block name, one different insert option on some, and one is on a different layer than the rest.

Code: [Select]


;;; Electrical.mnl file
;;; Dominic Cesare
;;; Last update: Fri June 4, 2004

;Duplex Outlet
(defun c:Duplex_Outlet (/ oldsnaps oldecho oldlayer block)
  ;error trapping
  (setq temperr *error*)
  (setq *error* trap1)
  ;storing current variables
  (setq oldlayer (getvar "clayer")
oldsnaps (getvar "osmode")
oldecho (getvar "cmdecho")
)
  ;turning snaps and echo off
  (setvar "osmode" 0)
  (setvar "cmdecho" 0)
  ;prompts user to select insertion point and rotation
  (prompt "\nSelect Insertion Point and Rotation.....")
  ;inserting block
  (command "-insert" "r1001" "nea" pause "" "" pause)
  ;setting the inserted block to "block"
  (setq block (entlast))
  ;creating PL-ELEC-FIXTURE layer if not present
  (if (not (tblsearch "layer" "PL-ELEC-FIXTURE"))
    (command ".layer" "m" "PL-ELEC-FIXTURE" "C" "3" "" "")
    )
  ;changing inserted block to the PL-ELEC-FIXTURE layer
  (command "change" block "" "p" "la" "PL-ELEC-FIXTURE" "")
  ;resetting system variables
  (setvar "clayer" oldlayer)
  (setvar "osmode" oldsnaps)
  (setvar "cmdecho" oldecho)
  ;error trapping
  (setq *error* temperr)
  ;ending silently
  (princ)
  )
;error trapping
(defun trap1 (errmsg)
  (command "u")
  (setvar "clayer" oldlayer)
  (setvar "osmode" oldsnaps)
  (setvar "cmdecho" oldecho)
  (setq *error* temperr)
  (prompt "Resetting System Variables.....")
  (princ)
  )


[Mark]

Sorry, my mistake. I did not understand what you were doing.  

IMO, the way you have it setup is fine, all the defun's in the .mnl file will be ready to use everytime you open a dwg. i.e. their are all loaded at once. My custom .mnl file is much the same way, except I have more than 19 in mine!! The programs I use on ocassion say once a day I load as needed, like so;

Code: [Select]


(defun c:program () (if (not c:program)(load "program")))

that way it's not loaded until I need it.