Hi all,
I have a question about the PS backend (building on the thread
"imshow with PS backend" from ~ a month ago). Evidently this backend
is fixed at 72 dpi. This isn't a problem with vector information.
However, it would seem that one would want to use a higher resolution
when plott
I don't know how (or if) this can be improved, but I will gladly consider
patches.
On Thursday 31 August 2006 03:09, Michael Fitzgerald wrote:
> Hi all,
>
> I have a question about the PS backend (building on the thread
> "imshow with PS backend" from ~ a month ago). Evidently this backend
> is
On 08/28/06 12:19, Christopher Barker wrote:
>
> wx is really due for an update to support alpha properly. But I guess
> you'll always have problems with different data formats.
I think they added preliminary support for alpha channels in 2.5, in the form
of wx.Image.HasAlpha(). My beef is that
Ken McIvor wrote:
> I think they added preliminary support for alpha channels in 2.5, in the
> form of wx.Image.HasAlpha().
right, but it uses the old 24 bit RGB buffer, and separate Alpha buffer,
it's kind of tacked on, rather than native.
> My beef is that you have to convert
> everything to
On 08/31/06 13:43, Christopher Barker wrote:
> Ken McIvor wrote:
>
> a wxBitmap is the same format as the native rendering system. While most
> systems use 24b RGB (or 32b RGBA), people can still run displays at
> 16bpp or whatever, so it's still needed.
I can understand why it's still necessar
> "Ken" == Ken McIvor <[EMAIL PROTECTED]> writes:
Ken> On 08/31/06 13:43, Christopher Barker wrote:
>> Ken McIvor wrote:
>>
>> a wxBitmap is the same format as the native rendering
>> system. While most systems use 24b RGB (or 32b RGBA), people
>> can still run display
John Hunter wrote:
> It is useful to store the final pixel buffer (eg in a PNG) as RGBA
> because some people like to have some parts of their figure
> transparent to composite the figure with other images.
fair enough, and that's probably a really cool feature when you need it!
ken wrote:
> I
