I am missing a possibility to enter an offset or zero point to the grid I selected, With the different Pitches and the mix of inches and metric I often have to switch and it would realy help if I could switch the offset to.
Kind regards
John
I am missing a possibility to enter an offset or zero point to the grid I selected, With the different Pitches and the mix of inches and metric I often have to switch and it would realy help if I could switch the offset to.
Kind regards
John
Hi,
On 02/14/13 23:37, John van Zijl wrote:
I am missing a possibility to enter an offset or zero point to the grid I selected, With the different Pitches and the mix of inches and metric I often have to switch and it would realy help if I could switch the offset to.
Kind regards
John
--
To view any images and attachments in this post, visit:
http://www.element14.com/community/message/69588#69588/l/grid-offset
the MARK command is not sufficient for this ?
Walter Spermann
--
-
Walter Spermann
Softwareentwicklung
CadSoft Computer GmbH
Pleidolfweg 15
84568 Pleiskirchen
Tel.: 08635/6989-10
www.cadsoft.de
-
Registergericht: Amtsgericht Traunstein HRB 5573
Geschäftsführer: Thomas Liratsch
-
Walter Spermann schrieb:
I am missing a possibility to enter an offset or zero point to the
grid I selected, With the different Pitches and the mix of inches
and metric I often have to switch and it would realy help if I
could switch the offset to.
the MARK command is not sufficient for this ?
NO. It affects only display and allows for "relative" coordinate entry,
but it does not modify the grid "snap" for any mouse movement.
Tilmann
Am 18.02.2013 13:53, schrieb Tilmann Reh:
the MARK command is not sufficient for this ?
NO. It affects only display and allows for "relative" coordinate entry,
but it does not modify the grid "snap" for any mouse movement.
The current grid behaviour has at least two problems that get
increasingly annoying with 'modern' electronic components:
1. As stated above, the grid should have a selectable origin, so
that the snapping works properly.
This is not SO important for the package editor, but for the
'real' board: There, one sometimes has mechanical restrictions
like 'this part MUST go here, and those LEDs should each have
0.1" distance from THIS point which, unfortunately, is NOT
on the grid'. It IS possible to solve this problem now, but
only with a piece of paper and manual coordinate entry.
2. It should be possible to have a DIFFERENT grid distance for
horizontal and vertical directions.
This is not SO important for the board editor, but for the
package editor: Though I thoroughly HATE components that have
a millimeter grid in one direction and inches in the other,
such bloody components DO exist. And components with different
inch grids in both directions are not SO rare. At the moment,
this can only be solved by manually switching between grid
settings a thousand times.
I suggest the following:
3. Introduce three additional keywords for the GRID command:
- VERT: Works like the ALT keyword, only that following
characters change the VERTICAL grid settings
- HORZ: Ditto, only with the HORIZONTAL settings
- ORIGIN: Must be followed by a point (x,y)
If none of these is given in the command, it behaves just
as usual. Examples:
- GRID Inch 0.1 Lines On; [sets 0.1" in BOTH directions]
- GRID Horz Inch 0.1; [sets 0.1" horizontally AND
LEAVES THE VERTICAL GRID
UNCHANGED]
- GRID Horz Inch 0.1 Vert mm 3.75;
- GRID Origin (1inch 2mm);
- GRID Origin (1inch 2mm) Horz Inch 0.1 Vert mm 3.75 Lines On;
The only things that I don't know at the moment is a) how to
define the ALT grid horizontally or vertically and b) what to
do with the multiplier.
4. Lines/dots and on/off should always work for BOTH directions.
5. The grid dialog should be changed accordingly. I'll think about
this and mail you again.
Andreas Weidner
Am 18.02.2013 13:53, schrieb Tilmann Reh:
the MARK command is not sufficient for this ?
NO. It affects only display and allows for "relative" coordinate entry,
but it does not modify the grid "snap" for any mouse movement.
The current grid behaviour has at least two problems that get
increasingly annoying with 'modern' electronic components:
1. As stated above, the grid should have a selectable origin, so
that the snapping works properly.
This is not SO important for the package editor, but for the
'real' board: There, one sometimes has mechanical restrictions
like 'this part MUST go here, and those LEDs should each have
0.1" distance from THIS point which, unfortunately, is NOT
on the grid'. It IS possible to solve this problem now, but
only with a piece of paper and manual coordinate entry.
2. It should be possible to have a DIFFERENT grid distance for
horizontal and vertical directions.
This is not SO important for the board editor, but for the
package editor: Though I thoroughly HATE components that have
a millimeter grid in one direction and inches in the other,
such bloody components DO exist. And components with different
inch grids in both directions are not SO rare. At the moment,
this can only be solved by manually switching between grid
settings a thousand times.
I suggest the following:
3. Introduce three additional keywords for the GRID command:
- VERT: Works like the ALT keyword, only that following
characters change the VERTICAL grid settings
- HORZ: Ditto, only with the HORIZONTAL settings
- ORIGIN: Must be followed by a point (x,y)
If none of these is given in the command, it behaves just
as usual. Examples:
- GRID Inch 0.1 Lines On; [sets 0.1" in BOTH directions]
- GRID Horz Inch 0.1; [sets 0.1" horizontally AND
LEAVES THE VERTICAL GRID
UNCHANGED]
- GRID Horz Inch 0.1 Vert mm 3.75;
- GRID Origin (1inch 2mm);
- GRID Origin (1inch 2mm) Horz Inch 0.1 Vert mm 3.75 Lines On;
The only things that I don't know at the moment is a) how to
define the ALT grid horizontally or vertically and b) what to
do with the multiplier.
4. Lines/dots and on/off should always work for BOTH directions.
5. The grid dialog should be changed accordingly. I'll think about
this and mail you again.
Andreas Weidner
On 02/18/13 14:41, Andreas Weidner wrote:
Am 18.02.2013 13:53, schrieb Tilmann Reh:
the MARK command is not sufficient for this ?
NO. It affects only display and allows for "relative" coordinate entry,
but it does not modify the grid "snap" for any mouse movement.
The current grid behaviour has at least two problems that get
increasingly annoying with 'modern' electronic components:
1. As stated above, the grid should have a selectable origin, so
that the snapping works properly.
This is not SO important for the package editor, but for the
'real' board: There, one sometimes has mechanical restrictions
like 'this part MUST go here, and those LEDs should each have
0.1" distance from THIS point which, unfortunately, is NOT
on the grid'. It IS possible to solve this problem now, but
only with a piece of paper and manual coordinate entry.
2. It should be possible to have a DIFFERENT grid distance for
horizontal and vertical directions.
This is not SO important for the board editor, but for the
package editor: Though I thoroughly HATE components that have
a millimeter grid in one direction and inches in the other,
such bloody components DO exist. And components with different
inch grids in both directions are not SO rare. At the moment,
this can only be solved by manually switching between grid
settings a thousand times.
I suggest the following:
3. Introduce three additional keywords for the GRID command:
- VERT: Works like the ALT keyword, only that following
characters change the VERTICAL grid settings
- HORZ: Ditto, only with the HORIZONTAL settings
- ORIGIN: Must be followed by a point (x,y)
If none of these is given in the command, it behaves just
as usual. Examples:
- GRID Inch 0.1 Lines On; [sets 0.1" in BOTH directions]
- GRID Horz Inch 0.1; [sets 0.1" horizontally AND
LEAVES THE VERTICAL GRID
UNCHANGED]
- GRID Horz Inch 0.1 Vert mm 3.75;
- GRID Origin (1inch 2mm);
- GRID Origin (1inch 2mm) Horz Inch 0.1 Vert mm 3.75 Lines On;
The only things that I don't know at the moment is a) how to
define the ALT grid horizontally or vertically and b) what to
do with the multiplier.
4. Lines/dots and on/off should always work for BOTH directions.
5. The grid dialog should be changed accordingly. I'll think about
this and mail you again.
Andreas Weidner
In many cases the alternate grid should also be helpful.
You can have different units for both grids, but I agree, such extensions
sound reasonable. Thanks !
Walter Spermann
--
-
Walter Spermann
Softwareentwicklung
CadSoft Computer GmbH
Pleidolfweg 15
84568 Pleiskirchen
Tel.: 08635/6989-10
www.cadsoft.de
-
Registergericht: Amtsgericht Traunstein HRB 5573
Geschäftsführer: Thomas Liratsch
-
On 02/18/2013 08:41 AM, Andreas Weidner wrote:
Am 18.02.2013 13:53, schrieb Tilmann Reh:
the MARK command is not sufficient for this ?
NO. It affects only display and allows for "relative" coordinate entry,
but it does not modify the grid "snap" for any mouse movement.
The current grid behaviour has at least two problems that get
increasingly annoying with 'modern' electronic components:
1. As stated above, the grid should have a selectable origin, so
that the snapping works properly.
This is not SO important for the package editor, but for the
'real' board: There, one sometimes has mechanical restrictions
like 'this part MUST go here,
For exact placement of parts, I always use the command line.
MOVE R1 (101 123.456);
Or click move, then the part, then type in (101 123.456);
and those LEDs should each have
0.1" distance from THIS point which, unfortunately, is NOT
on the grid'. It IS possible to solve this problem now, but
only with a piece of paper and manual coordinate entry.
Try:
MARK (101 123.4);
MOVE LED1 (R100 0);
MOVE LED2 (R200 0);
The "R" in the coordinates specify a coordinate relative to the mark.
In this example, LED1 would be placed 0.1 units to the right of the
mark. Polar coordinates are also available.
2. It should be possible to have a DIFFERENT grid distance for
horizontal and vertical directions.
This is not SO important for the board editor, but for the
package editor: Though I thoroughly HATE components that have
a millimeter grid in one direction and inches in the other,
such bloody components DO exist. And components with different
inch grids in both directions are not SO rare. At the moment,
this can only be solved by manually switching between grid
settings a thousand times.
Not a bad idea. I usually route the last leg from the SMD pad to a wire
rather than from the wire to the SMD pad. The latter always leaves an
obfuscated short segment from the grid to the center of the pad. If you
route from the pad, this short segment is at the other end of the wire
segment.
Your enhancement request deserves consideration. I just point out that
there are ways around it - until it can be included in a release.
Enjoy,
- Chuck
6327.att1.html.zip |
Am 21.02.2013 14:12, schrieb Chuck Huber:
For exact placement of parts, I always use the command line.
Yes. I'm a BIG fan of the command line (it's ONE reason why I use EAGLE
and not some other software).
BUT you still have to calculate things like "horizontal three times
3.75mm, wait a moment, errrrrm, and vertical five times 0.15inch." Of
course it is possible, but with a nice grid that would be much easier.
Andreas Weidner
On 02/21/2013 09:49 AM, Andreas Weidner wrote:
Am 21.02.2013 14:12, schrieb Chuck Huber:
For exact placement of parts, I always use the command line.
Yes. I'm a BIG fan of the command line (it's ONE reason why I use
EAGLE and not some other software).
BUT you still have to calculate things like "horizontal three times
3.75mm, wait a moment, errrrrm, and vertical five times 0.15inch." Of
course it is possible, but with a nice grid that would be much easier.
I have often had to do a step-and-repeat kind of placement. LED's,
resistors, etc..
It's worth noting that coordinates on the command line do not have to be
of the same unit, or even the grid unit.
MARK (3.75mm 0.15in);
It's also worth noting that you can move the mark relative to its own
position. So I set the mark at the start point, place the component
relative to the mark, then step the mark. It gets pretty easy using
relative positions and the up-arrow for command history.
MARK (12 12);
MOVE R1 (R0 0);
MARK (R3.75mm 0.15in);
MOVE R2 (0 0);
Now I can up-arrow twice to repeat the relative movement of the mark,
and move the next component.
So there's your good old fashioned, home grown, red-blooded, all
American, mixed-unit coordinate step and repeat.
HTH,
- Chuck
7024.att1.html.zip |