After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 564626 - Maximizing/restoring a minimized window does not show window
Maximizing/restoring a minimized window does not show window
Status: RESOLVED OBSOLETE
Product: libwnck
Classification: Core
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: libwnck maintainers
libwnck maintainers
Depends on:
Blocks:
 
 
Reported: 2008-12-15 16:22 UTC by Wouter Bolsterlee (uws)
Modified: 2018-01-24 13:46 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Double restore item (12.33 KB, image/png)
2008-12-15 21:13 UTC, Wouter Bolsterlee (uws)
Details

Description Wouter Bolsterlee (uws) 2008-12-15 16:22:27 UTC
When I maximize/restore a minimized window using the context menu on my panel's window listing applet, the window stays minimized. It should not.
Comment 1 Paul Bolle 2008-12-15 21:00:59 UTC
0) Isn't the Windows List Applet a gnome-panel component? If so, might be a duplicate of that product.

1) A quick look here suggests the following (in 2.22): the context menu has two items a top:
 - (un)minimize
 - (un)maximize
These two items seem independent. What this means, is that toggling (un)maximize on a minimized window changes a setting one will only notice after also toggling unminimize. It only looks like (un)maximizing doesn't do anything. It just doesn't do anything directly noticeable ...

2) I'm not sure what the merits of this part of the Window List Applet UI are. At first glance it is rather puzzling.

3) Anyhow, does this cover the problem of comment #0?
Comment 2 Wouter Bolsterlee (uws) 2008-12-15 21:13:55 UTC
Created attachment 124757 [details]
Double restore item

Both "Unmaximize" and "Unminimize" are called "Restore" it seems. See the menu in the screenshot. This is after I minimized a maximized window. You can see two identical menu items, one of which does show the window, i.e. unmaximizes, while the other seems to do nothing, i.e. it toggles the maximized stated of the hidden window without showing the window.

Fwiw, "Herstellen" is the Dutch translation for "Restore" — I'm not sure if this is a i18n issue (haven't checked in another locale).
Comment 3 Paul Bolle 2008-12-15 21:24:49 UTC
Can confirm comment #2 regarding the translation of unminimize and unmaximize. The Dutch translation adds another level of confusion to this UI. Separate bug, I guess.

Anyway, the troublesome item is the second item: Maximaliseren vs Herstellen. That's the item that doesn't do anything directly noticeable.

By the way, could even be a libwnck bug. Cheked for dplicates there?
Comment 4 Wouter Bolsterlee (uws) 2008-12-15 21:25:51 UTC
I already pinged vuntz about it.
Comment 5 Paul Bolle 2008-12-15 22:54:06 UTC
uws: duplicate of bug #122640 (five years old, broader scope)?
Comment 6 Vincent Untz 2009-01-06 16:18:46 UTC
Hrm, there are a few things here:

 + the translations are bad (in french too), which creates some confusion. On the other hand, I know it's hard to provide something better...
 + there's bug #122640, as already pointed out, which could solve the issue from a metacity point of view
 + libwnck could possibly unminimize when unmaximizing a window from this menu.

The last item is the libwnck part. I'm not 100% sure we want to do this (we'd actually need to do it for move & resize too).

So moving the bug to libwnck for further consideration, since there's already a metacity bug abou this.
Comment 7 Marcus Carlson 2009-06-28 19:39:46 UTC
About the libwnck stuff, can't we just disable the (un)maximize, move and resize option when the window is minimized?
Comment 8 GNOME Infrastructure Team 2018-01-24 13:46:07 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/libwnck/issues/108.