Documentos de Académico
Documentos de Profesional
Documentos de Cultura
SpecChecker for V8
Perform quality assurance checks on your
MicroStation files quickly and easily!
Version 8.11
Axiom
1805 Drew Street
Clearwater, Florida 33765
1-727-442-7774 voice
1-727-442-8344 fax
AxiomInt@AxiomInt.com
www.AxiomInt.com
Page 2
SpecChecker
Chapter 1 Introduction
Table of Contents
Chapter 1 Introduction--------------------------------------------------------------------- 7
The purpose of SpecChecker -----------------------------------------------------------------------7
SpecChecker allows you to ----------------------------------------------------------------------7
Correcting elements automatically-----------------------------------------------------------------8
Analyzing element characteristics -----------------------------------------------------------------9
Analyzing level characteristics in level tables-------------------------------------------------- 10
Chapter 2 Installation----------------------------------------------------------------------11
General instructions-------------------------------------------------------------------------------- 11
Before you install ---------------------------------------------------------------------------------- 11
Typical installation from CD --------------------------------------------------------------------- 11
Congratulations------------------------------------------------------------------------------------- 17
Page 3
Page 4
SpecChecker
Chapter 1 Introduction
Page 5
------------------------------------------------------------------------- 52
------------------------------------------------------------------------------ 54
---------------------------------------------------------------------- 57
Page 6
SpecChecker
Chapter 9 Troubleshooting--------------------------------------------------------------61
Errors not covered in the document-------------------------------------------------------------- 61
Chapter 1 Introduction
Page 7
Identify every design file element that does not conform to your CAD standards.
Interactively visit (and edit) the elements that do not conform to your standards.
Reduce revisions by guaranteeing that drawings are correct before they are plotted.
Page 8
SpecChecker
Level
Color
Weight
Style
Priority
Transparency
Font
Text Height
Text Width
Text Justification
Fill color
Class
Invisible property
Global Origin
And more!
See the RuleManager System Administrators Guide section How Elements are
Corrected for a complete description of how SpecChecker corrects elements.
Chapter 1 Introduction
Page 9
Level
Color
Weight
Style
Type
Font
Class
Fill color
Cell names
Rotation angle (cells, shared cells, text, text nodes, arcs, ellipses) (2D files only)
Number of vertices
Text justification
Page 10
SpecChecker
Various information about the parent element of a component element (e.g. parent
type, parent level, parent color, location of the parent element) A parent element is
the complex header of a component element.
And more!
Level name
Level number
Level Description
Priority
Transparency
Global Display
Global Freeze
Plot
Lock
SpecChecker allows you to check and correct level characteristics of both master file
levels and the levels of reference files attached to the file.
Chapter 2 Installation
Page 11
General instructions
This version of SpecChecker requires MicroStation Version 8.1 or later.
A license file on floppy disk for the product(s) you are about to install.
Please shut down all MicroStation sessions on your computer before continuing.
Page 12
SpecChecker
3. Click the [OK] button and the first installation dialog box (below) will appear.
6. These instructions will describe only the Typical installation path. Choose
Typical and click [Next].
Chapter 2 Installation
Page 13
7. Choose the license file for this installation. Toggle on I have a license file
somewhere else. And press [Next].
8. Browse to the axiom.lic file on the CD and click [Open]. The licenses in the
specified license file will display in the next dialog box. Press [Next].
Although you have already selected the MicroStation family (V7 or V8) for which
you want to install Axiom tools, it is common for one computer to have more than
one instance of MicroStation installed on it. For example, you might have two
versions of MicroStation/J installed (07.01.04.16 and 07.02.04.20). You must choose
which of the two you want to associate your Axiom tools with.
Page 14
SpecChecker
9. Highlight the version of MicroStation you want to associate the Axiom tools with and
click [Next].
Since this is a Typical installation, all programs for which an Axiom license was
found will already be checked-on to be installed. Other items that are also
automatically checked-on for installation are the product Users Guides, individual
product sample files and Axioms MicroStation pull-down menu.
Chapter 2 Installation
Page 15
Page 16
SpecChecker
If you accept the license and click [Next], the installation will begin. You can click
[Cancel] at any time to abort the installation.
Chapter 2 Installation
Page 17
13. This is the final dialog box. It shows that the installation is complete. By default the
View Readme.pdf option is toggled on and will display the Readme.pdf document
when you click [Finish].
Congratulations
Thats it! You have successfully completed the installation of your Axiom tools.
Page 18
SpecChecker
Page 19
Prerequisites
1. MicroStation V8 version 8.1 or later.
2. SpecChecker must be installed on your computer. To start SpecChecker, select the
Axiom menu from MicroStations main menu bar, then select SpecChecker. If
SpecChecker does not appear in the Axiom menu, follow the instructions in the
Installation section of this Users Guide.
Sample Files
To help you get started, SpecChecker comes with some sample files (V8 design files and
SpecChecker rules files). In most cases, these sample files will be located in the
c:\Program Files (x86)\Axiom\V8\Checker\sample\ directory.
These sample design files and their corresponding rules files are described in the
following table:
Design File
Rules File
Description
checker.dgn
checker.rul
Demonstrates common
SpecChecker commands and
keywords.
text_justification.dgn
text_justification.rul
Demonstrates SpecChecker
keywords related to text
justification.
models.dgn
models.rul
Demonstrates keywords
related to V8 models.
Note: These sample rules files were designed only to report on non-conforming
elements, not correct them. This is so that new SpecChecker users can use the sample
files multiple times until they are familiar with SpecChecker. If SpecChecker were to
Page 20
SpecChecker
correct those elements the first time through, you would not be able to ride the ride
again.
Demonstration Version
Demonstration versions of SpecChecker allow you to process 500 design file elements.
Licensed versions of SpecChecker do not have this restriction.
The Basics
When should I use SpecChecker?
To detect, report and correct elements in your design files that do not comply with your
project standards. You tell SpecChecker what your project standards are. SpecChecker
shows you all the elements that do not comply with those standards. SpecChecker can
also correct most of the errors it finds according to the rules you defineautomatically!
Lets say that for a certain project all text on level A-ANNO-TEXT should be yellow.
Just create a file (using any text editor or SpecCheckers Rule Wizard tool) describing
this standard. Then tell SpecChecker which design files you want to check for
compliance. SpecChecker then reads your standards file and checks your design files
against those standards. SpecChecker creates a complete report of all detected noncompliances. Not only that, SpecChecker can correct many violations automatically
according to your instructions! For example, it might change all the blue text on level
A-ANNO-TEXT to yellow and move all the red text on level 19 to level 29.
This Quick Start will introduce these features to you.
Page 21
Page 22
SpecChecker
3. If the file names in your dialog box do not match the names in the image above,
select these files now. You can type their names in directly or use the {Edit List...}
and {Select...} buttons to select these files. You may have SpecChecker create the
Report file in the directory of your choice. See the section titled Choose Files to
Process for information on how to select files after you click the {Edit List...}
button.
You will be checking the design file checker.dgn against the rules file
checker.rul. For the purpose of example, this rules file will reject the majority of
the elements in the design file. No automatic corrections will be made.
4. If it is checked on, uncheck the Interactive editing checkbox in the main dialog
box.
5. You are now ready to start SpecChecker. Press the {Start} button. You will see the
main dialog box extend down slightly to display summary data during processing.
6. When the processing is done, you will see an information box that says Processing
complete. Press {OK} to close this box.
7. Now press the {Display Report} button. You will see a detailed report of the nonconforming elements (those that do not comply with the sample standards defined in
checker.rul).
8. Here is an excerpt from the checker.rep report file that should be created. This
excerpt shows just the element details. Report header and footer information has been
omitted.
4000113,
4000114,
4000115,
4000116,
4000117,
4000118,
4000119,
4000120,
4000121,
4000122,
4000123,
4000126,
4000127,
4000129,
ID=0
ID=0
ID=0
ID=0
ID=0
ID=0
ID=0
ID=0
ID=0
ID=0
ID=0
ID=0
ID=0
ID=0
---------------
Level = A
Level = B
Level = C
Text height (1.5000) should not exceed 1.0mu.
Text width (1.5000) should not exceed 1.0mu.
Font (1025) must be 3 (ENGINEERING).
Font (1) must be 3 (ENGINEERING).
Font (0) must be 3 (ENGINEERING).
Weight = 1
Weight = 2
Weight = 3
Color (3) must be ByLevel.
Rotation (89.0000) must be 0 or 90.
Rotation (91.0000) must be 0 or 90.
Page 23
2. Press the {Start} button. SpecChecker will open the selected design file and begin
checking it interactivelytaking you to each non-conforming element.
3. The SpecChecker interactive editing box below tells you that an element in the design
file violates one of the rules in the sample checker.rul rules file.
The Message: field describes the specific non-compliance detected by
SpecChecker. In our example, SpecChecker simply reports that this element was
found on level A.
4. Press the {Blink} button to cause the non-conforming element to blink on the screen
so you can see it clearly.
Page 24
SpecChecker
5. Keep pressing the {Ignore} button and looking at the rejected elements. Blink them if
you are not sure which element is being rejected. Be sure to read the contents of the
Message: field for each rejected element to find out what caused it to be rejected.
You will find elements rejected based on such characteristics as level, text height and
width, font, weight, color and rotation angle.
6. When you have visited every non-conforming element in checker.dgn, you will see
an Information box saying Processing complete. Press {OK} to close this box.
7. Press the {Display Report} button and view the report file. Each element that you
visited in interactive editing mode will be mentioned in the report file, along with the
message telling you exactly what was wrong with each.
Page 25
6. Here is what your main SpecChecker dialog box should look like:
7. You are now ready to start SpecChecker. Press the {Start} button.
8. SpecChecker will reject each text element in this file based on its text justification. It
will report each text elements justification value to you as it is rejected.
Page 26
SpecChecker
9. Visit the next text element in this file by pressing the {Ignore} button when you are
done with the current text element.
10. When the processing is done, you will see an Information box that says Processing
complete. Press {OK} to close this box.
11. Now press the {Display Report} button. You will see a detailed report of the nonconforming text elements you just viewed interactively.
Page 27
6. Now click on the option button labeled Models: and choose All models.
Page 28
SpecChecker
7. Here is what your main SpecChecker dialog box should look like:
8. You are now ready to start SpecChecker. Press the {Start} button.
9. SpecChecker will reject the single text element on each model in models.dgn. It will
also open each model to show you the rejected element.
10. Visit each text element in this file (one per model) by pressing the {Ignore} button
when you are done visiting each one.
11. When the processing is done, you will see an Information box that says Processing
complete. Press {OK} to close this box.
Now press the {Display Report} button. You will see a detailed report of the nonconforming elements (each text element) with its model name also reported.
Page 29
Running SpecChecker
After installing SpecChecker as described under Installation and after creating your
rules file(s) as described in the RuleManager System Administrators Guide, you are
ready to run SpecChecker.
Select SpecChecker from the Axiom menu on the MicroStation menu bar.
File | Exit
The File menu contains only the Exit option.
Page 30
SpecChecker
Settings
The Settings menu allows you to change the factory default settings and to save and
reload your personalized settings. The Change Settings options are described in
detail in the next section.
Help | Contents...
Choose this to open the Users Guide.
Help | About
This displays the current product version, license type, copyright information plus contact
information for Axiom Support, Sales and Licensing.
Page 31
Files:
Here is where you designate which design files or cell libraries you want SpecChecker to
examine. There are several ways to specify files:
Key-in the name of a single design file or cell library. For example:
c:\project\sample.dgn.
Key-in a series of design file or cell library names separated by semi-colons. For
example: c:\project1\sampleA.dgn;c:\project2\sampleB.dgn.
You can use wildcards too. For more information, see the Choose Files to Process
section of this guide.
See the section Choose Files to Process and its File | Save List As feature, which
allows you to save a list of files as a text file like Filelist.lst. In this way, you can use
the Choose Files to Process dialog box to build the list of files you want processed and
save the list of files for later.
{Edit List}
Clicking the {Edit List} button opens the Choose Files to Process dialog box, which
you can use to choose one or more files to be processed. See the section Choose Files to
Process for detailed information.
After you create a list of files to process and close the Choose Files to Process box, the
Files: field will display the number of files you selected for processing. So if you made
a list of 1,001 files, the Files: field would say <List of 1,001 files>.
Models:
Use the Models: section to define which models you want SpecChecker to process.
MicroStation V8 design files always contain a Default model. This model cannot be
deleted. MicroStation V8 design files can also contain any number of additional Design
or Sheet models.
Page 32
SpecChecker
Model Type
Choose the model type you want SpecChecker to process. The default is {Active model}.
Rules File:
Enter the name of a rules file to use for processing the selected design files. You can
enter the name of a MicroStation Settings Manager parameter file (a .stg file) in place
of a rules file. By processing a .stg file, SpecChecker can check your design files
against the same standard used to define your Settings Manager lists.
Use the {Select...} button to the right of the Rules file: field to browse for a specific
rules file. To browse for a .stg file, change the option button under the List file of
type: label to read All files (*.*)
The default folder in MicroStation that contains Settings Manager .stg files is
...\MicroStation\Workspace\System\data\
Page 33
When you save SpecChecker settings, the selected rules file or .stg file name is saved
in the current SpecChecker settings file.
Tip: Using a .stg file by itself to check design files rejects design file header elements
and other non-graphic elements. You can eliminate this by using a rules file that accepts
non-graphic elements and contains a #include rule with the path, name and extension of
the .stg to be used. See the RuleManager System Administrators Guide for
information about using the #include command.
Report File:
SpecChecker writes the results of the examination to a plain text report file. Any legal
filename can be specified. If the file already exists, it will be overwritten.
SpecChecker allows you to either have one report file for all design files processed in one
run or one report file for each design file processed.
{Select}
Use the {Select} button to choose a specific report file by browsing for it.
Page 34
SpecChecker
Search only
Suppress SpecCheckers ability to automatically correct elements. In interactive editing
mode, this will cause the {Change...} buttons to be disabled. In automatic (noninteractive) mode, no corrections will be made. The net effect is that SpecChecker will
search your files for problems (and report on them) but it will not correct them.
In this mode, no backup files will be created.
If your rules file does not specify any automatic corrections, this option is not applicable.
Interactive editing
This option gives you the capability of visiting each element SpecChecker finds that
violates your standards. SpecChecker will zoom in on the non-compliant element. If more
than one design file is specified in the SpecChecker main dialog box then each design file
will be opened in turn and checked interactively.
{Start}
Push this button when you have finished selecting all of your options and are ready to
have SpecChecker process your files.
{Display Report}
Push this button to open SpecCheckers text report file using Notepad.
Page 35
The numbers before the -- or ++ indicate the file position and unique V8 element ID
of the rejected element. The part after the -- or ++ is the rejection message defined in
the rules file.
{Close}
There are several special messages that will be in the report file under the following
circumstances:
When a correction command modifies one or more (but not all) components of a complex
header youll see messages such as (V7 example shown):
24
24
24
24
24
24
24
24
---------
Components
Components
Components
Components
Components
Components
Components
Components
element
element
element
element
element
element
element
element
In most complex elements all components must share the same symbology. If you change
the level, color, weight or style of one or more components but not all of the components
in a complex element, the above messages will notify you that the components no longer
match. Text justifications and multipliers must also match for all text in text nodes.
Page 36
SpecChecker
++
++
++
++
++
++
++
++
Headers
Headers
Headers
Headers
Headers
Headers
Headers
Headers
Again, these messages do not apply to cells and shared cells because cell component
elements are allowed to have varying characteristics within the same cell.
Page 37
Settings menu
The Settings menu gives you control over SpecCheckers settings and settings files.
Change Settings
Change Settings opens a dialog box where you can access all of SpecCheckers
settings.
Load Settings
Use the Load Settings... option to load a settings file that you have saved previously.
Save Settings
Use the Save Settings option to save your current SpecChecker settings to the current
settings file.
Save Settings As
Save your current settings to an alternate SpecChecker settings file and make that settings
file active.
Page 38
SpecChecker
Settings File:
The Settings File: line displays the currently loaded Settings file. Clicking on it has
no effect except that it causes the Settings menu to close.
General Settings
This is where you change general SpecChecker settings.
Interactive editing
This option lets you visit each element that violates your standards. SpecChecker will
zoom in on the non-compliant element.
For more information about this option, see the Interactive Editing section of this
guide. This option is off by default (unchecked.)
Page 39
Search only
Use this to disable any automatic corrections defined your rules file. The full, detailed
report file will still be created.
This option defaults to Off, no checkmark.
Tip: Since this is a commonly used option, it is also located in the main dialog box.
Page 40
SpecChecker
First
When you select First, SpecChecker stops processing the element after the first violated
rule.
Tip: If you have speed considerations then set this to First. This can speed up
processing significantly.
It may be useful to set SpecChecker to "First" and "Search only" when you just want to
know if designs are "perfect" (no violations) or not. This may be especially useful if you
are processing many files and are not interested in what the specific standards violations
are.
Last
In interactive mode, SpecChecker will create a temporary list of all rules violated by an
element and present only the last one found.
In non-interactive mode, SpecChecker will create a list of all rules violated by the
element and report/correct only the last one. Only the last rule violated by each element
will be reported (and therefore be available for automatic correction).
All
In interactive mode, each violation is reported until the element passes all rules or you
have chosen to ignore all remaining violations.
In non-interactive mode and when not using the Search Only option, each element will
be compared against each rule in the rules file and the first rule violated that contains a
correction clause will update the element. Then the updated element will be passed
against all rules again from the first rule. If a second violation is found, the cycle begins
again. If a violated rule does not contain a correction clause, or SpecChecker is running in
Search only mode, or if you choose Ignore in interactive mode, the rejection message
will be written to the report file, and the next rule will be processed.
When no more rules remain on the list, SpecChecker processes the next element.
Symbology:
Elements can have one of two types of symbology:
Element Symbology
As Displayed
Element
This is the default. If you choose Element then each elements actual symbology will
be tested by SpecChecker. Level Symbology and ByLevel symbology will be ignored.
Page 41
As displayed
If you choose As displayed then each elements displayed symbology will be tested by
SpecChecker. This could include any combination of Element Symbology, Level
Symbology or ByLevel Symbology for any given element.
SpecChecker will see elements exactly as they are displayed in the active view, whether
their display is based on their Element,Level or ByLevel symbology (or any combination
of these.)
Highlight color
This option allows you to specify the highlight color when SpecChecker is highlighting
the element in interactive editing mode. There is a color palette to select from. This
option is only active/useable if Interactive | Highlight or fence each element is selected.
Page 42
SpecChecker
Limitations
Here you can define limitations on how many rejections are reported by SpecChecker.
Page 43
Rules Files
This is where you change settings related to how SpecChecker handles rules files.
Page 44
SpecChecker
Report File
This is where you change settings related to SpecCheckers report file.
Page 45
This list of settings will be repeated for every model processed, which can make your
report larger and thus harder to read.
Only turn this on if you actually need this information in your report file.
Page 46
SpecChecker
The interactive editing dialog box allows you to choose which predefined corrections you
want to perform. SpecChecker will zoom in on the element that violates your standards.
You can then choose to make the correction specified in the rule that has been violated or
use any MicroStation function to manually change the element yourself.
If more than one design file is specified in the SpecChecker main dialog box then each
design file will be opened in turn and checked interactively.
Note: When running in interactive editing mode on cell libraries, be sure to choose All
models from the main SpecChecker dialog box. Each cell in a MicroStation V8 cell
library is in its own model.
Rule
Here is where SpecChecker displays the actual rule that is in the rules file or the setting in
the Settings Manager .stg file that is being violated. In the example above, an element
on level A was rejected.
Page 47
Message
This is the message defined in your rules file for whichever rule has been violated. In the
case of .stg files (instead of SpecChecker rules files), this is a general message about
the element that violated the settings in the .stg file.
Correction
This displays the correction that will be made if you press the Current Element
{Change} button.
If no correction is specified in your rules file for the rule which has been violated, this
will say <None>.
{Ignore} means dont make the correction for this element and go to the next noncompliant element.
{Change} means make the specified correction and go to the next non-compliant
element.
{Blink}
This allows you to flash the rejected element. This helps you locate (or re-locate) the noncompliant element when there are other elements around or covering it.
Page 48
SpecChecker
{Undo}
This button allows you to undo the last change to this design file. This could be either the
last change by the {Change} button or what you did directly within MicroStation. If you
have not made any changes, the button will be grayed out as shown here.
Note: Whenever you are highlighting the element and you want to undo any changes
you have done, you will need to press the undo button twice. The first time you press the
undo button the element will change to the highlight color and the second time the
element color will be restored to its original color.
{Quit}
Pressing this button stops examining the design file and takes you back to the main
SpecChecker dialog box.
Current Model
The Current Model options allow you to select three options specific to the current
model in the design file being processed.
This will cause SpecChecker to ignore the rule that causes this element to be rejected for
the rest of the elements in that model.
Page 49
Correct all elements in this model that violate this rejection rule. Whenever this rule is
found to be violated the correction clause in the rule will be automatically executed in
this design file only.
If no correction is specified for this rule in your rules file or if you are running
SpecChecker in Search only mode, this button will be deactivated.
Correct all elements in this model that violate any rejection rule. All correction clauses
will be automatically executed as each element is analyzed.
File:
This is the current file that is being checked by SpecChecker. It is the active design file.
Element ID:
This is the unique V8 element ID of the non-conforming element currently being
displayed.
Page 50
SpecChecker
Page 51
Page 52
SpecChecker
By dragging and dropping them from Windows Explorer into the Files to Process
list. You can open a Windows Explorer window using the
button.
By importing an existing ASCII text file with files listed in it using File | Import File
List
Browse ProjectWise
Click on this button or press {Ctrl-P} to open the Axiom ProjectWise Navigator box.
You will be prompted to log into a ProjectWise datasource.
Page 53
Browse your ProjectWise datasource, select the files you want and press {Add to List}. No
files are shown in the above picture but youll see files once you log into a datasource.
Here you simply select the files you want to process and press {Add to List} to add them
to your list of files to process. You can also right-click and choose Add Files to List to
get the same result.
When you are done adding files to your list of files to process, press {Close}.
Page 54
SpecChecker
Select one or more files and press {Open} to add them to your list of files to process.
Page 55
Search in:
Choose the folder you want to search for files in. Click the Choose a folder to search
button
Include subfolders.
Enable this if you want to search for files in subfolders too.
Page 56
SpecChecker
{Search Now}
Once you have made your file search choices, click {Search Now} to perform the search.
When the search is done, you will see a count of the number of files found. Press {Add
Files} to add the files to your list of files to process.
{Add Files}
After searching for files, press this button to add the found files to your list of files to
process.
{Close}
Press this button to close the Search for Files box.
Here you can choose any number of folders to search by checking them on in the folder
tree.
Page 57
Page 58
SpecChecker
Files to Process
The object of this entire box is to put files in the Files to Process list.
Using {Shift-left-click}
You can select multiple adjacent files in the list by first left-clicking on the first file then
holding down the {Shift} key while left-clicking on the last file in the series.
Using {Ctrl-left-click}
You can select multiple files arbitrarily by holding down the {Ctrl} while left-clicking on
each one.
Page 59
button.
2. Select one or more files and right-click on one of them, then choose a removal option
from the menu which appears.
3. Select one or more files and press the {Delete} key on your keyboard.
4. Click the {Remove all files}
button.
Version
Right-click on the title bar and choose About Axiom File List Processor to bring up a
box containing version information which is useful if you are calling Axiom for support.
{OK}
Once you have chosen all the files you want to process, press {OK} to close the Choose
Files to Process box.
{Cancel}
If you change your mind, press {Cancel} and any changes you made to your list of files
to process will be discarded.
Advanced Commands
The Choose Files to Process box is extremely powerful and easy to use. However, for
those users who want more raw power, it is possible to create a list of files to process
without even picking up your mouse.
Instead of opening the Choose Files to Process box, you can type wildcards and other
special commands directly in the file specification field in the main dialog box of the host
program (for example, FileFixers Which Files: field.)
Using these commands, your list of files to process will be created automatically when
you start processing. Or you can open the Choose Files to Process box to view and edit
your list of files before you begin processing them.
Page 60
SpecChecker
Command
*
Examples
c:\work\*.dgn
c:\work\*.*
c:\work\project1.*
Description
c:\work\project1.dg?
c:\work\project?.d??
c:\work\?project?.dgn
/S
c:\work\*.dgn /S
c:\work\border*.dgn /S
c:\work\project?.dgn /S
/L
/L c:\work\list.lst
Chapter 9 Troubleshooting
Page 61
Page 62
SpecChecker
Page 63
Additional Enhancements
Made some minor changes to labels in the user interface.
LEVEL_OVERRIDE_STYLE
Page 64
SpecChecker
LEVEL_DISPLAY
LEVEL_OVERRIDE_WEIGHT
LEVEL_FREEZE
LEVEL_PLOT
LEVEL_LOCK
LEVEL_PRIORITY
LEVEL_NAME
LEVEL_SCALE_LS
LEVEL_NUMBER
LEVEL_STYLE
LEVEL_OVERRIDE_COLOR
LEVEL_TRANSPARENCY
LEVEL_OVERRIDE_SCALE_LS
LEVEL_WEIGHT
List of new keywords to isolate the level table a level is associated to:
LEVEL_FILENAME The name of the file a level is associated to.
LEVEL_REFLOGICAL The logical name of the reference file a level is associated to.
LEVEL_TYPE The type of file, either Master or Reference, that a level is
associated to.
Additional Enhancements
New! Added support for font type in the FONT keyword.
New! Added a model name filter that allows users to choose specific models within a
model type category.
Page 65
Page 66
SpecChecker
Page 67
Improved the messages to the user when incorrect rules syntax is used.
Fixed several problems when loading the rules file before processing
Page 68
SpecChecker
Large rules files (thousands of lines) can now be loaded in seconds rather than minutes.
This also means that it is now more practical to use larger rules files than ever, by a factor
of hundreds.
AxiQA.dll has been replaced with separate DLLs for V7 and V8: AxiQAV7.dll and
AxiQAV8.dll. This should have no effect on users.
Added {Help} buttons throughout the product.
Added AxiRange.dll.
Added Help | Quick Start menu item.
Add Help | What's New? menu item.
Added the ability to handle rules files with UNIX line endings.
Renamed JUST keyword JUSTIFICATION.
Removed MASTER_UNIT correction keyword. It was dangerous and unnecessary.
Page 69
Page 70
SpecChecker
LEVEL_WILDCARD
LEVEL_REGEXP
STYLE_WILDCARD
STYLE_REGEXP
Page 71