GNOME Bugzilla – Bug 463395
metacity with "reduced_resources" true, double-click window title, should not show 3x3 grid line
Last modified: 2007-12-12 03:20:29 UTC
Please describe the problem: I want to make my ubuntu desktop to consume less cpu resource when I move, resize, maximize, minimize the window. I found an option: /apps/metacity/general/reduced_resources . So I set it to true using gconf_editor. When I double click the window title, I want it to maximized or restored. However, I see 3x3 grid line first. And for some application, such as gconf_editor itself, some grid lines will remain in its client area, not be cleared. When I click another window, I want to activate and focus it. However, I see 3x3 grid line first. Steps to reproduce: 1. run gconf_editor, set /apps/metacity/general/reduced_resources, to true 2. double click any window title, you see 3x3 grid line before the window is maximized or restored. 3. click any window title, you see 3x3 grid line immediately. not after a while or until user start to drag. Actual results: I see 3x3 grid line Expected results: 3x3 grid line should not show Does this happen every time? Yes Other information: Suggestion: when user click window title, the 3x3 grid line should appear only after a while or when user start drag. It's better to add an option, let user decide 3x3 grid or 1x1 grid, the latter will be more natural.
Additional Suggestion: When double click the window title, the 3x3 grid line also should not show.
With "reduced_resources" on, when you drag a window title-bar and move the window, the system still consume some percentage of CPU. However, in Windows XP, if you set the window contents not to be shown, the CPU usage is very low when dragging and moving a window. Still related to the 3x3 grid line? or Not?
Sorry for the delay in answering; I think this is actually a duplicate of bug 502644 (well, bug 502644 is a duplicate of this one, but more work has been done over there). Please feel free to go over there and share your thoughts on the matter. *** This bug has been marked as a duplicate of 502644 ***