| Summary: | wxWindows Template | ||
|---|---|---|---|
| Product: | [Developer tools] kdevplatform | Reporter: | Blackpaw <lindsay> |
| Component: | appwizard | Assignee: | KDevelop Developers <kdevelop-devel> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | 1.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Mandrake RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
Helio ? Closed on both 3_2_BRANCH and HEAD Thanks for report |
Version: 3.0.0.0b2 (using KDE KDE 3.1.3) Installed from: Mandrake RPMs Compiler: gcc 3.3.1 OS: Linux The code that gideon autogenerates for a base wxWindows app is ok for a std wxWindows build. However if wxWindows is build with unicode support then the generated code chokes the compiler. The problem is that all the string literals are ASCII, when they should be unicode. This can be portably worked around in the code by enclosng the strings in wxT(), e.g.: m_fileMenu->Append(101, wxT("Open")); m_fileMenu->Append(102, wxT("Save")); This will compile with unicode *and* non-unicode builds of wxwindows