This is the copy paste bug we've had some some time I gather. I'm thinking we can do a release but make it clear this is a known issue.
I think the problem extends beyond just Padre and into the Wx toolkit itself. I'm not 100% sure though, but there is a comment in the ticket to the effect that this problem does appear in the demo as well. The last release announcement did say that Padre was moving to a somewhat "unstable" few releases on the run up to 1.0, so having an existing bug like this one one persist for this release shouldn't be a major issue, so I don't see it should be a blocker for this release, but it certainly should be something we try to get sorted out by 1.0. I have been effected by this bug myself and find it a frustrating usability issue, however one that has been with us a for quite some time. If no one has any strong reasons not to do so I'll branch with intent to release by Monday. Peter. > Hi, > > maybe this bug here should be closed before the release (does not mean > "before branching"): > http://padre.perlide.org/trac/ticket/1312 > > And this one, too, but I would not argue too much for it, because I > seem to be the only one affected by it, and it is due to some weird > things in external CPAN packages: > http://padre.perlide.org/trac/ticket/1327 > > Best regards, > Zeno > > On Wed, Oct 19, 2011 at 3:32 PM, Peter Lavender <pla...@internode.on.net> > wrote: > > Hi Everyone, > > > > This release is showing up to be one of the biggest after one of the longest > > development cycles in a really long time. > > > > Are we at a good point to create the branch for release? > > > > Peter. > > _______________________________________________ > > Padre-dev mailing list > > Padre-dev@perlide.org > > http://mail.perlide.org/mailman/listinfo/padre-dev > > > > > > >
_______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
