[Mono-bugs] [Bug 48689][Min] Changed - Visible is not saved at SaveViewState

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Mon, 29 Sep 2003 03:37:20 -0400 (EDT)


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 gonzalo@ximian.com.

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

--- shadow/48689	2003-09-29 03:11:19.000000000 -0400
+++ shadow/48689.tmp.32043	2003-09-29 03:37:20.000000000 -0400
@@ -1,12 +1,12 @@
 Bug#: 48689
 Product: Mono/Class Libraries
 Version: unspecified
 OS: All
 OS Details: 
-Status: NEEDINFO   
+Status: REOPENED   
 Resolution: 
 Severity: Unknown
 Priority: Minor
 Component: System.Web
 AssignedTo: gonzalo@ximian.com                            
 ReportedBy: yaronsh@mainsoft.com               
@@ -37,6 +37,19 @@
 
 
 ------- Additional Comments From yaronsh@mainsoft.com  2003-09-29 03:11 -------
 The visible is not saved in SaveViewState.
 One could say that by giving the property value the visible variable 
 is saved but there is a chanse that we miss an "edge case"...
+
+------- Additional Comments From gonzalo@ximian.com  2003-09-29 03:37 -------
+I have the same feeling, but i don't want to populate the VIEWSTATE
+with more data until we are sure.
+
+Btw, talking about VIEWSTATE size with Duncan, I realized that we can
+perform at least 2 reductions more. One of them is related to this:
+using an int as a bit field. That way we can save Visible, Enabled and
+others boolean values, while not making VS grow too much.
+
+I think I'm gonna do that pretty soon. The other 'reduction' is using
+hexadecimal numbers instead of decimal ones or even binary. I'll do
+some testing... and then store Visible too.