Community
Tom,
(if (desired textstyle)
(set textstyle as current)
(create textstyle)
);endIF
Now, lets have a closer look at this efficiency...
Program Writing Design Guidelines:
1) Do an internal search of the font style before going to exterior sources.
2) When no style is internally found, the support path is automatically used
in conjunction with the style command.
Please note the following conditions may be true:
a) Font file desired is not in support path.
b) When user input, font may be misspelled (create a list of choices instead).
Now we have to protect the program from crashing due to the possible errors shown above.
Employ FINDFILE first, to see if file exists, before starting the style command.
Create a prompt or alert message when the font file does not exist in the support path.
======================================
Now, to create a realistic environment, the following has been simplified for this example:
a) We have Five major divisions in our symbol library.
Each folder is declared in the support path and each folder contains 100 files.
b) We also have a "SHX" font folder with over 150 files.
c) We also have a "True Type Font" folder with over 500 files.
d) Other standard support path items can be summed up to around 50 files.
The threads you mention will have to browse some 1200 external files each time this font is called forward.
Now may I ask you what geometry is the most efficient?
======================================
The successful creation of this macro will not require an error handler.
Since no error handler, place macro in the "MNL" file.
======================================
My environment can instantly toggle between Drawing Scales while remaining in the same file!
We can have up to three unique drawing scales, which requires a minimum of four settings
to align for each drawing scale. One of these is the TEXTSTYLE switch.
The base drawing scale can be set to a minimum of 5 unique (permanent) drawing scales.
The other two unique drawing scales have 5 choices also.
This equals 125 possible combinations of drawing scales available in one drawing file!
Publishing the document will yield consistent text heights regardless of scale.
Scot-6
Message was edited by: Scot-65
(if (desired textstyle)
(set textstyle as current)
(create textstyle)
);endIF
Now, lets have a closer look at this efficiency...
Program Writing Design Guidelines:
1) Do an internal search of the font style before going to exterior sources.
2) When no style is internally found, the support path is automatically used
in conjunction with the style command.
Please note the following conditions may be true:
a) Font file desired is not in support path.
b) When user input, font may be misspelled (create a list of choices instead).
Now we have to protect the program from crashing due to the possible errors shown above.
Employ FINDFILE first, to see if file exists, before starting the style command.
Create a prompt or alert message when the font file does not exist in the support path.
======================================
Now, to create a realistic environment, the following has been simplified for this example:
a) We have Five major divisions in our symbol library.
Each folder is declared in the support path and each folder contains 100 files.
b) We also have a "SHX" font folder with over 150 files.
c) We also have a "True Type Font" folder with over 500 files.
d) Other standard support path items can be summed up to around 50 files.
The threads you mention will have to browse some 1200 external files each time this font is called forward.
Now may I ask you what geometry is the most efficient?
======================================
The successful creation of this macro will not require an error handler.
Since no error handler, place macro in the "MNL" file.
======================================
My environment can instantly toggle between Drawing Scales while remaining in the same file!
We can have up to three unique drawing scales, which requires a minimum of four settings
to align for each drawing scale. One of these is the TEXTSTYLE switch.
The base drawing scale can be set to a minimum of 5 unique (permanent) drawing scales.
The other two unique drawing scales have 5 choices also.
This equals 125 possible combinations of drawing scales available in one drawing file!
Publishing the document will yield consistent text heights regardless of scale.
Scot-6
Message was edited by: Scot-65
Scot-65
A gift of extraordinary Common Sense does not require an Acronym Suffix to be added to my given name.
Tom,
We are getting close.
The original poster' wanted hints as he himself has little expierence with LISP.
I did not originally want to go into detail any more than necessary.
Nobody is wrong here.
=====================
We have over 3000 archived documents available to our customers.
Many of them generated in R12 and R14.
Many of them drawn by hand.
Before I overhauled the menu system, the standard text was set to a height of 4-1/2 inches. The new standard we now use is 4 inches (modelspace). We do not employ the variable TEXTHEIGHT. Therefore, all of our styles are declared with a fixed height greater than zero (0). Oh, the beauty of many items to customize...
The macro has accounted for this new setting to a previous file that will now be released to the new customer. Not only does this macro test for an existing declared textstyle, it will also check the declared height. If one or the other does not pass, reload style.
When was the last time you waited for the mouse box to appear after typing STYLE? It has not changed since R13 (TTF files).
When was the last time your associates loaded a textstyle with the wrong height (relative to drawing scale)?
Scot-65
---------------------------
DCouch here is the code ("H1" is our regular text):
(if (and (tblsearch "style" c)
(= (rtos (cdr (assoc 40 (tblsearch "style" c))) 2 2) d) )
(setvar "textstyle" c)
(progn
(if (findfile "H1.shx")
(setq e "H1.shx")
(progn
(setq e "txt.shx")
(alert (strcat
"The font file called \"H1.shx\" is not in your support path."
"\nA default font file will be used instead.")) );progn
);if
(setvar "cmdecho" 0)(command ".style" c e d "" "" "" "")
(setvar "cmdecho" 1)(princ (strcat "\n" c " textstyle loaded. ")) );progn
);if
Where "c" and "d" is passed to this menu function as the style with desired height (chosen from a list).
See my above post for hints of other switches to set when changing drawing scales within a file (also incorporated in this same menu function macro).
If your environment declares text styles with a height of 0, do Kent's method (ensure a routine accounts for the desired height without the User entering a value).
[see if ya'll can find the bug I purposely designed into this routine]
It is only fair to give back to this fourm as much as it is to extract.
Scot-65
We are getting close.
The original poster' wanted hints as he himself has little expierence with LISP.
I did not originally want to go into detail any more than necessary.
Nobody is wrong here.
=====================
We have over 3000 archived documents available to our customers.
Many of them generated in R12 and R14.
Many of them drawn by hand.
Before I overhauled the menu system, the standard text was set to a height of 4-1/2 inches. The new standard we now use is 4 inches (modelspace). We do not employ the variable TEXTHEIGHT. Therefore, all of our styles are declared with a fixed height greater than zero (0). Oh, the beauty of many items to customize...
The macro has accounted for this new setting to a previous file that will now be released to the new customer. Not only does this macro test for an existing declared textstyle, it will also check the declared height. If one or the other does not pass, reload style.
When was the last time you waited for the mouse box to appear after typing STYLE? It has not changed since R13 (TTF files).
When was the last time your associates loaded a textstyle with the wrong height (relative to drawing scale)?
Scot-65
---------------------------
DCouch here is the code ("H1" is our regular text):
(if (and (tblsearch "style" c)
(= (rtos (cdr (assoc 40 (tblsearch "style" c))) 2 2) d) )
(setvar "textstyle" c)
(progn
(if (findfile "H1.shx")
(setq e "H1.shx")
(progn
(setq e "txt.shx")
(alert (strcat
"The font file called \"H1.shx\" is not in your support path."
"\nA default font file will be used instead.")) );progn
);if
(setvar "cmdecho" 0)(command ".style" c e d "" "" "" "")
(setvar "cmdecho" 1)(princ (strcat "\n" c " textstyle loaded. ")) );progn
);if
Where "c" and "d" is passed to this menu function as the style with desired height (chosen from a list).
See my above post for hints of other switches to set when changing drawing scales within a file (also incorporated in this same menu function macro).
If your environment declares text styles with a height of 0, do Kent's method (ensure a routine accounts for the desired height without the User entering a value).
[see if ya'll can find the bug I purposely designed into this routine]
It is only fair to give back to this fourm as much as it is to extract.
Scot-65
Scot-65
A gift of extraordinary Common Sense does not require an Acronym Suffix to be added to my given name.
![Autodesk Design & Make Report](https://forums.autodesk.com/t5/image/serverpage/image-id/1350519iCB55845EBFC43016/image-size/large?v=v2&px=999" "Autodesk Design & Make Report")
