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 303003 - GtkUIManager::add-tearoffs should be a style property
GtkUIManager::add-tearoffs should be a style property
Status: VERIFIED WONTFIX
Product: gtk+
Classification: Platform
Component: Widget: Other
unspecified
Other All
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2005-05-04 15:26 UTC by Dominic Lachowicz
Modified: 2005-07-27 00:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Dominic Lachowicz 2005-05-04 15:26:56 UTC
It would be useful to me as a themer to control this at the toolkit level from
the gtkrc, and then encourage application designers to not play with its value.
Comment 1 Owen Taylor 2005-05-04 19:28:37 UTC

*** This bug has been marked as a duplicate of 303002 ***
Comment 2 Dominic Lachowicz 2005-05-04 19:50:54 UTC
fwiw, i feel that marking this as a dupe is a cop-out. 

it's entirely unreasonable for a user to see different behavior between say,
gimp, and gnumeric's menubar. the behavior should be standard and consistent
across the desktop.

i'm not asking for this and bug 303002 to be fixed in the gtk 2.x days, where it
would break APIs and UIs. i'm just asking whether it's perhaps more reasonable
to have widget consistency across apps vs. a non-killer feature like tear-off
combo boxes and menus.

"A spreadsheet might want its color selection dropdown to be able to
be torn off, and disabling that would "break" the interface."

the reason i filed this bug is because we were hacking on gnumeric and wanted
its custom combo box widget's behavior to be consistent with the rest of the
platform. i'm willing to bet that widely enforced consistency is preferable to
the 1 app on the desktop that absolutely "*needs*" tearoff menus and ComboBoxes.
Comment 3 Owen Taylor 2005-05-04 20:05:22 UTC
It wsan't a copout, is was too quick reading of the subject. (Hitting
submit twice is *very* common)

If you believe bug 302002 was closed inappropriately, please respond
there and reopen.
Comment 4 Owen Taylor 2005-05-04 20:12:35 UTC
I don't know the rationale for GtkUIManager::add-tearoff, maybe
Matthias remembers.

Since when we added it, we were aware of style properties and GtkSettings
(this certainly is more of a GtkSetting thing than a style property 
thing .. it couldn't even *be* a style property because there is no
widget), I suspect that it was added because some app needed it
in particular.

We used to have a global setting in gnome to make all menus tearoff,
but that was clearly a horribly bad idea.

If a style property was added here, it would have to be something
like never-make-menus-tearoff or something. But I don't see 
tearoff vs. not as a platform thing, precisely because a "menus
get torn off" platform would be a stupid platform.
Comment 5 Owen Taylor 2005-07-26 23:01:16 UTC
My opinion is that if you have an app where you think you need it,
that app needs to just stop turning on tearoffs.
Comment 6 Dominic Lachowicz 2005-07-27 00:20:25 UTC
whatever