Front page | perl.wxperl.users |
Postings from February 2013
Hi, On 05/02/2013 17:19, Tarek Unger wrote: > Greetings, > > i personally think this is a good approach. > A simple "use Wx;" anywhere in the code should *not* change the behavior > of a complete separate codepart. I think I'll release Wx 0.9917 with this change in. > Is it possible to change the overriding of wxAppTraits::SetLocale() > within perl? It is possible to allow the use to create custom wxAppTraits objects, but simpler I think just to stop the automatic setting. I don't think I would want to create some custom wxPerl specific call into and out of the C++ code. I would rather wrap wxAppTraits completely. However I don't see much else of that class as useful so for now I'll just override the default 'SetLocale' behind the scenes. If user wants to 'SetLocale' they can easily do it with Wx::Locale and create overall custom solution to suit their needs with POSIX::setlocale() > > On the other hand, if you are trying to maintain compatibility with > vanilla cpp-wxWidgets > i would suggest to document this problem on a prominent place. > > Something like this at the bottom of Wx.pm (i assembled some of your > explanation here): Maintaining compatibility with vanilla wxWidgets is a goal - but in this case I am sure the majority of wxPerl users would not want to automatically change basic Perl number to string conversions. There will be a lot of module code out there that assumes a 'C' locale with respect to number formatting. It seems silly to have a default behaviour that most wxPerl users will want to override. Thanks for taking the time to set this out. I'll add it to Wx pod and write a page on the Wiki with code to do in Perl what the automated wxWidgets code does. Best Regards MarkThread Previous