AutoCAD Visual LISP Technical Newsletter - March 2000

XDSoft

AutoCAD Visual LISP Technical Newsletter - March 2000  
This document is part of    Visual Lisp Newsletter Archive     



/Note: Have you missed a Newsletter issue? Visit our Newsletter archive at
the following URL:/

http://adn.autodesk.com/techsupp/docs/newsletters.htm
  

Dear Visual LISP developer,
  

Table of Contents
=================
(1)  VL *ERROR* HANDLER THAT PREVENTS FUNCTION CANCELLATION
(2)  ARX FUNCTION EXPOSURE WITHIN A SEPARATE NAMESPACE VLX
(3)  USING LISP TO READ AN ACCESS DATABASE VIA ADO
(4)  CASCADING PULLDOWN SUBMENU TERMINATOR IS NOT WRITTEN TO MNS FILE
(5)  New or updated solutions
  

With the advent of the Multiple Document Environment, and the resultant
Multiple Document Namespaces, Visual LISP introduced the
Separate-NameSpace VLX.

That's compiled lisp code which runs outside the current document
namespace, and in it's own code name-space.

This new feature adds more power, and different coding requirements
beyond those necessary for lisp routines that run in a drawing.

In addition to the essential documentation here in the:

Visual Lisp Developer's Guide -> Chapter 4 -- Building Applications ->
Designing for a Multiple Document Environment ->
Running an Application in Its Own Namespace,

and here:

Visual Lisp Developer's Guide -> Appendix A
-- AutoLISP Function Synopsis -> VLX Namespace Functions

We have created a few solutions which demonstrate using SNS VLX's.

==================================================================
(1) 19037 - VL *ERROR* HANDLER THAT PREVENTS FUNCTION CANCELLATION
==================================================================
Ever want lisp to handle an error, yet still keep processing code instead
of dying ?

Here's a solution that provides example code using a SNS
(Separate NameSpace) VLX to do just that:

/cgi-bin/solution.pl?SID=19037

==================================================================
(2)  47496 - ARX FUNCTION EXPOSURE WITHIN A SEPARATE NAMESPACE VLX
==================================================================
In a SNS (Separate NameSpace) VLX the (vl-arx-import) function is required,
to expose ARX function(s) to your VLX code. See this solution for more
information:

/cgi-bin/solution.pl?SID=47496

==================================================
(3)  USING LISP TO READ AN ACCESS DATABASE VIA ADO
==================================================
Looking for a way to use Microsoft's ADO COM database technology with
Visual Lisp ? Here's some example code that demonstrates this:

/cgi-bin/solution.pl?SID=48677

=============================================================================
(4)  45782 - CASCADING PULLDOWN SUBMENU TERMINATOR IS NOT WRITTEN TO MNS FILE
=============================================================================
Wishing to create an on-the-fly pulldown menu, using the new ActiveX Menu
API's? It's not hard, but creating a complex pulldown menu via code does
seem a bit daunting when you first try it. This solution demonstrates how
to put all the pulldown menu parts together, and provides a critical
demonstration of the EndSubMenuLevel Property for cascading pulldown menus.

/cgi-bin/solution.pl?SID=45782

============================
(5) New or updated solutions
============================

VL *ERROR* HANDLER THAT PREVENTS FUNCTION CANCELLATION
/cgi-bin/solution.pl?SID=19037

ACCUST: USING ENTMAKE TO CREATE LWPOLYLINES
/cgi-bin/solution.pl?SID=37860

HOW TO DEFINE LISP CODE FOR AN UNDO OF A MENU SELECTION
/cgi-bin/solution.pl?SID=44795

(COMMAND "_REGEN") LEAVES AN UNDO GROUP ACTIVE
/cgi-bin/solution.pl?SID=44937

HOW TO DELETE A DATABASE LINK WITH VISUAL LISP
/cgi-bin/solution.pl?SID=45169

NO DIALOG DISPLAYS WHEN I RUN A COMMAND VIA LISP OR A SCRIPT
/cgi-bin/solution.pl?SID=45187

ENTMOD OF OLD STYLE HATCHING CAUSES AUTOCAD TO CRASH
/cgi-bin/solution.pl?SID=45644

HOW TO SPECIFY A UNC PATH NAME IN LISP
/cgi-bin/solution.pl?SID=45762

CASCADING PULLDOWN SUBMENU TERMINATOR IS NOT WRITTEN TO MNS FILE
/cgi-bin/solution.pl?SID=45782

RTOS DOES NOT RETURN DECIMALS AS SPECIFIED
/cgi-bin/solution.pl?SID=45865

ARX FUNCTION EXPOSURE WITHIN A SEPARATE NAMESPACE VLX
/cgi-bin/solution.pl?SID=47496

DOES LISP CONSIDER '/' AS DIVIDE OPERATOR IN DISTOF FUNCTION?
/cgi-bin/solution.pl?SID=47637

USING LISP TO  FIND OUT THE VERSION OF A DWG?
/cgi-bin/solution.pl?SID=48199

USING LISP TO READ AN ACCESS DATABASE VIA ADO
/cgi-bin/solution.pl?SID=48677

HOW CAN I USE LAYOUTLIST FUNCTION IN A SEPARATE NAMESPACE VLX?
/cgi-bin/solution.pl?SID=48898

HOW TO SET A POLYLINE'S WIDTH USING ACTIVEX?
/cgi-bin/solution.pl?SID=49217

-----------------------------------------------------------------------------
To subscribe or unsubscribe, go to
http://adn.autodesk.com/techsupp/docs/newsletters.htm
-----------------------------------------------------------------------------

You received this message as a result of your registration
on the ADN List Server subscription page.  If you no longer wish
to receive these messages, read the next section, How to use this
mailing list.

How to use this mailing list:

You may unsubscribe from this e-mail newsletter, or subscribe to
a variety of other informative e-mail newsletters, by returning
to the ADN List Server subscription page at
http://adn.autodesk.com/techsupp/docs/newsletters.htm
and changing your subscription preferences.

Alternatively, from the subscribed account you can send an e-mail to
<Majordomo-partnersys@autodesk.com> with the following command in the
body of your email message:

unsubscribe <list-name>

----------------------------------------------------------------------

Autodesk Developer Network (ADN) information and events:

For information on all ADN topics, please visit:
  http://www.autodesk.com/adn

----------------------------------------------------------------------

THIS DOCUMENT IS PROVIDED FOR INFORMATIONAL PURPOSES ONLY.  The
information contained in this document represents the current view of
Autodesk Inc. on the issues discussed as of the date of publication.
Because Autodesk must respond to change in market conditions, it
should not be interpreted to be a commitment on the part of Autodesk
and Autodesk cannot guarantee the accuracy of any information
presented after the date of publication.
INFORMATION PROVIDED IN THIS DOCUMENT IS PROVIDED 'AS IS' WITHOUT
WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND FREEDOM FROM INFRINGEMENT.
The user assumes the entire risk as to the accuracy and the use of
this document. This  document may be copied and distributed subject to
the following conditions:
1.   All text must be copied without modification and all pages must
     be included
2.   All copies must contain Autodesk's copyright notice and any other
     notices provided therein
3.   This document may not be distributed for profit