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:date:message-id:subject:from:to:content-type;
	bh=5Osmp3PHhJTU+QIkwyASi0HEKcdxRh+LDyxgPt2x780=;
	b=GkkdmskCAj9QpQU9WH1YgfDa7tWAcX4L9G6J4fFv30vpTWd55PUlbz30ovTIYUP6LA
	PAyvYSzmjgPwDXKnEHpIZhEqR2XW+ro7EXLf3YiRgLpU9vkm7PS6qa/JNT03ecYB4QNu
	HV0HGQgzQ3l128wacGXLxQ0TpC9sTLNIh/vOrJTH3850D4U8qGtwLjEsM19n6Vfc9rRU
	xPONfaYykXDLNFr6KE+aNkNDskcr2/jkpccOAKZh19fjVJajU/NAQOqk4zigQCa5+Miu
	RRd7C5cfPnOOV35X6Xj3gAzJ2qg3kxqoLO14YtyB+PyKJn0Wnnc6zbImGddBBYE2gGIJ
	DwBQ==
MIME-Version:	1.0
X-Received:	by 10.194.109.97 with SMTP id hr1mr49122785wjb.38.1442388817700;
	Wed, 16 Sep 2015 00:33:37 -0700 (PDT)
Date:	Tue, 15 Sep 2015 23:33:37 -0800
Message-ID:	<CAC4O8c9G5T-Mf7nBMvy9ozN0VVQ47Qvm4Gni_d8U1brH-4ZLyQ@mail.gmail.com>
Subject:	[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]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Reply-To:	geda-user AT delorie DOT com

--089e01494b381b6f8f051fd8514f
Content-Type: text/plain; charset=UTF-8

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

It could be just:

   click_on_violation -> zoom

At the cost of pointer warping which some people find weird and might work
different with
different window managers.

The other HIDs probably still don't pan correctly because CenterDisplay()
got hacked to not actually center the display.  It looks like the
HID_SC_PAN_VIEWPORT option of set_crosshair might work right for lesstif at
least (it was quite broken for gtk).

I think these bugs come from the strange definition of set_crosshair in
hid.h.  Its only used during DRC check and really you always want
PAN_VIEWPORT, and can just decide once and for all on pointer warp (I tend
to say no).  set_crosshair without pan makes for a big inconsistency and
WARP_POINTER without pan is worse.

--089e01494b381b6f8f051fd8514f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div style=3D"">I made a fix to make gtk pan correctly=
 to violation and put crosshair on it.</div><div style=3D""><br></div><div =
style=3D"">I could add in pointer warping but maybe people dont want it?</d=
iv><div style=3D""><br></div><div style=3D"">Now the work flow is:</div><di=
v style=3D""><br></div><div style=3D"">=C2=A0 =C2=A0click_on_violation -&gt=
; point_at_crosshair -&gt; zoom=C2=A0</div><div style=3D""><br></div><div s=
tyle=3D"">It could be just:</div><div style=3D""><br></div><div style=3D"">=
=C2=A0 =C2=A0click_on_violation -&gt; zoom</div><div style=3D""><br></div><=
div style=3D"">At the cost of pointer warping which some people find weird =
and might work different with</div><div style=3D"">different window manager=
s.</div><div style=3D""><br></div><div style=3D"">The other HIDs probably s=
till don&#39;t pan correctly because CenterDisplay() got hacked to not actu=
ally center the display.=C2=A0 It looks like the HID_SC_PAN_VIEWPORT option=
 of set_crosshair might work right for lesstif at least (it was quite broke=
n for gtk).</div><div style=3D""><br></div><div style=3D"">I think these bu=
gs come from the strange definition of set_crosshair in hid.h.=C2=A0 Its on=
ly used during DRC check and really you always want PAN_VIEWPORT, and can j=
ust decide once and for all on pointer warp (I tend to say no). =C2=A0set_c=
rosshair without pan makes for a big inconsistency and WARP_POINTER without=
 pan is worse.</div></div>

--089e01494b381b6f8f051fd8514f--

- Raw text -