X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=472PM8Tlyv0aa6aGmDNXdyGgt1Il7Ut30zD34MAEqQQ=; b=Kw5fe8HIEk0kTHc6pME2Hq0ykoCZj637XQc6edj1BtVYqnKY+D5d6RM2gnwQVusYIT S4H85mnkKpV7KH0jpVbiINI3X9K7/rzmGkmhZxcsmYGPKjluM9EhHZoDo/h5QYrHHaEb qw6X/yIoaxWc47bJ1A9oQ3eJslwuKadJgSjHUBIkavhIEY3k8CV6JeJSK+5d2eF2280P X6Bh/h+OOq+IN7aui9GODLDN1fH1H/MHuM4thvzqWLRytM3J2ho+HCgNTWU+G+Vtr/bc /n+REQDHjiCW+7x4qtZIGU623LOtx3AkkLBsTsdRo6a7L7U0JJqy8OWExOYkVKIrhCBG H+Uw== MIME-Version: 1.0 X-Received: by 10.180.89.101 with SMTP id bn5mr1656421wib.20.1442447880264; Wed, 16 Sep 2015 16:58:00 -0700 (PDT) In-Reply-To: <55F92747.9030201@m0n5t3r.info> References: <55F92747 DOT 9030201 AT m0n5t3r DOT info> Date: Wed, 16 Sep 2015 15:58:00 -0800 Message-ID: Subject: Re: [geda-user] DRC pan/crosshair/pointer warp fixes and options From: "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Content-Type: multipart/alternative; boundary=f46d0444eba382a128051fe611c8 Reply-To: geda-user AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: geda-user AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk --f46d0444eba382a128051fe611c8 Content-Type: text/plain; charset=UTF-8 On Wed, Sep 16, 2015 at 12:24 AM, Sabin Iacob (iacobs AT m0n5t3r DOT info) [via geda-user AT delorie DOT com] wrote: > On 09/16/2015 10:33 AM, Britton Kerin (britton DOT kerin AT gmail DOT com) [via > geda-user AT delorie DOT com] wrote: > > > > I made a fix to make gtk pan correctly to violation and put crosshair > > on it. > > > > I could add in pointer warping but maybe people dont want it? > > > > Now the work flow is: > > > > click_on_violation -> point_at_crosshair -> zoom > > > this is much better than the current situation; however, doesn't the > crosshair follow the mouse? won't attempting to point at the crosshair > move it? > Yep. Funny what you don't notice when testing. So you can potentially get lost on your way to the main window, with only a little tiny purple part to show where you want to go. Presumably this is why pointer warping was done in the first place. Given this I think warp is the way to go. For gnome it works ok even without focus-follows-mouse on in the window manager, since scroll events still go to the hovered window. mind you, this may not be too big of an issue (you still have the > supposed violation centered and highlighted) > I dunno, it's still weird to have to depend on centering, that takes user training just like warp or worse because it's more subtle. The warp may juke you the first few times but has a payout after that. > > > > It could be just: > > > > click_on_violation -> zoom > > > I'm not sure about others, but I find having the mouse pointer jump to > arbitrary places ... disconcerting > > also, remember that at least Linux window managers are pretty adamant > about focus stealing prevention[1] , so when you click the violation the > mouse would jump somewhere, but the DRC window will stay on top, and it > may cover the place it's trying to point at anyway, so moving the mouse > is meaningless. > Ug you're right. I always put it beside. The main window could perhaps be reliably raised, but maybe its not worth all this. --f46d0444eba382a128051fe611c8 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On Wed, Sep 16, 2015 at 12:24 AM, Sabin Iacob (iacobs AT m0n5t3r DOT info) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:
On 09/16/2015 10:33 AM, Britton = Kerin (britton DOT kerin AT gmail DOT com) [via
geda-user AT delorie= .com] wrote:
>
> I made a fix to make gtk pan correctly to violation and put crosshair<= br> > on it.
>
> I could add in pointer warping but maybe people dont want it?
>
> Now the work flow is:
>
>=C2=A0 =C2=A0 click_on_violation -> point_at_crosshair -> zoom

this is much better than the current situation; however, doesn't= the
crosshair follow the mouse? won't attempting to point at the crosshair<= br> move it?

Yep.=C2=A0 Funny wh= at you don't notice when testing.=C2=A0 So you can potentially get lost= on your way to the main window, with only a little tiny purple part to sho= w where you want to go.=C2=A0 Presumably this is why pointer warping was do= ne in the first place.

Given= this I think warp is the way to go.=C2=A0 For gnome it works ok even witho= ut focus-follows-mouse on in the window manager, since scroll events still = go to the hovered window.

I dunno, it's still weird to have to depend on centeri= ng, that takes user training just like warp or worse because it's more = subtle.=C2=A0 The warp may juke you the first few times but has a payout af= ter that.
=C2=A0
>
> It could be just:
>
>=C2=A0 =C2=A0 click_on_violation -> zoom


I'm not sure about others, but I find having the mouse pointer j= ump to
arbitrary places ... disconcerting

also, remember that at least Linux window managers are pretty adamant
about focus stealing prevention[1] , so when you click the violation the mouse would jump somewhere, but the DRC window will stay on top, and it
may cover the place it's trying to point at anyway, so moving the mouse=
is meaningless.

Ug you'r= e right.=C2=A0 I always put it beside.=C2=A0 The main window could perhaps = be
reliably raised, but maybe its not worth all this.<= /div>
=C2=A0
--f46d0444eba382a128051fe611c8--