[wxWidgets.git] / docs / msw / issues.txt

Current issues and bugs
-----------------------

Memory-checking subsystem
-------------------------

This conflicts with wxUSE_IOSTREAMSH = 0 using MS VC++ 5.0
(crashes the template code). It should be switched off if you
wish to use wxUSE_IOSTREAMSH = 0.

BC++ in 16-bit mode
-------------------

resource.cpp has to be split into two to compile (hence
resourc2.cpp). Unfortunately we still get the error:

        Segment TEXT_RESOURCE exceeds 64K.

The solution is probably to load wxResourceBitListTable
dynamically using LoadString to load the names, and initialize the table
at wxWidgets start-up.

Meanwhile the work-around is to switch wxUSE_WX_RESOURCES to 0
(done in setup.h if BC++/16-bit mode is detected).

See also:
 http://www.inprise.com/devsupport/borlandcpp/ti_list/TI703.html
 http://www.inprise.com/devsupport/borlandcpp/ti/TI1007.html
Commit	Line	Data
2bda0e17 KB	1	Current issues and bugs
	2	-----------------------
	3
4fabb575 JS	4	Memory-checking subsystem
	5	-------------------------
	6
	7	This conflicts with wxUSE_IOSTREAMSH = 0 using MS VC++ 5.0
	8	(crashes the template code). It should be switched off if you
	9	wish to use wxUSE_IOSTREAMSH = 0.
	10
3b1de9c2 JS	11	BC++ in 16-bit mode
	12	-------------------
	13
	14	resource.cpp has to be split into two to compile (hence
	15	resourc2.cpp). Unfortunately we still get the error:
	16
	17	Segment TEXT_RESOURCE exceeds 64K.
	18
	19	The solution is probably to load wxResourceBitListTable
	20	dynamically using LoadString to load the names, and initialize the table
fc2171bd	21	at wxWidgets start-up.
3b1de9c2 JS	22
	23	Meanwhile the work-around is to switch wxUSE_WX_RESOURCES to 0
	24	(done in setup.h if BC++/16-bit mode is detected).
	25
	26	See also:
	27	http://www.inprise.com/devsupport/borlandcpp/ti_list/TI703.html
	28	http://www.inprise.com/devsupport/borlandcpp/ti/TI1007.html
	29