| 1. |
Are Aardvark Software
products guaranteed? |
|
Yes. Aardvark Software is so sure that
you will like our products that we offer a 90-day money back guarantee if you are
unsatisfied. |
| 2. |
Which
versions of Windows are supported by Aardvark Software products? |
|
Aardvark Software products work
with Windows 95/98/ME, NT 4.0, and Windows 2000 and XP. |
| 3. |
Which versions of Visual
Basic are supported by Aardvark Software products? |
|
Aardvark Software's products
support Microsoft Visual Basic 3.0, 4.0, 5.0 and 6.0. |
| 4. |
Are Aardvark Software
products Year 2000 Compliant? |
|
Yes. For more information, see
our Statement of Year 2000 Compliance. |
|
Pretty
Printer |
| 1. |
What does
Pretty Printer do? |
|
Pretty Printer prints Visual
Basic code. You can also browse through the code on the screen, but the heart of Pretty
Printer lies in the printing. Based on user settings, Pretty Printer prints clear,
eye-pleasing code that is ideal for tracking down bugs or impressing clients. |
| 2. |
Do I need
a color printer to run Pretty Printer? |
|
No. While a color printer makes
the print-outs look nicer, a laser printer will work fine. Many of Pretty Printer's most
critical features (AutoIndent, Connection Lines, Procedure Separators) look just as good
on a laser printer as they do in color. Gray shadowing can be used if desired. |
| 3. |
Does Pretty Printer
produce an index or cross reference? |
|
Pretty Printer can produce a Table of
Contents for an entire project, or a procedure-by-procedure Table of Contents. However, it
does not produce a symbol or procedure cross-reference. |
| 4. |
How can I automatically
print a file when Pretty Printer starts? |
|
To print a file when Pretty Printer
starts up, simply put that file on the command line (like in Microsoft Word or the Edit
program in DOS). This is done with the following call on the command line:
C:\path\vbpp32.exe c:\path\vbfile.extension |
| 5. |
Does Pretty Printer allow
the user to customize settings? |
|
Yes. Users can specify how to
display the code both on the screen and when it prints. Although display is not the main
intent of Pretty Printer, users can customize the on-screen colors, indentation, fonts,
and other code display options. For printing, users can customize the headers and footers
on each page, several aspects of the layout, the colors, and the fonts. |
| 6. |
Does Pretty Printer have
the capability to print only new or updated files? |
|
Yes. If a user prints out a large project
and later updates only a few modules, for example, Pretty Printer lets the user print out
only the updated files. However, it will not interleave the new pages into the old ones. |
| 7. |
Does Pretty Printer
support selective printing? |
|
Somewhat. While the user is not able to
highlight a given block of text and print that, Pretty Printer does let the user choose
what parts of the code they want. The user can print only certain pages, only certain
procedures, only the form definition, only the actually code, the attributes, etc. |
| 8. |
What are the new features
in Pretty Printer 6.0? |
|
Pretty Printer 6.0 adds several new and
helpful features...
 | Support for Visual Basic 6.0 |
 | 1000+ new keywords |
 | Support for new file structures |
|
 | HTML Output |
 | Loads full files |
 | Updated Help file |
|
|
|
Polisher |
| 1. |
What does
Polisher do? |
|
Polisher takes any Visual Basic code
file, lets the user customize the reformatting options to comply with their standards
(personal or company), and then reformats the file. The output is perfectly formatted
source code that is ideal for tracking down bugs on the screen and maintaining the code.
You can save the output. |
| 2. |
Does Polisher support
user customized settings? |
|
Yes. In fact, the first thing the user
sees after the splash screen is a choice of options. The user can customize virtually any
part of the code reformatting process with the 11 categories of options. These range from
White Space, to Comment Blocks, to Indentation, to basically anything else the user could
possibly want to change. |
| 3. |
Does Polisher have a
print capability? |
|
Polisher can work in conjunction with
Pretty Printer to print source code. |
| 4. |
What spell-checking can
Polisher do? |
|
Polisher can spell-check comments,
literals in code, and literals in forms and controls (e.g., captions). It knows to ignore
VB keywords. However, if a user does not want spell-checking, it is easy to disable. |
| 5. |
Does Polisher support
automated comment block creation? |
|
Yes. Polisher lets the user define three
levels (module, events, user-defined procedures) of comment blocks that will automatically
be inserted into the code when it is polished. With the Comment Block Definition tool, the
whole process of creating comment blocks is made easier. |
| 6. |
What kinds of
reformatting/conversion does Polisher do? |
|
Polisher has a wealth of reformatting
options. It can automatically indent code within a loop or If
statement, it can put all the data type declarations (e.g., As
Integer) in a designated column so they all line up, it can delete consecutive
blank lines that exceed a user-defined number, and it can add line continuations if the
number of characters in a line exceeds a user-defined number.
Polisher also has a number of conversion tools. It can convert DAO calls from
version 2.0 from 3.0, it can convert Dim to Private and Global to Public in General Declarations sections, and it can convert MsgBox calls to use intrinsic constants. |
| 7. |
Can Polisher rearrange code? |
|
Yes. Polisher can rearrange declarations
within a procedure. The user is in almost complete control of what the sorting order is
(and can disable rearranging altogether), and can arrange the declarations by scope,
alphabetical order, data type, etc. Polisher can also rearrange procedures within a
module. |
| 8. |
What's new in Polisher 6.0? |
|
Polisher 6.0 has many new features that
make it even more convenient and user-friendly...
 | The ability to sort Procedures and variable declarations |
 | Support for Visual Basic 6.0. |
 | 1000+ keywords added |
 | Y2K scan |
|
 | Additional control over white space |
 | More whitespace options |
 | Ability to line number code |
 | Ability to insert error handling |
 | Ability to insert module entry & exit routines. |
|
|
|
Other Questions |
|
If you have any other questions, either
go to the feedback page, or send email to . |