Your message dated Wed, 10 Jun 2020 05:08:45 +0000
with message-id <[email protected]>
and subject line Bug#938834: Removed package(s) from unstable
has caused the Debian Bug report #239782,
regarding ColourDialog doesn't use pre-set data for display
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
239782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=239782
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libwxgtk2.4-python
Version: 2.4.2.4
I noticed an oddity which I'd like to track down. I'm not sure that
it is a bug in the binding instead of in my programming, which is why
I'd like to talk to an expert first before opening a bug report
officially.
I'm working with Python 2.3 and wxWidgets 2.4.2.4 under Debian sid and
discovered that after creating the colour dialog, pre-setting the
colour doesn't seem to take the effects I expected. Instead, the
dialog always displays black as selected colour, regardless of my
pre-setting.
In the example below I set the colour to red (#FF0000) after the
dialog is created but before it is drawn on the screen. However, on
my system it still displays black as selection instead of red.
This bug has been confirmed by Robin Dunn <[email protected]>, who is
responsible for the Python bindings of wxWidgets. However, he
discovered that this problem can be bypassed by using a different
constructor and supplying the color data at the __init__ stage.
He is working on a fix. So this bug report is just to document the
problem. Please check the attached program when you upload a new
version of wxWidgets to find out whether the problem is still present
or not.
Regards,
Joey
--
Still can't talk about what I can't talk about. Sorry. -- Bruce Schneier
Please always Cc to me when replying to me on the lists.
# -*- encoding: iso-8859-1 -*-
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
"""
I noticed an oddity which I'd like to track down. I'm not sure that
it is a bug in the binding instead of in my programming, which is why
I'd like to talk to an expert first before opening a bug report
officially.
I'm working with Python 2.3 and wxWidgets 2.4.2.4 under Debian sid and
discovered that after creating the colour dialog, pre-setting the
colour doesn't seem to take the effects I expected. Instead, the
dialog always displays black as selected colour, regardless of my
pre-setting.
In the example below I set the colour to red (#FF0000) after the
dialog is created but before it is drawn on the screen. However, on
my system it still displays black as selection instead of red.
This bug has been confirmed by Robin Dunn <[email protected]>, who is
responsible for the Python bindings of wxWidgets. However, he
discovered that this problem can be bypassed by using a different
constructor and supplying the color data at the __init__ stage.
Comment out one of the following runTest functions to find out what
the bug feels like.
"""
from wxPython.wx import *
#---------------------------------------------------------------------------
# Using the set data method, pre-selection doesn't work.
#
def runTest(frame, nb, log):
dlg = wxColourDialog(frame)
dlg.GetColourData().SetColour("#FF0000")
log.WriteText('Pre-selected color: %s\n' % str(dlg.GetColourData().GetColour().Get()))
dlg.GetColourData().SetChooseFull(True)
if dlg.ShowModal() == wxID_OK:
log.WriteText('You selected: %s\n' % str(dlg.GetColourData().GetColour().Get()))
dlg.Destroy()
# From Robin Dunn: Using a different constructor pre-selection works
#
# def runTest(frame, nb, log):
# data = wxColourData()
# data.SetColour("#FF0000")
# dlg = wxColourDialog(frame, data)
# log.WriteText('Pre-selected color: %s\n' % str(dlg.GetColourData().GetColour().Get()))
# dlg.GetColourData().SetChooseFull(True)
# if dlg.ShowModal() == wxID_OK:
# log.WriteText('You selected: %s\n' % str(dlg.GetColourData().GetColour().Get()))
# dlg.Destroy()
#---------------------------------------------------------------------------
if __name__ == '__main__':
from sys import path
path.insert (0, "/usr/share/doc/wxwin2.4-examples/examples/wxPython")
import sys,os
import run
run.main(['', os.path.basename(sys.argv[0])])
--- End Message ---
--- Begin Message ---
Version: 3.0.2.0+dfsg-8+rm
Dear submitter,
as the package wxpython3.0 has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/938834
The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
