[Mono-bugs] [Bug 342662] New: Setting Visibility do not always Invalidate

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Mon Nov 19 05:16:53 EST 2007


           Summary: Setting Visibility do not always Invalidate
           Product: Moonlight
           Version: unspecified
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: engine
        AssignedTo: mono-bugs at ximian.com
        ReportedBy: sdelcroix at novell.com
         QAContact: mono-bugs at ximian.com
          Found By: ---

on the minesweeper (http://blogs.telerik.com/demos/minesweeper/), you can flag
possible bombs using shift-click (or ctrl-click), but the flag does not appear
as it should on the flagged square.

the code responsible for flagging is:

mFlag.Visibility = (value) ? Visibility.Visible : Visibility.Collapsed;

nothing fancy, should work...

I guess it's an invalidating issue, cause applying this patch to moon solves
the issue :

Index: src/uielement.cpp
--- src/uielement.cpp   (revision 89918)
+++ src/uielement.cpp   (working copy)
@@ -134,6 +134,7 @@
                        g_warning ("Invalid value (%d) specified for
UIElement::VisibilityProperty.", v);
                        /* continue as default (VisibilityVisible) */
                case VisibilityVisible:
+                       FullInvalidate (true);
                        flags |= UIElement::RENDER_VISIBLE;
                        Invalidate ();

Obviously, FullInvalidate is way too much...

Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

More information about the mono-bugs mailing list