[Mono-bugs] [Bug 82729][Min] New - Form: windows is three times too big when opaque/transparent(?)

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Fri Sep 7 04:41:46 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.

http://bugzilla.ximian.com/show_bug.cgi?id=82729

--- shadow/82729	2007-09-07 04:41:46.000000000 -0400
+++ shadow/82729.tmp.20419	2007-09-07 04:41:46.000000000 -0400
@@ -0,0 +1,40 @@
+Bug#: 82729
+Product: Mono: Class Libraries
+Version: 1.2
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Minor
+Component: Windows.Forms
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: andyhume32 at yahoo.co.uk               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Form: windows is three times too big when opaque/transparent(?)
+
+Repro is ./ch02_Forms/OpacitySample and ./ch02_Forms/TransparencySample 
+from the sample code for the book "Windows Forms 2.0 Programming," by 
+Chris Sells and Michael Weinhardt, sources available from 
+http://www.sellsbrothers.com/writing/wfbook/
+
+Each tested on SVN head on Win32, 1.2.5_5 Win32 and 1.2.5_5 Suse VM.
+
+The first sample displays a partially transparent window, and the second 
+sample display an ellipsoid-shaped window.  Both are two to three times 
+bigger than expected (as seen in MSFT and in forms designer in VS).
+
+
+The first sample is meant to go transparent when unfocused (Deactivated) 
+and on focus (Activated) grow more opaque step-by-step.  The 'activated' 
+action does not occur on Win32 it appears that the timer does not run.  
+On Suse VM the timer does run (but -- I presume due to the VM -- neither 
+of the windows appear transparent).
+
+
+(The second sample's windows is meant to move when I/J/K/L is pressed.  
+On Suse VM it won't move to the right it just jiggles back and forth.  
+Don't know whether again this is an artifact of the VM).


More information about the mono-bugs mailing list