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 592443 - Edit Custom Messages item should respect menu icon setting
Edit Custom Messages item should respect menu icon setting
Status: RESOLVED OBSOLETE
Product: empathy
Classification: Core
Component: Contact List
2.27.x
Other Linux
: Low minor
: ---
Assigned To: empathy-maint
empathy-maint
: 592853 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-08-20 10:48 UTC by Michael Monreal
Modified: 2018-05-22 13:38 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot (4.19 KB, image/png)
2009-08-20 10:48 UTC, Michael Monreal
Details

Description Michael Monreal 2009-08-20 10:48:05 UTC
GNOME 2.28 defaults to not show menu icons for most items (except applications, "objects" and certain special items). In the status chooser, the last entry "Edit Custom Messages..." should not show the gtk-edit icon if menus_have_icons is set to false.
Comment 1 Michael Monreal 2009-08-20 10:48:58 UTC
Created attachment 141231 [details]
Screenshot
Comment 2 Frederic Peters 2009-08-20 11:27:43 UTC
This is voluntary, it has been discussed in bug 591247.

> <mpt> fredp, yes, I think IM statuses should count as objects
> <mpt> (and therefore have icons)
Comment 3 Michael Monreal 2009-08-20 11:48:37 UTC
IM statuses for sure, but the "Edit Custom Messages..." is not a status, it's an action like "save" or "open". I'm quite sure mpt would agree :)
Comment 4 Frederic Peters 2009-08-20 12:03:22 UTC
Oh right, didn't click on your screenshot :)
Comment 5 Frederic Peters 2009-08-21 14:12:57 UTC
Ok, I got confused as you're not talking about the menu that appears when right clicking on the status icon, which has an "edit custom messages..." that should respect global policy, and the presence chooser in the main window, which is *not* a menu but a treeview.

This makes it relatively difficult to fix it correctly, as it needs code to listen to the global gconf property, and update a treeview item on changes...

The "wrong" fix is however quite easy, removing the icon permanently could be done by this simple fix to presence_chooser_create_model():

        gtk_list_store_insert_with_values (store, NULL, -1,
                COL_STATUS_TEXT, _("Edit Custom Messages..."),
-               COL_STATE_ICON_NAME, GTK_STOCK_EDIT,
+               COL_STATE_ICON_NAME, "",
                COL_DISPLAY_MARKUP, _("Edit Custom Messages..."),
                COL_TYPE, ENTRY_TYPE_EDIT_CUSTOM,
                -1);
Comment 6 Frederic Peters 2009-08-24 06:38:32 UTC
*** Bug 592853 has been marked as a duplicate of this bug. ***
Comment 7 Xavier Claessens 2009-08-24 08:12:35 UTC
(In reply to comment #5)
> This makes it relatively difficult to fix it correctly, as it needs code to
> listen to the global gconf property, and update a treeview item on changes...

Indeed that's what we should do.

> The "wrong" fix is however quite easy, removing the icon permanently could be
> done by this simple fix to presence_chooser_create_model():
> 
>         gtk_list_store_insert_with_values (store, NULL, -1,
>                 COL_STATUS_TEXT, _("Edit Custom Messages..."),
> -               COL_STATE_ICON_NAME, GTK_STOCK_EDIT,
> +               COL_STATE_ICON_NAME, "",
>                 COL_DISPLAY_MARKUP, _("Edit Custom Messages..."),
>                 COL_TYPE, ENTRY_TYPE_EDIT_CUSTOM,
>                 -1);

I don't like that patch. IMO we should respect the value of that gconf key. I personally don't like removing all icons. For menus I know, I can find the line I want just by a quick look to icons, and don't read text anymore...
Comment 8 GNOME Infrastructure Team 2018-05-22 13:38:54 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/empathy/issues/106.