Troubleshooting and Error Handling

Troubleshooting

This section should help you to solve some non-application issues.

wxGlade has started e.g. by clicking the desktop icon with mouse, but no application window opens

Check the log file for errors (see the section called “Configuration Files”) and check that all dependencies (especially wxWidgets and Python) are installed. A list of dependencies is in the section called “Requirements and Supported Platforms”.

If you think this is an application issue, file a bug report like described in the section called “How to Report a Bug”, please.

Error Messages

The following list are error messages should help you to find the reason and take corrective actions. Please note, the list is still incomplete.

Output path "<path>" must be an existing directory when generating multiple files.

Details: You want to create multiple files for your design. wxGlade expects an output directory in such case, but the given output path isn't a existing directory.

Corrective Action: Create the missing directory or select an existing output directory.

Output path "<path>" exists but the directory is not writable.

Corrective Action: Choose a writable output directory.

Output path "<path>" can not be a directory when generating a single file.

Details: You want to write your design into a single file. wxGalde expects an output filename, but the given output path is a directory.

Corrective Action: Choose a file instead of a directory.

Output path "<path>" should be a directory when generating multiple files.

Details: You want to create multiple files for your design. wxGlade expects an output directory in such case, but the given output path isn't a directory.

Corrective Action: Choose a output directory.

Generated source code couldn't converted to encoding <encoding>. The source contains invalid characters "<characters>" from <start position> to <end position>.

Details: The current design uses characters that can't converted to the encoding selected for the source code file.

Corrective Action: Choose a design encoding that supports the listed characters also.

Generating Lisp code for wxWidgets version <version> is not supported.

Details: There is no Lisp support for the selected version of wxWidgets

Corrective Action: Create the code for an older wxWidget version.

XRC code cannot be split into multiple files.

Details: You want to create multiple XRC files for your design. This option isn't supported by wxGlade.

Corrective Action: Select the Single file option to store the whole design in one XRC file.

Code generation from a template is not possible.

Details: You've selected a template as input file to generate source code from.

Corrective Action: Use a design file instead of a template.

Code writer for "<language>" is not available.

Details: The code generators for the given language hasn't been loaded.

Corrective Action: That's probably a bug in wxGlade. Please check the log file and file a bug report. See the section called “How to Report a Bug” for more details.

Conversion of the source file <filename> to Unicode failed.

Details: The file encoding set within the design doesn't match the encoding used within the source file. Thereby the source file can't be loaded.

Corrective Action: Check the encoding selected in your design and the encoding of your source file. Change the design encoding to match source files encoding.

How to Report a Bug

Writing a helpful bug report is easy if you follow some hints. The items below should help you to integrate useful information. They are not an absolute rule - it's more like a guideline.

  • What did you? May you want to include a screen shot.

  • What do you want to happen?

  • What actually happened?

  • Provide a short example to reproduce the issue.

  • Include the internal error log file wxglade.log always. The pane How to Report a Bug contains the full path of the error log file. The file location is additionally described in the section called “Configuration Files”.

May you read How to Report Bugs Effectively additionally.

Please open a new bug in the wxGlade bug tracker at Sourceforge. You have to log-in at Sourceforge to file a bug report.

Alternatively you can send the bug report to the wxGlade mailing list. Keep in mind that you need a subscription for sending emails to this mailing list.

Figure 1.5. An error dialog example

An error dialog example