Windows-specific problems

Under Windows, dialog boxes refuse to appear.

You probably forgot to include the file wx.rc in your resource script (see Resources).

Under X, the menu bar does not appear, and a blank area of window appears instead.

You may be using SetClientSize before the menu bar has been created. Call it after the whole window and its subwindows have been created.

Under Windows, I get a link error.

See sections Memory models and Large Data. Also, try invoking the Microsoft C++ help program (Quick Help) with the given error message.

Under Turbo C++ for Windows, you are likely to get an error which says that there is too much debugging information. Unfortunately, this is a fault of Borland's linker, and can only be solved by omitting some sections of your program from the debugging process, or by buying a new linker. Here is a message from the UseNet on the subject.

Article 34639 of comp.lang.c++:
>From: timh@loot01.demon.co.uk (Tim Hawkins)
Newsgroups: comp.lang.c++
Subject: Re: Turbo C++ 3.0 can't debug large programs!??
Date: 8 Aug 93 12:24:46 GMT
Reply-To: Timh@loot01.demon.co.uk

In article <5e0a8B2w165w@waffle.sns.com> billj@waffle.sns.com writes:

>zargon@leland.Stanford.EDU (Daniel Sommerfield) writes:
>> >However, I compiled my own class library (wxWindows) after much
>> >flicking of switches and fiddling with precompiled headers,
>> >only to find that linking with a small example program bombed
>> >the linker with "Debugging information overflow", and advice to
>> >reduce the number of modules with debugging information.
>> >
>Try downloading tdwin.zip from the Borland BBS.  Then unzip the file and 
>follow the procedures.  Probably you will end up renaming TDWIN.ZIP to 
>(TDWIN.DLL) to WINDEBUG.DLL.
>> 

This is a common problem with BC++, I get this on almost all of my projects

Using TDWIN will not help as the problem is during linking and not during
debugging sessions. 

The reason for the difficulty is that Borland limits the amount of symbolic
debug data to 256K, for "performance" reasons. However there is a fix,

SLR systems produce a linker which is fully compatable with the Tlink linker,
which does not suffer from this problem, it is called "optilink" and claims
to remove redundant methods as a bonus. If you get past the linker stage, and
still have problems, then this is because although TDW has a bigger symbol
limit than tlink, it is often still to small.. I have switched to using
the symantec "Multiscope" debugger which is also borland C++ compatable.

The link\debug system in BC++ is IMHO only suitable for small to medium
sized projects, and even then can bottle out at a suprisingly early stage.

Borland claim they have no plans to fix this problem. 
-- 
+--------------------------------------------------------------------------+
| Tim Hawkins  - timh@loot01.demon.co.uk     Loot Ltd Londons NoticeBoard  |
+--------------------------------------------------------------------------+