                                   
     +==========================================================+
         READDOC.TXT - R13c4 Manual Corrections and Additions
     +==========================================================+
                                   
                           15 December 1995



This file contains updates and corrections to the current AutoCAD
documentation set. For a description of changes and additions to the
documentation that shipped with AutoCAD R13c0 - R13c3, see the
R13C4NEW Help file (for Windows) or the R13C4NEW.TXT file (for DOS and
UNIX).

=====================================================================-
CONTENTS
========-

  - General Notes
  - AutoCAD Command Reference
  - AutoCAD User's Guide
  - AutoCAD Customization Guide
  - ADS Developer's Guide

The following list describes the R13c4 readme files:

README         Contains general information related to all platforms.
READPC         Contains DOS-specific and Windows-specific information.
READDOC        Contains documentation updates and revisions.
READDEV        Describes the text files that explain how to compile,
               link, and debug ADS and ARX applications, and tells
               where to find them.
READHIST       Describes the history of enhancements, fixes, and
               information related to each of the R13 update releases.


=====================================================================-
GENERAL NOTES
=============-


Leader Associativity
--------------------
Information which implies that leader objects and their annotation
become associated with each other is incorrect. Leader objects and
their annotation aren't associated with each other.


=====================================================================-
AUTOCAD COMMAND REFERENCE
(PUBLICATION #00105-000000-5031)
==========================================================-

ASEADMIN, Link Path Name, page 46
---------------------------------
The third sentence in the second paragraph of this option description
should be changed to:

    A single link created with the primary link path name can
    reference data in both tables.


DDIM, Name, page 186.
---------------------
The statement concerning renaming the default STANDARD dimension style
is incorrect. You can rename the default STANDARD dimension style. The
sentence:

    "To rename a style, enter a name and then choose Rename---you
    can't rename the default STANDARD dimension style."

should be changed to:

      "To rename a style, enter a name and then choose Rename."


Appendix A, System Variables, CMLJUST, page 727
-----------------------------------------------
The CMLJUST system variable is saved in the drawing, not in the Config
file.


Appendix A, System Variables, CMLSCALE, page 727
------------------------------------------------
The CMLSCALE system variable is saved in the drawing, not in the
Config file.


Appendix A, System Variables, CMLSTYLE, page 727
------------------------------------------------
The CMLSTYLE system variable is saved in the drawing, not in the
Config file.


Appendix A, System Variables, FONTALT, page 747
-----------------------------------------------
The initial value of this system variable has been changed from
"txt.shx" to "". This prevents slow operation when font files that
can't be found during the loading of a drawing.


Appendix A, System Variables, MTEXTED, page 753
-----------------------------------------------
The description for this system variable should be revised as follows:

Sets the primary and secondary text editors to use for mtext objects.
This allows you to use the small "Edit Mtext" dialog box on mtext
objects up to 80 characters long. This avoids clearing the screen and
going to full-screen editors such as DOS Edit or Notepad. For mtext
objects larger than 80 characters long you can specify the editor to
be used, or accept the default editor.

As an editor, you can also specify an AutoLISP function that has been
designed for editing text. This can be any function that accepts a
single string argument. The function will be called only if the mtext
object contains less than 80 characters. The function should return
one of the three values:

    A string of less than 256 characters. This string will then
    replace the current mtext contents.
    An integer, 0. This will cancel the editing operation.
    An integer, -1. This will cause the operation to use the
    secondary editor.

The MTEXTED syntax is as follows:

     :<lisp function name>#<editor name>

where:
:                       is the AutoLISP indicator
<lisp function name>    is the primary editor (an AutoLISP function
                        designed for editing text)
#                       is the separator between the primary
                        and secondary text editors
<editor name>           is the secondary editor

Some valid values are:
Internal                the Windows Mtext editing dialog box
Notepad                 the Windows Notepad editor
lisped                  built-in AutoLISP function for editing  small
                        mtext objects with the small "Edit Mtext"
                        dialog box
blank                   the default editors (DOS Edit or Notepad)
<function name>         an AutoLISP function name designed for editing
                        text
<editor name>           an external text editor

Examples
:lisped                 Use the AutoLISP function, lisped as the
                        primary editor if the mtext object is less
                        than 80 characters long. If the mtext object
                        is greater than 80 characters long, the
                        default editor is used (DOS Edit or Notepad).
:Lisped#internal        Use the AutoLISP function, lisped as the
                        primary text editor if the mtext object is
                        less than 80 characters long. Use the internal
                        Mtext dialog box as the secondary text editor
                        if the mtext object is greater than 80
                        characters long. (Windows only).
<editor name>           Use the external editor named <editor name>.
:lisped#<editor name>   Use the AutoLISP function, lisped as the
                        primary editor if the mtext object is less
                        than 80 characters long. If the mtext object
                        is greater than 80 characters long, the
                        external editor <editor name> is used.
:<function name>        Same as :lisped above, but uses the AutoLISP
                        function <function name> instead.


=====================================================================-
AUTOCAD USER'S GUIDE
(PUBLICATION #00105-000000-5021)
=====================================================-


Chapter 2, Creating Multiline Styles, page 47
---------------------------------------------
The following text should replace the procedural steps entitled "To
create a multiline style" in the "Creating Multiline Styles" section
beginning on page 47.

To create a multiline style
1.  Open the Multiline Styles dialog box using one of these methods:
  Windows      From the Object Properties toolbar or the Data menu,
               choose Multiline Style.
  DOS and UNIX       From the Data menu, choose Multiline Style.
2.  In the Name box, enter a style name.
3.  In the Description box, enter a description of the style if you
    want it described. The name you enter can have up to 255
    characters, including spaces.
4.    Choose Element Properties to add elements to, or to modify
elements of the style.
5.  To modify a default element, select one from the Element
    Properties dialog box. Then make the changes to Offset, Color,
    and Linetype.
6.  To add an element, select Add in the Element Properties dialog
    box. Then make the changes to Offset, Color, and Linetype.
    Offset defines the 0,0 origin of the multiline, relative to which
    all other elements are drawn. There doesn't have to be an element
    drawn at the origin.

Now finish defining the element properties and save the style.
1.  Choose OK in the Element Properties dialog box.
2.  Choose Add to add the style to the drawing, and set this style as
    current.
3.  Choose Save to save the style to an external multiline style file
    (.mln file, the default is acad.mln).

You can add up to 16 elements to a multiline style. If you create or
modify an element so that it has a negative offset, it appears below
the origin in the image tile of the Multiline Style dialog box.


Chapter 7, Inserting Block References, page 230
-----------------------------------------------
The procedure titled "To insert a block using drag and drop in
Windows" states that AutoCAD must be minimized before a drag and drop,
this is incorrect, drag and drop only works when AutoCAD is NOT
minimized.


Chapter 8, Adding Text to Drawings.
-----------------------------------
Add a new section entitled, "Editing Mtext Objects with DDEDIT"

Depending on the setting of the MTEXTED system variable, you can edit
mtext objects with a variety of editors using DDEDIT.

For mtext objects up to 80 characters long, you can use the DDEDIT
dialog box rather than the default full-screen editor (DOS Edit or
Windows Notepad). For mtext objects larger than 80 characters long,
you can specify the editor to be used, or accept the default full-
screen editor. For more information on specifying primary and
secondary editors see the MTEXTED system variable.

To edit an mtext object:
1.  Start the DDEDIT command using one of these methods:
  DOS          From the Modify menu, choose Edit Text.
  Windows   Choose the Edit Text icon on the Modify toolbar.
2.  Select the text to edit.
    The text can display in the default full-screen editor, a DDEDIT
    dialog box or in a user-specified external editor.
    To use the default full-screen editor from the DDEDIT dialog box
    choose the Full Editor button.
    Note: In the DDEDIT dialog box you can use the codes described in
    the "Format codes for paragraphs" table in the "Formatting
    Paragraph Text in a Text Editor" section of the AutoCAD User's
    Guide.

Command line equivalent:  DDEDIT
Related:  MTEXTED sets the primary and secondary text editors to use
for mtext objects.


Chapter 13, Defining Primary and secondary link Path Names, page 496
--------------------------------------------------------------------
The following should be added to the first paragraph:

When you create a link using a secondary link path name, you will not
be able to access records from tables referenced through the primary
link path name using this link. In order to access multiple tables
from one link path name, all links must be created using the primary
link path name.


=====================================================================-
AUTOCAD CUSTOMIZATION GUIDE
(PUBLICATION #00105-000000-5041)
============================================================-


Forcing the display of a pull-down menu, pages 100, 102, 107, and 114
---------------------------------------------------------------------
The ability to force the display of a pull-down menu does not conform
to Windows guidelines. Therefore, calling of the Pn=* syntax from a
menu macro or with the menucmd function will not be supported on
Windows platforms in future releases.


Special label characters, page 108
----------------------------------
It should be noted that on Windows platforms the "&" character
specifies the accelerator key just as the "/c" sequence does.


Command Scripts, page 153
-------------------------
The following should be added to this section:

All references to long file names that contain embedded spaces must be
enclosed in double quotes. For example, to open the drawing MY
HOUSE.DWG from a script you must use the following syntax:

    open "my house"


Invoking a Script when Loading AutoCAD, page 154
------------------------------------------------
The following should be added to this section:

You can use the <dwgname>=<prototype_dwgname> syntax in place of
<dwgname> to run a script on a new drawing based on a prototype. For
example, to run the script MAKE_BOX.SCR on a new drawing named CIRCLE
which uses the drawing PROTO1 as a prototype, use the following
command syntax:

    ACAD CIRCLE=PROTO1 MAKE_BOX

To run a script on a drawing that uses the default prototype (a new
unnamed drawing) use a dot (period) in place of the <dwgname>, as in
the following:

    ACAD . MAKE_DWG

On systems that make use of long file names, any drawing or script
name that contains embedded spaces must be enclosed in double quotes.


Opening and Closing Dialog Boxes, page 286
------------------------------------------
To properly function with the AutoLISP code at the bottom of the page,
the first line of the DCL code example should read as follows:

    hello: dialog {


dictadd, page 377
-----------------
As a general rule, each object added to a dictionary must be unique to
that dictionary.

This is specifically problem when adding group objects to the group
dictionary. Adding the same group object using different key names
results in duplicate group names which can send the dictnext function
into an infinite loop.


dictdel (dictremove), page 378
------------------------------
This function has been renamed to dictremove.

The following should be added to the dictremove function description:

If successful, dictremove returns the entity name of the removed
entry.

By default, removing an entry from a dictionary does not delete it
from the database. This must be done with a call to entdel. Currently
the exceptions to this rule are groups and mlinestyles. The code that
implements these features requires that the database and these
dictionaries be up to date, and therefore automatically deletes the
entity when it is removed (with dictremove) from the dictionary.

The dictremove function disallows the removal of an mlinestyle from
the mlinestyle dictionary if it is actively referenced by an mline in
the database.


startapp, page 461
------------------
If an argument has embedded spaces, it must be surrounded by literal
double quotes. For example, to edit the file "my stuff.txt" with
Notepad use the following syntax:

    (startapp "notepad.exe \"my stuff.txt\"")


OLE2FRAME, page 688
-------------------
This is a new entity type. The following information should be added
to Appendix C:

OLEFRAME
The following group codes apply to ole2frame entities. This
information is read only. During DXFIN, the values are ignored, since
they are part of the OLE binary object, and are obtained via access
functions.

Ole2frame group codes
Group codes    Description
100            Subclass marker (AcDbOle2Frame)
70             OLE version number
3              OLE object description, such as "Paintbrush Picture"
10, 20, 30     x,y,z of the upper left corner (WCS)
11, 21, 31     x,y,z of the lower right corner (WCS)
71             OLE object type, 1 = link, 2 = embedded, 3 = static
72             Tile mode descriptor,
               0 = object is in a tiled model space viewport
               1 = object is in a non-tiled viewport (paper space or
               floating model space)
90             Length of binary data
310            Binary data
1              End of Ole date (the string "OLE")

Sample DXF output:
    OLE2FRAME
      5
    2D
    100
    AcDbEntity
     67
         1
      8
    0
    100
    AcDbOle2Frame
     70
         2
      3
    Paintbrush Picture
     10
    4.43116
     20
    5.665992
     30
    0.0
     11
    6.4188
     21
    4.244939
     31
    0.0
     71
         2
     72
         1
     90
        23680
    310
    0155764BD60082B91140114B08C8F9A916400000000000000000506DC0D0D9AC

    310
    1940114B08C8F9A916400000000000000000506DC0D0D9AC194002303E5CD1FA

    310
    10400000000000000000764BD60082B9114002303E5CD1FA1040000000000000
    ...
    ...

AutoLISP entnext function sample output:
    Command: (setq e (entget e3))
    ((-1 . <Entity name: 7d50428>) (0 . "OLE2FRAME") (5 . "2D")
    (100 . "AcDbEntity") (67 . 1) (8 . "0") (100 . "AcDbOle2Frame")
    (70 . 2) (3 "Paintbrush Picture") (10 4.43116 5.66599 0.0)
    (11 6.4188 4.24494 0.0) (71 . 2) (72 . 1))


=====================================================================-
ADS DEVELOPER'S GUIDE
(ELECTRONIC DOCUMENT)
===========================================-


ads_getfiled function description, chapter 6, page 227
------------------------------------------------------
The image of the get file dialog is incorrect. The Select Initial View
and Read Only Mode options are not part of this dialog.

