search

jparris / enso

Automatically exported from code.google.com/p/enso
Other
0 stars 0 forks source link

Semi-transparent window has not semi-transparent background #17

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?

1. Compile Enso on WindowsXP, using MS Windows Server 2008 SDK
2. Run Enso

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

The colors of the main semi-transparent window are just wrong,
it seems it is not semitransparent but instead it just re-colors
the background, see the attached screenshots.

The background for the list of matches is missing, only white 
text is visible.

What version of the product are you using? On what operating system?

Latest source from SVN
Windows XP SP2
Litestep shell

Please provide any additional information below.

I do not have that problem with frozen Enso version.

Original issue reported on code.google.com by pavelvi...@gmail.com on 26 Mar 2008 at 12:44

Attachments:

GoogleCodeExporter commented 8 years ago 
Python 2.5

Original comment by pavelvi...@gmail.com on 26 Mar 2008 at 12:48

GoogleCodeExporter commented 8 years ago 
I've tried figuring out this bug - its weird. Its like the source surface (the 
Enso
window) is added to the destination surface (whatever windows are underneath) -
whereas it should work more like an overlay. Or something.

On my system, it looks fine on a black background - . Also looks fine if 
transparency
is disabled - but then you lose the cool rounded corners. 

And I never had this issue on Frozen Enso either.

Original comment by unfocu...@gmail.com on 28 Mar 2008 at 1:17

GoogleCodeExporter commented 8 years ago 
This problem appears also in the build from another developer, for Python 2.4.

Original comment by pavelvi...@gmail.com on 30 Sep 2008 at 5:01

GoogleCodeExporter commented 8 years ago 
Upgraded Windows XP to SP3, no change

Original comment by pavelvi...@gmail.com on 30 Sep 2008 at 5:02

GoogleCodeExporter commented 8 years ago 
Found the cause of the problem: DLL hell.
Enso was loading libcairo-2.dll from another application (GIMP), seeing it
on the PATH before Enso libcairo-2.dll.

This has also resulted in couple of another strange errors like "MemoryError" 
etc.

Patch I provided is for community branch.

Original comment by pavelvi...@gmail.com on 1 Oct 2008 at 12:54

Attachments: