List of Known RILSIM Bugs |
Display ProblemData forms did not display at full width if the computer's display
had been set to use Large Fonts (120 dpi resolution) rather than the default setting of
Small Fonts (96 dpi resolution). For a detailed description, see this page.
|
1.05 |
Fixed in version 1.06 |
August 2003 |
Improperly Formatted Numeric DisplayIn the Personnel and Equipment Assignment data forms
associated with an Activity data record, piece rate costs were displayed using the number
of digits to the right of the decimal place specified for time-based costs, rather than the
number of digits to the right of the decimal place specified for piece rates.
|
1.05 1.06 |
Fixed in version 1.07 |
January 2004 |
Difficulty Index Worksheet ErrorIn the Difficulty Index worksheet, if the OK
button was pressed while the cursor remained over a newly entered quantity in the Difficulty
Index column, the worksheet row corresponding to that entry was lost and the weighted-average
difficulty index was incorrectly calculated.
|
1.05 1.06 |
Fixed in version 1.07 |
January 2004 |
Activity Sorting Error—The list of activity names is sorted immediately before each
simulation run in order to ensure that calculations are carried out in the order in which
the activities would be implemented. Under certain circumstances it was possible for an item
within this list to receive an out-of-bounds index number. This caused a runtime error within the
sorting routine and shut down RILSIM. The indexing problem could occur when the user reordered
activities, either on the Activity Data Form or within the Activity Chart. Specifically, the error
occured when the user moved an activity without subsidiaries in such a way that
it then became the parent of Activity 1 (i.e., Activity 1 became its subsidiary).
This caused the index mentioned above to receive an out-of-bounds value, and when the user attempted
to run the scenario a runtime error occurred, shutting down RILSIM.
|
1.05 1.06 |
Fixed in version 1.07 |
January 2004 |
Activity Renaming Error—In some situations a programming error in the routine that supports
renaming of activities within the Activity Chart caused a runtime error and shut down RILSIM when the user
attempted to rename an activity. This only occurred within the Activity Chart, not on the main Activity data form.
|
1.05 1.06 |
Fixed in version 1.07 |
January 2004 |
Decimal-Point Symbol ErrorUnder certain circumstances it was possible to inadvertently
change the decimal-point symbol for an analysis. This could happen as follows:
- A RILSIM database was opened or created.
-
While the first database remained in memory, a second RILSIM database was opened or
created within the same instance of RILSIM, and the second database used a
different symbol for the decimal-point character.
For example, the first RILSIM database might use a comma as the decimal-point symbol and the
second database might use a dot (full stop or period).
This sequence of events would cause the decimal-point symbol for the first database to change so that
it matched the symbol used in the second database. In versions 1.05, 1.06, and 1.07 of RILSIM this
would not cause an error but it would certainly be disconcerting to the user. In RILSIM 2.00 and later
versions, however, such a change might actually cause numerical errors. This is because these later
versions permit users to select not only the decimal-point symbol but also the digit-grouping
symbol for each analysis. An unintended change in the decimal-point symbol could then cause both the
decimal-point symbol and the digit-grouping symbol for a RILSIM database to be represented by
the same character (for instance, a comma). RILSIM would then interpret the first comma
encountered in a numeric data field as the decimal-point symbol, whereas it might possibly be
intended to represent a digit-grouping character instead.
More information about the digit-grouping symbol is available here.
|
1.05 1.06 1.07 |
Fixed in version 2.00; for earlier versions, see the workaround suggested below.
This error results from the way decimal-point symbols are recognized by the Microsoft Windows
operating systems. When multiple documents are open simultaneously within a single instance of an
application, they must all use the same decimal-point symbol. We did not fully appreciate this
limitation when RILSIM was first created.
Fix—In RILSIM 2.00 and later versions, a check is made whenever a database is
opened to ensure that its decimal-point symbol matches that of any database already open within that
instance of RILSIM. If the decimal-point symbols do not match, RILSIM displays an error message
and refuses to load the new document within the same instance of RILSIM.
Workaround—If you need to open multiple RILSIM databases simultaneously and there is a
chance that they may have been created with different decimal-point symbols, launch a new
instance of RILSIM to open each file. There is no limit to the number of instances of RILSIM that
can be running at one time.
|
September 2004 |
Inability to Share Files—In the original translation from English to
Portuguese that was released for use in Brazil in 2006, certain headings in the routine that writes
data to .rdb data files were translated into Portuguese that should have remained in English,
since they are never seen by the user but are used by RILSIM to organize data within the output files.
As a result, RILSIM Português could read its own data files but could not read files written
by other versions of RILSIM. Similarly, other versions of RILSIM could not read data files that had
been written by RILSIM Português 2.00.
|
2.00
ptb
|
Fixed in version 2.02
Fix—RILSIM 2.02 has been rewritten so that it will properly read data file headings written
either in English or in Portuguese. This means that all language versions of RILSIM 2.02 can read data
files written by any other version. This includes files written by the original RILSIM Português
version.
|
July 2009
|
Side-by-side installations—Previously, different language versions
of RILSIM could not be installed simultaneously on a single computer. Although the
installations might appear to succeed, the most recent installation would overwrite
Windows registry entries that had been created by previous installations. The different
language versions would therefore interfere with each other. In addition, the installation
modules for the different language versions did not recognize language differences.
As an example, installing RILSIM Français on a computer that already had
RILSIM 1.05 installed would cause RILSIM 1.05 to be removed, even though that version
was in English. Although this might be what the user intended, we decided it was
better for the user to explicitly decide whether to remove the English version and
then install the French version.
|
2.00
2.01
|
Fixed in version 2.02
Fix—Each language version of RILSIM 2.02 now uses its own entries in
the Windows registry that are separate from those of other language versions. In
addition, the installation module for each language version will only update previous
installations in that same language. Therefore, all language versions can now be
installed on an individual computer and will not interfere with each other.
|
July 2009
|