DJ Delorie wrote:
>> At that zoom there are still some issues with the scale being so
>> small that there's still ambiguity.
>>
>
> I'm not sure any code changes will give you a bigger screen ;-)
>
>
Ah - but how about a magnifying glass over the cursor.
_
> At that zoom there are still some issues with the scale being so
> small that there's still ambiguity.
I'm not sure any code changes will give you a bigger screen ;-)
___
geda-user mailing list
geda-user@moria.seul.org
http://www.seul.org/cgi-bin/ma
The new pin snap is a big improvement. I just routed a bus from a TSSOP
to a QFP and I was able to do it from a zoom where I could see both parts
and still have confidence that I was hitting the pin.
At that zoom there are still some issues with the scale being so small
that there's still ambigui
Um, yeah... In crosshair.c FitCrosshairIntoGrid(), look for:
if (ans & PAD_TYPE)
And just don't update x0, y0 if the pad isn't on the right layer. If
nobody gets to it, I'll do it eventually, but this is a great "getting
started" project :-)
___
On Mon, 12 Nov 2007 20:42:28 +, Kai-Martin Knaak wrote:
>> When "crosshair snaps to pins and pads" is checked, by default the
>> crosshair snaps whenever the cursor is within the pin/pad copper, even
>> if a grid point is closer.
Just tried it for my current board --- Snapping feels a lot bet
On Mon, 12 Nov 2007 14:31:40 -0500, DJ Delorie wrote:
> When "crosshair snaps to pins and pads" is checked, by default the
> crosshair snaps whenever the cursor is within the pin/pad copper, even
> if a grid point is closer.
Nice. This will enhance to click-to-click usability. I often find myself
When "crosshair snaps to pins and pads" is checked, by default the
crosshair snaps whenever the cursor is within the pin/pad copper, even
if a grid point is closer.
If you hold the shift key, the crosshair snaps to the grid point if
it's closer (the "old" way).
_
7 matches
Mail list logo
