Creating custom events - Event Handling Overview vs. wxFormBuilder

[Vadim Zeitlin]

On Thu, 21 Feb 2008 13:26:08 +0100 Lars Uffmann <aral at nurfuerspam.de> wrote:

LU> Vadim Zeitlin wrote:
LU> >  Yes, wxCommandEvent ctor documentation is strange. OTOH it's still great
LU> > compared to your description of the problem. Let's see:
LU> >  [..]
LU> 
LU> I am really not in the mood to respond to your temper-tantrums. It's not 
LU> my fault if you're having a bad day.

 Oh sorry. I didn't mean to offense you but frankly, doesn't it seem
amazing that you managed to write a so unreadable report of a problem in
the documentation? Well, I guess not...

LU> If you ever bothered to actually be open to constructive criticism 

 I'm open to it but I honestly (I know you won't believe me but please try)
have no idea what did you complain about in the first place. I pointed to
the problem I see with the current documentation (which is problematic,
clearly documenting ctor by writing "Constructor" doesn't help much) but
you seemed to be complaining about something else entirely -- but I didn't
get what it was.

LU> In case you hadn't noticed, I never asked "please tell me how this
LU> works"

 FWIW there is nothing wrong with asking this if it's not already
prominently described in the docs.

LU> but instead asked for being pointed to documentation links
LU> regarding the issue I was having.

 Sorry, I didn't understand this. I thought you were pointing out a problem
in the documentation.

LU> Seriously man, get a grip on your bad humour... If responding to my 
LU> questions makes you become so upset, then please, don't do it. I'll get 
LU> along on my own somehow. No one is forcing you to be helpful and get all 
LU> angry over it.
LU> 
LU> Sheesh...
LU> 
LU> Thank you anyways, you've been helpful at some points at least.

 Rereading my reply it didn't come totally as I intended but I still think
you're overreacting. I wasn't upset and certainly didn't mean to upset you.
Once again, I just thought it was funny that a report about a problem with
a wording in the docs could have been written in so unclear way. I still
don't understand at all what your problem is, this description:

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

just seems to be lacking some bits critical for comprehension.

 Anyhow, good luck,
VZ

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