TODOs for wxWidgets 3.0

[ATS]

Robert Roebling <robert at ...> writes:

> I wonder what are actually the urgent TODOs for what
> will be wxWidgets 3.0. Maybe if we list the outstanding
> issues, people will have more incentive to tackle
> individual issues (well, maybe). I'll stick to wxMSW,
> wxMac and wxGTK as the other ports should not hinder
> a release of the three major ports.

A few things comes to my mind. 

1 - Weak references to wxEvtHandler derived classes. 

This can help a lot with keeping pointers to windows and
other objects. Too a large extent, weak references solves
problems with dangling pointers. It can help quite a bit 
in an app and also internally in wxW when a reference to 
a non owned object must be stored. 

I made a patch for this some 4 weeks ago at SF (so far 
unprocessed). 

2 - Thread safe logging 
I've implemented this and find it useful whenever working 
with threads (not submitted as patch). There's also a separate 
patch at SF implementing this.

Again, it is a basic but enabling feature.

3 - wxCriticalSection 
This class has different behaviour under Unix and Windows. 
(Unix: non-recursive mutex, Windows : native recursive
CRITICAL_SECTION used). It should be fixed so an app doesn't 
stumble on this.


I currently have no SVN write access, so far I've submitted 
SF patches for most of my work. This sometimes works, but 
can be awkward also.

Is there a procedure to have SVN write access?

Regards
// ATS