[Mono-bugs] [Bug 82765][Min] New - Form: Opacity property always returns 1 on Win32

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Sun Sep 9 11:18:25 EDT 2007

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by andyhume32 at yahoo.co.uk.


--- shadow/82765	2007-09-09 11:18:25.000000000 -0400
+++ shadow/82765.tmp.9636	2007-09-09 11:18:25.000000000 -0400
@@ -0,0 +1,42 @@
+Bug#: 82765
+Product: Mono: Class Libraries
+Version: 1.2
+OS Details: 
+Status: NEW   
+Priority: Minor
+Component: Windows.Forms
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: andyhume32 at yahoo.co.uk               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: Form: Opacity property always returns 1 on Win32
+Repro is ./ch02_Forms/OpacitySample from the sample code for the 
+book "Windows Forms 2.0 Programming," by 
+Chris Sells and Michael Weinhardt, sources available from 
+Tested on SVN head on Win32, 1.2.5_5 Win32, and 1.2.3 Win32.
+On setting Opacity to (say) 0.5 the window becomes partially transparent, 
+but reading the value back always gives a value of 1.0.  Suse VM shows 
+the correct value for reading back the value[1].
+The sample sets Opacity=0.5 on Deactivate, and on Activated starts a 
+Timer which in steps increases Opacity by 0.1 to 1.0.  The title bar is 
+updated at every point to contain the current value the property.
+Thus on deactivation the text in the title bar should say 0.5.  This is 
+seen on MSFT and Mono on Linux, but Mono on Win32 it always shows 
+value '1'.
+[1] Transparency isn't seen though -- due to VM?  Is there also a 
+rounding issue there -- it completes at value 1.1 not at 1.0?

More information about the mono-bugs mailing list