Lisp is supposed to break polylines

[Opie]

Add this to the very beginning of Tim's code above.

(vl-load-com)
(if (vl-string-search "FLOW" (strcase (getenv "ACAD")))
  (progn

And place this code at the very end of Tim's code from above.

  )
)

The above changes search the Support File Search Path (getenv "ACAD") for an occurance of the word "FLOW" in reference to the "FLOW" directory. This would make the above changes only to the AutoFLOW based AutoCAD session.

[jgratton]

Not deviating you from the main topic, but I think we can delete the extra right parentheses (red).

You could check if an AutoFlow.MNL file is available with the AutoFlow.MNU/MNC etc. If it is available, place the code to load MyLisp.LSP at the end of the AutoFlow.MNL, so that it will be loaded during the AutoFLOW session only.

Regards,

Abdul Huck

Yes! There is one! Here is what's there now...

(if (null gb_ds2dLoaded_Menu_Lisp)
(progn
(load "ds2dMenu")
(setq gb_ds2dLoaded_Menu_Lisp T)
) ;_ progn
) ;_ if


and this method sounds like it has merit too. But as I said earlier this release was designed to work with 2002-2006 as far as I know. If we were to upgrade to 2006, would the lisp or mnl have to change because of cuis?

[.T.]

Yes! There is one! Here is what's there now...

(if (null gb_ds2dLoaded_Menu_Lisp)
(progn
(load "ds2dMenu")
(setq gb_ds2dLoaded_Menu_Lisp T)
) ;_ progn
) ;_ if


and this method sounds like it has merit too. But as I said earlier this release was designed to work with 2002-2006 as far as I know.

Now that we know it works, it MAY be possible to move up the load order and use the MNL as Abdul mentioned, and yes, it has merit. We will need to change the code and test it, though.

There will be a point where we cannot go any further up the load order because the Pro-cad functions will start loading over your functions and revert back to using the ones from before. I don't know if that point will fall before or after the mnl loads. I don't have the software, and I don't know at what point that will be, so I started at the far end thinking that would be the best way to go.

I think the way we have it set up is good, but let me know if you want to persue this and I'll try to help as I have time.

If we were to upgrade to 2006, would the lisp or mnl have to change because of cuis?

Acaddoc.lsp and mnl's work the same in 2006, so either method can be transfered.

You may want to have a look at THIS (by rkmcswain). It could make your life easier later on. I would also have a look at these threads to get you up to speed on CUIs if upgrading is in your near future:

CUI and workspace videos from Autodesk

and

Notes on the philosophy of CUI

[jgratton]

Thanks, Tim. I want the easiest method to maintain and yours and opie's seems to involve fewer customized files, which is a good thing from my point of view. Since time is of the essence as well I will stick with this in the short term because I know it works for us. I am sure the mnl suggestion will be of value to others including ourselves down the line.

BTW, I was pretty involved in that second thread early on. Earned my grey hair! I have since switched jobs and will not be upgrading in the forseeable future.