Formatting Xref net labels

Hi,

On 11/19/12 22:49, Vidar (Z) wrote:

Hi

 

Normally I have used only the text-based net labels on line that goes

from one sheet to another. My wish is to use the XREF option but I am

not comfortable with the format options.

 

My "big" problem is that the signal name for a given net label comes

inside the flag. I would prefer all symbols to be of equal size and to

have the text align on beside of the net flag instead.

 

not like this            but like this

  ______________________          _____

/NETLABEL_SIGNAL_NAME |       /     | NETLABEL_SIGNAL_NAME

\______________________|        \_____|

 

If not existing as an option already I would recommend to make the order

of the label xref formatting tags relevant (as set in misc menu) to the

result. Se my examples below:

 

                 ________________

%F%N (%S)      / NETLABEL (1)  |

                \________________|

 

                 _____

%N %F(%S)      / (1) | NETLABEL

                \_____|

                 _____

%N (%S)%F      /     | NETLABEL (1)

                \_____|

 

Here everything coming in front of the %F tag ends up outside the flag

and everything after %F ends up inside. The flag symbol would thus have

a minimum size like say 3 letters.

 

Second. Is it possible to have flags indicating direction of a net? I.e.

if signal is in, out or bidirectional. This should be possible to change

with a change command like for example CHANGE DIRECTION or CHANGE FLAG

if not existing as an option already somewhere.

 

input             bi              output

  _______          ______         ______

_/       |       /      \       |      \

\_______|        \______/       |______/

 

Thanks, but some questions on this:

- What flags would you set if the net has many (>2) pin connections ?

- How should it behave is a user has a net with unlogical connections, say input - input ?

This can cause confusion.

Regards,

Walter Spermann

 

NOTE: I asked this as an question in the support forum, but as mentioned

there I would put it here as a suggestion if it was not possible in some

other way already. As far as I can see, it is not, though I am using

glasses....!*

 

Breg

Vidar (Z)

--

-

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

-

I do not care about text OUTSIDE the label frame (it will always stay

INSIDE for me), but I also would very much like to see in/out/bi labels

as outlined.

Am 20.11.2012 18:22, schrieb Walter Spermann:

>> input             bi              output

>>    _______          ______         ______

>> _/       |       /      \       |      \

>>   \_______|        \______/       |______/

>>

Thanks, but some questions on this:

  - What flags would you set if the net has many (>2) pin connections ?

The form of the label MUST NOT be set automatically! Please leave it in

the responsibility of the user to select the appropriate form and make

the following choices available: INPUT and OUTPUT and BIDIRECTIONAL as

shown above, and perhaps even RECTANGLE, which is a simple surrounding

rectangle with no directional information.

  - How should it behave is a user has a net with unlogical connections, say input - input ?

As stated above, the label form is NOT changed automatically, and

therefore, no 'behaviour' is necessary at all. Also, please no ERC

checks or anything else. Just graphics. Easy to program, no hassles, no

automatisms.

This can cause confusion.

Without automatisms, confusion won't be possible (other than the user

labelling nets with the WRONG graphics, but that's the user's fault,

then, and not CadSoft's).

Andreas Weidner

On 11/21/2012 10:25 AM, Andreas Weidner wrote:

I do not care about text OUTSIDE the label frame (it will always stay

INSIDE for me), but I also would very much like to see in/out/bi labels

as outlined.

By implementing the proposed 'position dependent xref tag setup' Eagle

will become flexible enough to meet most peoples wishes in a simple

manner. A program that puts the user in the front seat is a good

program. (well almost always). Eagle should default to already existing

xref formatting of-course and leaving it up to the user to change it to

whatever they need.

 

As stated above, the label form is NOT changed automatically, and

therefore, no 'behaviour' is necessary at all. Also, please no ERC

checks or anything else. Just graphics. Easy to program, no hassles, no

automatisms.

This can be made as an option to choose automated direction setting

based on the nearest pin, or if it must be set manually. I guess

defaulting to 'input' is the most logical choice when set to manual

since the existing flag label has the form of an input flag.

But, I my self agree that only manual setting of the direction is

necessary as it also force the user to think throughly through the

design. That has never hurt anyone and as also stated, the flag is only

a way of visualizing the actual signal flow and making a schematic more

readable

ERC should off course not reflect if the chosen label flag direction

shows the direction of the pin connected to or not. A flag showing a

direction is, once again, only a visualization of the signal flow as

seen from the user perspective view, and it must be possible to set to

whatever direction one wants regardless of the direction of the pin one

connects to.

This is called KIS design (Keep It Simple)

>> This can cause confusion.

 

Without automatisms, confusion won't be possible (other than the user

labelling nets with the WRONG graphics, but that's the user's fault,

then, and not CadSoft's).

 

In the end, what brings confusion is highly individual. So in stead of

arguing for or against I repeat the humble words of Aristotle:

"To say of what is that it is not, or of what is not that it is, is

false, while to say of what is that it is, and of what is not that it is

not, is true."

Breg

Vidar (Z)

On 11/21/2012 10:25 AM, Andreas Weidner wrote:

I do not care about text OUTSIDE the label frame (it will always stay

INSIDE for me), but I also would very much like to see in/out/bi labels

as outlined.

By implementing the proposed 'position dependent xref tag setup' Eagle

will become flexible enough to meet most peoples wishes in a simple

manner. A program that puts the user in the front seat is a good

program. (well almost always). Eagle should default to already existing

xref formatting of-course and leaving it up to the user to change it to

whatever they need.

 

As stated above, the label form is NOT changed automatically, and

therefore, no 'behaviour' is necessary at all. Also, please no ERC

checks or anything else. Just graphics. Easy to program, no hassles, no

automatisms.

This can be made as an option to choose automated direction setting

based on the nearest pin, or if it must be set manually. I guess

defaulting to 'input' is the most logical choice when set to manual

since the existing flag label has the form of an input flag.

But, I my self agree that only manual setting of the direction is

necessary as it also force the user to think throughly through the

design. That has never hurt anyone and as also stated, the flag is only

a way of visualizing the actual signal flow and making a schematic more

readable

ERC should off course not reflect if the chosen label flag direction

shows the direction of the pin connected to or not. A flag showing a

direction is, once again, only a visualization of the signal flow as

seen from the user perspective view, and it must be possible to set to

whatever direction one wants regardless of the direction of the pin one

connects to.

This is called KIS design (Keep It Simple)

>> This can cause confusion.

 

Without automatisms, confusion won't be possible (other than the user

labelling nets with the WRONG graphics, but that's the user's fault,

then, and not CadSoft's).

 

In the end, what brings confusion is highly individual. So in stead of

arguing for or against I repeat the humble words of Aristotle:

"To say of what is that it is not, or of what is not that it is, is

false, while to say of what is that it is, and of what is not that it is

not, is true."

Breg

Vidar (Z)