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 339093 - shortcuts conflict in composer: control + 8
shortcuts conflict in composer: control + 8
Status: RESOLVED FIXED
Product: GtkHtml
Classification: Other
Component: Editing
3.10.x
Other Linux
: Normal trivial
: ---
Assigned To: gtkhtml-maintainers
Evolution QA team
evolution[composer]
Depends on: 317386
Blocks: 310552
 
 
Reported: 2006-04-19 22:40 UTC by André Klapper
Modified: 2008-03-27 10:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
patch (1.20 KB, patch)
2006-04-20 10:51 UTC, Rohini
reviewed Details | Review
proposed gtkhtml patch (updated one) (1.20 KB, patch)
2008-03-11 17:08 UTC, Milan Crha
needs-work Details | Review
proposed gtkhtml patch ][ (3.00 KB, patch)
2008-03-12 12:29 UTC, Milan Crha
committed Details | Review

Description André Klapper 2006-04-19 22:40:15 UTC
in the composer, the shortcut Control+0 is both used for "HeadingNormal" format and "TextZoomReset" to chance the text zoom. => currently i can change the text zoom by "control"+"+", but i cannot reset it to the default zoom.
proposal: change "HeadingNormal" to Control+9 which is currently unused. not that cool, but no idea otherwise. :-/
Comment 1 Karsten Bräckelmann 2006-04-20 01:09:30 UTC
Hmm, I disagree with the proposed fix.

IMHO there is absolutely no reason to support changing a zoom level in the Composer. If changing this would be useful, the user is using a bad font size he should not use and most likely doesn't even want to use. The point is, if I can't read what I type, how could I possibly expect the recipient to?

My proposal would be to nuke the shortcuts for the zoom level entirely.

Note that this is a hidden gimmick, which is not available from any menu anyway. I assume this "feature" went in by accident. Honestly, I didn't even know this is possible till now...

On the other hand, Ctrl-0 is used for Paragraph Style "Normal" for a long time already.


Also, this is the Composer. GtkHTML/Editing. Dude... ;-)
Comment 2 Rohini 2006-04-20 03:49:19 UTC
Andre, It's Ctrl + 9 that is used to reset zoom.
Comment 3 André Klapper 2006-04-20 10:11:39 UTC
rohini, yes, but is that intentional? see bug 317386. where is this shortcut located in the code? i'm unable to find it.

even if the zoom is set to default by using control+9 (in composer) instead of control+0 (like it's in evo), we have the conflict that control+8 both means 
"HeadingAddress" and "text zoom-in", as it was in former times before we changed over to use control++ to keep consistency. so "HeadingAddress" does not work.

/me slightly modifies the subject, dumdidum... s/0/8

guenther: right. let's REMOVE text zoom in composer. but only after providing a howto here how to set the text size in composer. ;-)
Comment 4 Rohini 2006-04-20 10:50:45 UTC
ctrl + 0 conflicts with zoom out and normal.

Because there's already a keybinding for zoom in and zoom out. Removing the keybinding Ctrl+8 and Ctrl+0 for zoom would be sufficient.
Comment 5 Rohini 2006-04-20 10:51:28 UTC
Created attachment 63936 [details] [review]
patch
Comment 6 Harish Krishnaswamy 2006-06-12 12:46:50 UTC
The patch provided nukes the conflicting entries but does not necessarily remove the ability to zoom in/out as Karsten has suggested. I'd agree with that rationale.
Comment 7 André Klapper 2006-07-05 11:26:28 UTC
rohini: can you update the patch, please?
Comment 8 Milan Crha 2008-03-11 17:08:09 UTC
Created attachment 107075 [details] [review]
proposed gtkhtml patch (updated one)

for gtkhtml;

Let's see if someone will yell after this patch applied :)
Comment 9 André Klapper 2008-03-11 19:08:00 UTC
milan, the patch means that zooming still works for the main window (not composer), right? if so, it looks useful.
Comment 10 Milan Crha 2008-03-11 20:17:17 UTC
Nope, it was the thing I didn't understand completely, so this short cut can only work in non-composer, hmm, I should change the patch then.
Comment 11 Milan Crha 2008-03-11 21:11:29 UTC
It will be a gross hack, really. I cannot remove the binding based on the is_editable value, because the binding is for the class, not for the object. Really nice. So some hack for 'command' function with indication whether command comes from the binding or not and if yes, then ignore it in editable mode. It will be wondefull :)
Comment 12 Milan Crha 2008-03-12 12:29:38 UTC
Created attachment 107140 [details] [review]
proposed gtkhtml patch ][

for gtkhtml;

The hack as I wrote above.
Comment 13 Srinivasa Ragavan 2008-03-27 04:56:14 UTC
Seems fine. Commit to trunk. 
Comment 14 Milan Crha 2008-03-27 10:31:34 UTC
Committed to trunk. Committed revision 8792.