Hi,
All Wx constructors work this way though which I would guess you know?
You always have to specify all preceding params to the one you actually
want to set. Or is there something specific about Wx::ColourPickerCtrl?
(I can't remember using it).
On 20/03/2011 23:49, Reserved Local Account via RT wrote:
Sun Mar 20 19:49:28 2011: Request 66648 was acted upon.
Transaction: Correspondence added by a...@ali.as
Queue: Wx
Subject: Re: [rt.cpan.org #66648] Wx::ColourPickerCtrl does not support
null colours
Broken in: (no value)
Severity: (no value)
Owner: Nobody
Requestors: ad...@cpan.org
Status: rejected
Ticket<URL: http://rt.cpan.org/Ticket/Display.html?id=66648>
If you do that though, all the remaining parameters are off limits to
the constructor and can't be set.
Adam K
On 17 March 2011 09:07, Mattia Barbon via RT<bug...@rt.cpan.org> wrote:
<URL: https://rt.cpan.org/Ticket/Display.html?id=66648>
Il Mar 15 Mar 2011 21:00:21, ADAMK ha scritto:
Wx::ColourPickerCtrl segfaults if the colour parameter to the
constructor is undef.
According to the C++ documentation, I believe this should result in
Wx::ColourPickerCtrl defaulting to black.
The color will default to black if you call the constructor as:
Wx::ColourPickerCtrl->new( $parent, -1 );
an explicit undef, is translated to NULL, and the underlying C++ function takes
a C++
reference, wich can't be NULL.
Regards,
Mattia
