comment on

One reason might be that when you download the documentation, you find such gems as:

Under "Programming strategies" - "Strategies for reducing programming errors":

Use ASSERT
Although I haven't done this myself within wxWidgets, it is good practice to use ASSERT statements liberally,...
Under "Programming strategies" - "Strategies for debugging":

Positive thinking It is common to blow up the problem in one's imagination, so that it seems to threaten weeks, months or even years of work....

Under "Topics overview" - "wxWidgets Hello World sample"

//
// file name: hworld.cpp
//
//   purpose: wxWidgets "Hello world"
//

// For compilers that support precompilation, includes "wx/wx.h".
#include "wx/wxprec.h"

#ifdef __BORLANDC__
    #pragma hdrstop
#endif

#ifndef WX_PRECOMP
    #include "wx/wx.h"
#endif
[download]

Under "Topics overview" other subheads include "wxPython overview" & "Archive formats such as zip", but not a single mention of Perl or wxPerl.
Even the contents page header is "wxWidgets 2.6.1: A portable C++ and Python GUI toolkit"
The first mention of Perl I found was under "Classes by category" - "wxTopLevelWindow" - "wxTopLevelWindow::GetIcon" where if found:
- wxTopLevelWindow::GetIcon - wxPerl note: This method is not implemented in wxPerl
- wxTopLevelWindow::GetIcons - wxPerl note: This method is not implemented in wxPerl
- wxTopLevelWindow::GetTitle - wxPerl note: This method is not implemented in wxPerl
- ...

At which point I decided whatever limitations of documentation Tk has, and they are myriad, at least most of it is a) relevant; b) mostly Perl related.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^2: Win32 development by BrowserUk
in thread Win32 development by dragonchild

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.