unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Robert Pluim <rpluim@gmail.com>
Cc: 27830@debbugs.gnu.org, kaushal.modi@gmail.com, dgutov@yandex.ru
Subject: bug#27830: 26.0.50; Left fringe gets truncated by a pixel in window not sharing that edge with frame
Date: Wed, 11 Oct 2017 10:33:42 +0200	[thread overview]
Message-ID: <59DDD766.70300@gmx.at> (raw)
In-Reply-To: <87infno0ew.fsf@gmail.com>

 > Yes. In other GTK apps you can hold the mouse anywhere near the edge
 > of a scroll bar and resize it that way, but that's a feature for
 > another day.

Either the application must be able to discern scroll bar and border
drags from the direction of the initial drag (if the drag occurs on the
scroll bar) or you have no visual indication of the area where such an
operation is defined until we show some sort of resize arrow.  And then
that resize arrow will always pop up when the mouse gets too near to a
border.  Even if we make all of this customizable, it's still clumsy.

I earlier used code that allowed to resize windows by dragging a fringe
but didn't like it much either.

martin





  reply	other threads:[~2017-10-11  8:33 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-25 20:19 bug#27830: 26.0.50; Left fringe gets truncated by a pixel in window not sharing that edge with frame Kaushal Modi
2017-07-26  7:53 ` martin rudalics
2017-10-03 20:19   ` Kaushal Modi
2017-10-04  9:04     ` martin rudalics
2017-10-04 13:47       ` Kaushal Modi
2017-10-04 13:54         ` Kaushal Modi
2017-10-05  8:11           ` martin rudalics
2017-10-05  8:47             ` Eli Zaretskii
2017-10-05 11:59               ` Kaushal Modi
2017-10-06  8:17               ` martin rudalics
2017-10-06  9:45                 ` Eli Zaretskii
2017-10-07  8:08                   ` martin rudalics
2017-10-07  8:24                     ` Eli Zaretskii
2017-10-07  9:44                       ` martin rudalics
2017-10-07  9:51                         ` Eli Zaretskii
2017-10-09  7:59                           ` martin rudalics
2017-10-09  8:28                             ` Eli Zaretskii
2017-10-09 12:21                               ` martin rudalics
2017-10-09 12:53                                 ` Kaushal Modi
2017-10-10  8:12                                   ` martin rudalics
2017-10-09 13:41                                 ` Robert Pluim
2017-10-10  8:14                                   ` martin rudalics
2017-10-10  8:46                                     ` Robert Pluim
2017-10-11  8:33                                       ` martin rudalics [this message]
2020-09-04  5:25                             ` Lars Ingebrigtsen
2017-10-05  8:10         ` martin rudalics
2017-10-05  8:29           ` martin rudalics
2017-10-05 11:51             ` Kaushal Modi
2017-10-06  8:18               ` martin rudalics
2017-10-05 11:46           ` Kaushal Modi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=59DDD766.70300@gmx.at \
    --to=rudalics@gmx.at \
    --cc=27830@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=kaushal.modi@gmail.com \
    --cc=rpluim@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).