The close button position should respect gconf settings

Bug #500405 reported by Sebastián Porta
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gloobus-preview
Fix Committed
Low
Unassigned

Bug Description

gloobus-preview it's the only application that I have installed that forces the close button in the left side.
I think that the button should be at the right side to be consistent with the rest of the applications on my system.

There is a gconf key here: /apps/metacity/general/button_layout

This key defines the position of the min/max/close buttons. Gloobus should check that key in order to decide where it puts its close button.

Revision history for this message
zp (zekopeko-deactivatedaccount) wrote :

Confirmed. Breaks consistency.

Changed in gloobus-preview:
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
Danielle Foré (danrabbit) wrote :

Not confirmed here. Because my close/max/min buttons are on the left side ;)

I think Gloobus should check the metacity gconf setting in order to figure out which side to display its close icon.

summary: - The close button should be at the right side
+ The close button position should respect gconf settings
description: updated
Revision history for this message
ammonkey (am-monkeyd) wrote :

i checked gconf and i don't have any
/apps/metacity/general/button_layout key you mentionned. It's probably because i don't use metacity and/or gnome as environnement so the gconf thing is not very "standard". what about ppl using others enviroonnement, other windows managers openbox, tilled ones etc...

Well i think we can define this as an option in setting of gloobus-preview.

Revision history for this message
ammonkey (am-monkeyd) wrote :

new option available

Changed in gloobus-preview:
assignee: nobody → kitkat (am-monkeyd)
status: Confirmed → Fix Committed
Revision history for this message
Danielle Foré (danrabbit) wrote :

kitkat,

I don't feel the issue has been properly resolved. If at all possible, we shouldn't ask the user for this kind of information. Gloobus should be able to divine this info on its own. And as the majority of our users are probably going to be on a Ubuntu/Gnome/Metacity DE, I think another solution is in order.

I purpose that we first add a check for the metacity gconf key, and only present the option if that key is unavailable. This would provide an automatic resolution for most users, and another solution for the smaller use cases.

Changed in gloobus-preview:
status: Fix Committed → Incomplete
Changed in gloobus-preview:
status: Incomplete → In Progress
Revision history for this message
ammonkey (am-monkeyd) wrote :

checking gconf values now: /apps/metacity/general/button_layout
option appear in the setting menu if u don't have the proper key in gconf for users who don't use gnome like me.

Revision history for this message
ammonkey (am-monkeyd) wrote :

let me know if it works ok

Changed in gloobus-preview:
status: In Progress → Fix Committed
BadChoice (guitarboy000)
Changed in gloobus-preview:
milestone: none → 0.4.2
ammonkey (am-monkeyd)
Changed in gloobus-preview:
assignee: ammonkey (am-monkeyd) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.