kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

On 10/20/18 3:39 PM, Jeff Young wrote:
> Hi Seth,
>
> Yes, sorry, graphic items.
>
> The problem is the initial snap.  Let’s say I have an item at [100, 25] and my snap/zoom resolution is currently set to 2.  If I right arrow key then I’m expecting [102, 25] but what I get is [102, 24] (or maybe [102, 26] depending on rounding).  That move on the Y-axis in response to an X-axis keystroke is what’s annoying.
>
> Cheers,
> Jeff.
>
> BTW: did either you or Wayne get a chance to try out the escaping-labels-and-netnames patch?

Not yet.  It's on my list for tomorrow.

> > On 20 Oct 2018, at 16:34, Seth Hillbrand <seth@xxxxxxxxxxxxx> wrote:
> >
> > Am 2018-10-20 10:12, schrieb Jeff Young:
> > > I built up a pretty big board (at least for me) over the last week
> > > with 6.0.  No major issues.
> > > The most annoying one is that when moving objects with ‘m’ and then
> > > the arrow keys, it can move on the wrong axis if I’m zoomed out a bit.
> > > If I zoom in far enough to see the lowest level of grid dots, it
> > > works correctly.
> > > Is this because the arrow keys are snapping to screen pixels as well
> > > as the grid?  If so, can we remove that part?
> >
> > Hi Jeff-
> >
> > Assuming you are talking about snapping graphical items and not routing, the snap distance is defined in terms of screen distance.  So if you are zoomed out, your move will more easily snap to nearby items.
> >
> > I think that if a user is using the keyboard, they expect exact movement along the grid with no snapping to items.  However, I think the user should still see the "snapped" circle when they move over the exact snap point.
> >
> > -S
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp