Prev: wxSashWindow Event
Next: OpenGL and Light
From: Vadim Zeitlin on 7 May 2008 09:30
On Wed, 7 May 2008 03:39:12 -0700 (PDT) Marcin 'Malcom' Malich <malcompl(a)gmail.com> wrote:

MMM> > MMM> So, in my opinion, we should delete generate mouse event code from
MMM> > MMM> WM_KEY* (or sign to deprecate/compatible2.8 for existing code and
MMM> > MMM> delete in wx3.0),
MMM> >
MMM> > �I don't really see any reason to do this, what's the harm in keeping it?
MMM> > This change would break the existing code silently (you can't ensure that
MMM> > the code using this feature would generate compilation warnings or errors)
MMM> > and this is the worst kind of breakage possible so there should be really a
MMM> > very good reason to do it.
MMM>
MMM> The generate mouse event is not necessary, the code should by using
MMM> wxContextMenu for showing popup menu, no mosuse handlign event.

All correct.

MMM> Ofcourse it will ruin compatibility with older code that uses wx,

Also correct.

MMM> but developer should take it into consideration every time he changes
MMM> library's version he's using.

However here you're sadly mistaken if you think anybody can review the
entire existing code base when upgrading to a new wx version. One thing is
when the old code starts giving deprecation warnings or doesn't compile any
more. But in the case of silent breakage it's almost certain that it won't
be noticed.

MMM> In my opinion wx3 should supporting exception, namespace and other
MMM> language features ;)

Err, yes, but what does it have to do with VK_APPS?

MMM> > If you can write and test a (presumably very simple) patch needed to do
MMM> > this, I'd be glad to apply it.
MMM>
MMM> Ok, I'll write the patch in free time.

Thanks,
VZ

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

 | 
Pages: 1
Prev: wxSashWindow Event
Next: OpenGL and Light