From: Neil H. <ne...@su...> - 2007-09-05 08:35:36
|
On 05/09/2007 07:15, Kevin Altis wrote: > Checking wx.ALPHA_OPAQUE in the shell shows... > > >>> wx.ALPHA_OPAQUE > 255 Yes, I'm getting 255 alpha all the time. In fact, the Windows XP color picker does not allow you to set transparency and when you set a color it comes back as an (R,G,B) tuple in the property editor. But when you save the file, or click on a different property and return to the color one it has the transparency added. > I haven't dug into the other code in the resourceEditor or other places > that might make assumptions about the format of the color in the > framework, but I'm pretty sure there will be a number of problem spots > for trying to run on an older wxPython. I'm guessing that I'm an unusual case and most developers are using a single machine or update all their machines to the same version. Is it worth trying to handle this in code, or should we just class it as a very-low-priority issue that awkward s*!ds like me have to work around manually? > Alternatively, you could identify the 4 tuple strings in your .rsrc.py > files and do a global replace on them before copying/using on an older > version of wxPython. Exactly what I did when I hit the issue - I only had 2 color properties in the resource file so I chopped the transparency element off the end. Thanks for checking... -- Neil Hughes |