Creating custom events - Event Handling Overview vs. wxFormBuilder

[Vadim Zeitlin]

On Thu, 21 Feb 2008 10:30:57 +0100 Lars Uffmann <aral at nurfuerspam.de> wrote:

LU> Then that would be a prime example of the insufficient documentation 
LU> I've been complaining about before. I found an example of 
LU> wxCommandEvent, constructing a new one, with an error in the second 
LU> parameter (undefined variable), wanted to give that parameter a 
LU> meaningful value, and the documentation doesn't even mention what the 
LU> parameter is good for.

 Yes, wxCommandEvent ctor documentation is strange. OTOH it's still great
compared to your description of the problem. Let's see:

- you found an example of wxCommandEvent: where?
- "constructing a new one": phrase without verb no good
- with an error in the second parameter: what error?

So, without even trying, I am completely confused by the 3 sentences you
wrote. I hope after rereading what you wrote above you can appreciate a
little better why writing documentation which is immediately clear for
everyone is not easy.

 To summarize, I still have no idea what are you complaining about. I just
see the wrong value of type of the _first_ ctor parameter in the docs and
missing explanation for the same (do we really need to explain that the
parameter called "id" is meant to be passed an id?). What else is there?


LU> So does that mean I have to look through the wxwidgets sources to find 
LU> out more about this?

 Oh horror.

LU> No offense intended, but this is really dissapointing

 To be brutally honest, if you're not willing to consider the possibility
of ever looking in wx sources, you're going to waste a lot of time which
could be saved otherwise. You can still use wx, of course (plenty of people
with the same code-reading aversion attitude do) but I am just unable to
understand this instinctive queasiness towards looking into [not even
sources but] the headers. Personally it's the first thing I do (whether
using wx, MFC or whatever) because the code is so often more clear (in
spite of being more concise) than documentation anyhow.

 Regards,
VZ

-- 
TT-Solutions: wxWidgets consultancy and technical support
               http://www.tt-solutions.com/