Events sent programmatically

[Francesco Montorsi]

Kevin Ollivier ha scritto:
> I like the idea of deprecating old stuff at least as much as anyone 
> here. :-)
;)

> With our current approach, however, deprecating existing (and 
> common) functions in common classes is going to be a very long process, 
> and will likely require us to maintain both approaches throughout the 
> life of the 2.x series, to the point that these functions won't ever be 
> 'truly' deprecated in 2.x. 
Why couldn't we deprecate them in 2.8.0 ?


 >That being the case, having both Delete and
> Remove, and having the possibility of mixing them in existing code, is 
> going to be problematic for users.
since the function name cannot be made more explicit (i.e. we can't use 
SetSelectionWithoutEvent as discussed before), maybe we could add a some 
code wrapped into #ifdef __WXDEBUG__ #endif which detects if user is 
using both event-free and old-style functions (e.g. Remove & Delete) in 
the same application. If he's using both we output a wxLogDebug here and 
there to remember him of the difference.

> The only really feasible solution that I see to these API issues is for 
> those who really want to see them fixed to create a major version bump 
> with backwards-incompatible APIs, in order to fix these issues the right 
> way and not have to support the old system for years to come.
backwards-incompatible API would mean to definitevely remove the 
functions which send events (and not just deprecate them) ?

Francesco