|
23.
|
|
|
BUG: no options
|
|
|
This is shown if the configuration file has no installable options,
either because none are listed or they've all become disabled, which
is a bug the developer must fix before shipping her installer.
|
|
|
|
BUG: no options
|
|
Translated and reviewed by
Chris 'fydo' Hopp
|
|
|
|
24.
|
|
|
BUG: support_uninstall requires write_manifest
|
|
|
This is shown if the config file wants us to include the uninstaller
program with the rest of the files we write to disk, but didn't enable
the manifest support the installer needs. This is a bug the developer
must fix before shipping her installer.
|
|
|
|
BUG: support_uninstall requires write_manifest
|
|
Translated and reviewed by
Chris 'fydo' Hopp
|
|
|
|
25.
|
|
|
BUG: write_manifest requires Lua parser support
|
|
|
This is shown if the config file wants us to install a manifest (a list
of everything we wrote to disk) but didn't enable Lua parser support
in the binary, which they need to handle Lua source code without
compiling it first (as it needs to be "parsed")...the manifest is
ultimately just an uncompiled Lua program that the installer generates.
This is a bug the developer must fix before shipping her installer.
|
|
|
|
BUG: write_manifest requires Lua parser support
|
|
Translated and reviewed by
Chris 'fydo' Hopp
|
|
|
|
26.
|
|
|
BUG: Setup.DesktopMenuItem requires support_uninstall
|
|
|
This is shown if the config file wants us to add desktop menu items
but uninstaller support isn't enabled. It is considered bad taste
to add system menu items without a way to remove them. This is
a bug the developer must fix before shipping her installer.
|
|
|
|
BUG: Setup.DesktopMenuItem requires support_uninstall
|
|
Translated and reviewed by
Chris 'fydo' Hopp
|
|
|
|
27.
|
|
|
BUG: '%0' is not a valid permission string
|
|
|
This is a file's permissions. Programmers give these as strings, and
if one isn't valid, the program will report this. So, on Unix, they
might specify "0600" as a valid string, but "sdfksjdfk" wouldn't be
valid and would cause this error.
|
|
|
|
BUG: '%0' is not a valid permission string
|
|
Translated and reviewed by
Chris 'fydo' Hopp
|
|
|
|
28.
|
|
|
BUG: Invalid format() string
|
|
|
If there's a string in the program that needs be formatted with
%0, %1, etc, and it specifies an invalid sequence like "%z", this
error pops up to inform the programmer/translator.
"format()" is a proper name in this case (program function name)
|
|
|
|
BUG: Invalid format() string
|
|
Translated and reviewed by
Chris 'fydo' Hopp
|
|
|
|
29.
|
|
|
BUG: stage returned wrong type
|
|
|
The program runs in "stages" and as it transitions from one stage to
another, it has to report some data about what happened during the
stage. A programming bug may cause unexpected type of data to be
reported, causing this error to pop up.
|
|
|
|
BUG: stage returned wrong type
|
|
Translated and reviewed by
Chris 'fydo' Hopp
|
|
|
|
30.
|
|
|
BUG: stage returned wrong value
|
|
|
The program runs in "stages" and as it transitions from one stage to
another, it has to report some data about what happened during the
stage. A programming bug may cause unexpected information to be
reported, causing this error to pop up.
|
|
|
|
BUG: stage returned wrong value
|
|
Translated and reviewed by
Chris 'fydo' Hopp
|
|
|
|
31.
|
|
|
BUG: stepped back over start of stages
|
|
|
The program runs in "stages", which can in many cases be revisited
by the user clicking the "Back" button. If the program has a bug
that allows the user to click "Back" on the initial stage, this
error pops up.
|
|
|
|
BUG: stepped back over start of stages
|
|
Translated and reviewed by
Chris 'fydo' Hopp
|
|
|
|
32.
|
|
|
BUG: Unhandled data type
|
|
|
This happens if there's an unusual case when writing out Lua scripts
to disk. This should never be seen by an end-user.
|
|
|
|
BUG: Unhandled data type
|
|
Translated and reviewed by
Chris 'fydo' Hopp
|
|
|