Background images with transparent areas are bad visualized on Windows

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create an image with an alpha channel and a transparent area with gimp
2. Open ardesia
3. Load the prepared image with alpha channel as background image going in the
   Ardesia setting menu.

What is the expected output? What do you see instead?

I expect an image with a transparent area but instead of the transparent area 
is visualized a black hole.

Original issue reported on code.google.com by al...@paranoici.org on 9 Mar 2011 at 12:54

[GoogleCodeExporter]

I have tried two different approach to solve this bug:
  * load the images in a pixbuf, paint the windows with the pixbuf content through cairo  graphics library
  * load the image in a pixbuf, paint the widows with the gdk subsystem
  * load directly the the png file in the cairo context with the cairo_image_surface_create_from_png function

In all these approaches I have the same BAD result. I think that it is not 
possible at the moment load rgba images in a Windows gtk/gdi window.

Original comment by al...@paranoici.org on 9 Mar 2011 at 1:01

[GoogleCodeExporter]

Original comment by al...@paranoici.org on 14 Mar 2011 at 2:34

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

The issue is related for sure to the missing gtk RGBA support on windows

Original comment by al...@paranoici.org on 22 Jun 2011 at 12:05

[GoogleCodeExporter]

Original comment by al...@paranoici.org on 2 Aug 2011 at 1:52

• Added labels: Ardesia, Windows

[GoogleCodeExporter]

The Gtk 3 is out; the bug could be fixed porting the code from the gtk 2 to the 
gtk 3

Original comment by al...@paranoici.org on 9 Oct 2011 at 11:53

[GoogleCodeExporter]

Original comment by al...@paranoici.org on 11 Oct 2011 at 4:25

• Added labels: OpSys-Windows

[GoogleCodeExporter]

Ardesia on subversion repository has been ported on gtk3.
Are there some volunters that want to try to build Ardesia on WIndows and 
update the issue status.

Original comment by pilolli....@gmail.com on 27 Aug 2012 at 7:22

[GoogleCodeExporter]

Also this bug might be fixed with GTK3+ on Windows, this will be solved with 
issue 48 

Original comment by pilolli....@gmail.com on 26 Oct 2012 at 8:37

• Changed state: Invalid