element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      • Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Autodesk EAGLE
  • Products
  • More
Autodesk EAGLE
EAGLE User Support (English) Formatting Xref net labels
  • Blog
  • Forum
  • Documents
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Autodesk EAGLE to participate - click to join for free!
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 42 replies
  • Subscribers 182 subscribers
  • Views 6138 views
  • Users 0 members are here
Related

Formatting Xref net labels

zainka
zainka over 13 years ago

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

   _______          ______         ______

_/       |       /      \       |      \

  \_______|        \______/       |______/

 

 

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)

 

  • Sign in to reply
  • Cancel

Top Replies

  • autodeskguest
    autodeskguest over 8 years ago in reply to rachaelp +1
    Hi Jorge, How about having a way to be able to define our own XREF symbols so they match how we like to define our own schematics? Simply add a new pin type in the library editor so we can define a symbol…
  • autodeskguest
    autodeskguest over 8 years ago in reply to autodeskguest +1
    2017-02-15 00:38 keltezéssel, Jorge Garcia írta: Hi Jorge, How about having a way to be able to define our own XREF symbols so they match how we like to define our own schematics? Simply add a new pin…
Parents
  • CSWalt
    CSWalt over 13 years ago

    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

    -


     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Former Member
    Former Member over 13 years ago in reply to CSWalt

    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

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • autodeskguest
    autodeskguest over 9 years ago in reply to autodeskguest

    Just a comment to 1)

    I'd like to have the option for auto direction on this arrow. Since pin

    directions are defined in the devices, eagle can resolve wether the

    segment is connected to some output net, or only input nets, and choose

    direction according to this.

     

    However, not everyone is actively using pin directions on their devices

    (the lazy, sloppy and unskilled ones just set them to i/o or pas), so

    maybe there is a need for a manual direction too. The options for arrow

    direction should be:

    -Auto (based on segment pinrefs)

    -in (always pointing toward the end of the wire)

    -out (always pointing away from the end of the wire)

    -bidir (arrow in both directions)

     

    With auto, there is also some options for live ERC, like the ability to

    detect and show if the net is missing a driver or double driven by

    multiple outputs.

     

    Finally, I wouldn't mind of the xrefs got split into a new primitive

    called pageconnector, and get an attribute containing ALL the

    references. Also the full list of references should be shown at the

    tooltip on mouseover/hover event.

     

    Finally it should be possible to hook it to a bus too.

     

     

    On 12.05.2016 00:19, Márton Miklós wrote:

    Hello all,

     

    Bumping again. After ~2 years...

     

    Is there any information about this feature?

    Is it planned, not planned, if not why, if yes to which version?

     

    Thanks in advance!

    --

    Miklos Marton

     

    2014-03-12 08:48 keltezéssel, vidar vidnes írta:

    I think it's time to re-suggest the original request. Also called

    "bumping"

     

    1) To have the option to change the xref flag direction and shape

               That is: To choose which side the net attaches to the arrow,

    and to choose the shape of the flag (in and out are similar, but bidir

    needs arrow in both ends)

     

    2) One should be able to choose which data to be inside and which to be

    outside the flag by using the formatting options position relative to %F

    ., (Everything AFTER %F is inside the flag)

               thus having the possibility to have equally sized flags all

    over the schematic and the variable length text outside the flag.

     

    3) Not so important.

          *Flag fontsize must be able to change

          *Flag minimum/maximum size should be possible to be configured by

    setting number of characters allowed inside flag

          *Text should be centered along the midline of the flag.

          *wire width the flag is drawn width should be editable

     

    And as the years has passed, I see more and more customer drawings which

    is designed using different tools which have this feature. And to read

    customer drawings where I know the intentional direction by just looking

    at the flag makes things a whole lot more simple. Also when discussing a

    design with someone which is not so skilled in electronics I see how

    much easier it is for them to understand the  designers intention when

    having flags that are pointing out the signals direction.

     

    Breg

    Vidar

     

    --

    To view any images and attachments in this post, visit:

    http://www.element14.com/community/message/106051

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • autodeskguest
    autodeskguest over 9 years ago in reply to autodeskguest

    Just a comment to 1)

    I'd like to have the option for auto direction on this arrow. Since pin

    directions are defined in the devices, eagle can resolve wether the

    segment is connected to some output net, or only input nets, and choose

    direction according to this.

     

    However, not everyone is actively using pin directions on their devices

    (the lazy, sloppy and unskilled ones just set them to i/o or pas), so

    maybe there is a need for a manual direction too. The options for arrow

    direction should be:

    -Auto (based on segment pinrefs)

    -in (always pointing toward the end of the wire)

    -out (always pointing away from the end of the wire)

    -bidir (arrow in both directions)

     

    With auto, there is also some options for live ERC, like the ability to

    detect and show if the net is missing a driver or double driven by

    multiple outputs.

     

    Finally, I wouldn't mind of the xrefs got split into a new primitive

    called pageconnector, and get an attribute containing ALL the

    references. Also the full list of references should be shown at the

    tooltip on mouseover/hover event.

     

    Finally it should be possible to hook it to a bus too.

     

     

    On 12.05.2016 00:19, Márton Miklós wrote:

    Hello all,

     

    Bumping again. After ~2 years...

     

    Is there any information about this feature?

    Is it planned, not planned, if not why, if yes to which version?

     

    Thanks in advance!

    --

    Miklos Marton

     

    2014-03-12 08:48 keltezéssel, vidar vidnes írta:

    I think it's time to re-suggest the original request. Also called

    "bumping"

     

    1) To have the option to change the xref flag direction and shape

               That is: To choose which side the net attaches to the arrow,

    and to choose the shape of the flag (in and out are similar, but bidir

    needs arrow in both ends)

     

    2) One should be able to choose which data to be inside and which to be

    outside the flag by using the formatting options position relative to %F

    ., (Everything AFTER %F is inside the flag)

               thus having the possibility to have equally sized flags all

    over the schematic and the variable length text outside the flag.

     

    3) Not so important.

          *Flag fontsize must be able to change

          *Flag minimum/maximum size should be possible to be configured by

    setting number of characters allowed inside flag

          *Text should be centered along the midline of the flag.

          *wire width the flag is drawn width should be editable

     

    And as the years has passed, I see more and more customer drawings which

    is designed using different tools which have this feature. And to read

    customer drawings where I know the intentional direction by just looking

    at the flag makes things a whole lot more simple. Also when discussing a

    design with someone which is not so skilled in electronics I see how

    much easier it is for them to understand the  designers intention when

    having flags that are pointing out the signals direction.

     

    Breg

    Vidar

     

    --

    To view any images and attachments in this post, visit:

    http://www.element14.com/community/message/106051

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • autodeskguest
    autodeskguest over 9 years ago in reply to autodeskguest

    Am 12.05.2016 um 09:15 schrieb Morten Leikvoll:

    Just a comment to 1)

    I'd like to have the option for auto direction on this arrow. Since pin

    directions are defined in the devices, eagle can resolve wether the

    segment is connected to some output net, or only input nets, and choose

    direction according to this.

     

    That would be nice image

     

     

    However, not everyone is actively using pin directions on their devices

    (the lazy, sloppy and unskilled ones just set them to i/o or pas), so

    maybe there is a need for a manual direction too. The options for arrow

    direction should be:

    -Auto (based on segment pinrefs)

    -in (always pointing toward the end of the wire)

    -out (always pointing away from the end of the wire)

    -bidir (arrow in both directions)

     

    If the direction arrows are done correctly everything is nice.

    However (greetings from orcad) I once had to modify drawings and those

    people gave a damn on correct use of it. I ran into trouble until I

    completely ignored the directions.

    So I'm not  too eager on that, but would be nice to have.

     

     

    With auto, there is also some options for live ERC, like the ability to

    detect and show if the net is missing a driver or double driven by

    multiple outputs.

     

    Finally, I wouldn't mind of the xrefs got split into a new primitive

    called pageconnector, and get an attribute containing ALL the

    references. Also the full list of references should be shown at the

    tooltip on mouseover/hover event.

     

    I don't know if this is practical. Think  of a little project with 15 to

    20 pages and then select "GND"....perhaps it would be better in kind of

    an info line...

     

    Finally it should be possible to hook it to a bus too.

     

    --

    Mit freundlichen Grüßen / With best regards

     

    Joern Paschedag

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • autodeskguest
    autodeskguest over 9 years ago in reply to autodeskguest

    Am 12.05.2016 um 09:15 schrieb Morten Leikvoll:

    Just a comment to 1)

    I'd like to have the option for auto direction on this arrow. Since pin

    directions are defined in the devices, eagle can resolve wether the

    segment is connected to some output net, or only input nets, and choose

    direction according to this.

     

    That would be nice image

     

     

    However, not everyone is actively using pin directions on their devices

    (the lazy, sloppy and unskilled ones just set them to i/o or pas), so

    maybe there is a need for a manual direction too. The options for arrow

    direction should be:

    -Auto (based on segment pinrefs)

    -in (always pointing toward the end of the wire)

    -out (always pointing away from the end of the wire)

    -bidir (arrow in both directions)

     

    If the direction arrows are done correctly everything is nice.

    However (greetings from orcad) I once had to modify drawings and those

    people gave a damn on correct use of it. I ran into trouble until I

    completely ignored the directions.

    So I'm not  too eager on that, but would be nice to have.

     

     

    With auto, there is also some options for live ERC, like the ability to

    detect and show if the net is missing a driver or double driven by

    multiple outputs.

     

    Finally, I wouldn't mind of the xrefs got split into a new primitive

    called pageconnector, and get an attribute containing ALL the

    references. Also the full list of references should be shown at the

    tooltip on mouseover/hover event.

     

    I don't know if this is practical. Think  of a little project with 15 to

    20 pages and then select "GND"....perhaps it would be better in kind of

    an info line...

     

    Finally it should be possible to hook it to a bus too.

     

    --

    Mit freundlichen Grüßen / With best regards

     

    Joern Paschedag

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • autodeskguest
    autodeskguest over 9 years ago in reply to autodeskguest

    Am 12.05.2016 um 09:15 schrieb Morten Leikvoll:

    Just a comment to 1)

    I'd like to have the option for auto direction on this arrow. Since pin

    directions are defined in the devices, eagle can resolve wether the

    segment is connected to some output net, or only input nets, and choose

    direction according to this.

     

    That would be nice image

     

     

    However, not everyone is actively using pin directions on their devices

    (the lazy, sloppy and unskilled ones just set them to i/o or pas), so

    maybe there is a need for a manual direction too. The options for arrow

    direction should be:

    -Auto (based on segment pinrefs)

    -in (always pointing toward the end of the wire)

    -out (always pointing away from the end of the wire)

    -bidir (arrow in both directions)

     

    If the direction arrows are done correctly everything is nice.

    However (greetings from orcad) I once had to modify drawings and those

    people gave a damn on correct use of it. I ran into trouble until I

    completely ignored the directions.

    So I'm not  too eager on that, but would be nice to have.

     

     

    With auto, there is also some options for live ERC, like the ability to

    detect and show if the net is missing a driver or double driven by

    multiple outputs.

     

    Finally, I wouldn't mind of the xrefs got split into a new primitive

    called pageconnector, and get an attribute containing ALL the

    references. Also the full list of references should be shown at the

    tooltip on mouseover/hover event.

     

    I don't know if this is practical. Think  of a little project with 15 to

    20 pages and then select "GND"....perhaps it would be better in kind of

    an info line...

     

    Finally it should be possible to hook it to a bus too.

     

    --

    Mit freundlichen Grüßen / With best regards

     

    Joern Paschedag

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • autodeskguest
    autodeskguest over 9 years ago in reply to autodeskguest

    Am 12.05.2016 um 14:51 schrieb Joern Paschedag:

    Am 12.05.2016 um 09:15 schrieb Morten Leikvoll:

    Just a comment to 1)

    I'd like to have the option for auto direction on this arrow. Since pin

    directions are defined in the devices, eagle can resolve wether the

    segment is connected to some output net, or only input nets, and choose

    direction according to this.

     

    That would be nice image

     

     

    Hi,

     

    currently there are no concrete plans. It's in the todo list, but

    with low priority. I will bring this up for V8 again.

    - Direction for xref labels

    - xref for a bus

     

     

    However, not everyone is actively using pin directions on their devices

    (the lazy, sloppy and unskilled ones just set them to i/o or pas), so

    maybe there is a need for a manual direction too. The options for arrow

    direction should be:

    -Auto (based on segment pinrefs)

    -in (always pointing toward the end of the wire)

    -out (always pointing away from the end of the wire)

    -bidir (arrow in both directions)

     

    If the direction arrows are done correctly everything is nice.

    However (greetings from orcad) I once had to modify drawings and those

    people gave a damn on correct use of it. I ran into trouble until I

    completely ignored the directions.

    So I'm not  too eager on that, but would be nice to have.

     

     

    With auto, there is also some options for live ERC, like the ability to

    detect and show if the net is missing a driver or double driven by

    multiple outputs.

     

    Finally, I wouldn't mind of the xrefs got split into a new primitive

    called pageconnector, and get an attribute containing ALL the

    references. Also the full list of references should be shown at the

    tooltip on mouseover/hover event.

     

    I don't know if this is practical. Think  of a little project with 15 to

    20 pages and then select "GND"....perhaps it would be better in kind of

    an info line...

     

    It's planned to show the occurences of the net in the info dialog.

     

     

     

    Finally it should be possible to hook it to a bus too.

     

     

    --

    Mit freundlichen Gruessen / Best regards

    Richard Hammerl

      CadSoft Support -- hotline@cadsoft.de

      FAQ: http://www.cadsoft.de/training/faq/

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • autodeskguest
    autodeskguest over 9 years ago in reply to autodeskguest

    Am 12.05.2016 um 14:51 schrieb Joern Paschedag:

    Am 12.05.2016 um 09:15 schrieb Morten Leikvoll:

    Just a comment to 1)

    I'd like to have the option for auto direction on this arrow. Since pin

    directions are defined in the devices, eagle can resolve wether the

    segment is connected to some output net, or only input nets, and choose

    direction according to this.

     

    That would be nice image

     

     

    Hi,

     

    currently there are no concrete plans. It's in the todo list, but

    with low priority. I will bring this up for V8 again.

    - Direction for xref labels

    - xref for a bus

     

     

    However, not everyone is actively using pin directions on their devices

    (the lazy, sloppy and unskilled ones just set them to i/o or pas), so

    maybe there is a need for a manual direction too. The options for arrow

    direction should be:

    -Auto (based on segment pinrefs)

    -in (always pointing toward the end of the wire)

    -out (always pointing away from the end of the wire)

    -bidir (arrow in both directions)

     

    If the direction arrows are done correctly everything is nice.

    However (greetings from orcad) I once had to modify drawings and those

    people gave a damn on correct use of it. I ran into trouble until I

    completely ignored the directions.

    So I'm not  too eager on that, but would be nice to have.

     

     

    With auto, there is also some options for live ERC, like the ability to

    detect and show if the net is missing a driver or double driven by

    multiple outputs.

     

    Finally, I wouldn't mind of the xrefs got split into a new primitive

    called pageconnector, and get an attribute containing ALL the

    references. Also the full list of references should be shown at the

    tooltip on mouseover/hover event.

     

    I don't know if this is practical. Think  of a little project with 15 to

    20 pages and then select "GND"....perhaps it would be better in kind of

    an info line...

     

    It's planned to show the occurences of the net in the info dialog.

     

     

     

    Finally it should be possible to hook it to a bus too.

     

     

    --

    Mit freundlichen Gruessen / Best regards

    Richard Hammerl

      CadSoft Support -- hotline@cadsoft.de

      FAQ: http://www.cadsoft.de/training/faq/

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • autodeskguest
    autodeskguest over 9 years ago in reply to autodeskguest

    Am 12.05.2016 um 14:51 schrieb Joern Paschedag:

    Am 12.05.2016 um 09:15 schrieb Morten Leikvoll:

    Just a comment to 1)

    I'd like to have the option for auto direction on this arrow. Since pin

    directions are defined in the devices, eagle can resolve wether the

    segment is connected to some output net, or only input nets, and choose

    direction according to this.

     

    That would be nice image

     

     

    Hi,

     

    currently there are no concrete plans. It's in the todo list, but

    with low priority. I will bring this up for V8 again.

    - Direction for xref labels

    - xref for a bus

     

     

    However, not everyone is actively using pin directions on their devices

    (the lazy, sloppy and unskilled ones just set them to i/o or pas), so

    maybe there is a need for a manual direction too. The options for arrow

    direction should be:

    -Auto (based on segment pinrefs)

    -in (always pointing toward the end of the wire)

    -out (always pointing away from the end of the wire)

    -bidir (arrow in both directions)

     

    If the direction arrows are done correctly everything is nice.

    However (greetings from orcad) I once had to modify drawings and those

    people gave a damn on correct use of it. I ran into trouble until I

    completely ignored the directions.

    So I'm not  too eager on that, but would be nice to have.

     

     

    With auto, there is also some options for live ERC, like the ability to

    detect and show if the net is missing a driver or double driven by

    multiple outputs.

     

    Finally, I wouldn't mind of the xrefs got split into a new primitive

    called pageconnector, and get an attribute containing ALL the

    references. Also the full list of references should be shown at the

    tooltip on mouseover/hover event.

     

    I don't know if this is practical. Think  of a little project with 15 to

    20 pages and then select "GND"....perhaps it would be better in kind of

    an info line...

     

    It's planned to show the occurences of the net in the info dialog.

     

     

     

    Finally it should be possible to hook it to a bus too.

     

     

    --

    Mit freundlichen Gruessen / Best regards

    Richard Hammerl

      CadSoft Support -- hotline@cadsoft.de

      FAQ: http://www.cadsoft.de/training/faq/

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • autodeskguest
    autodeskguest over 9 years ago in reply to autodeskguest

    2016-05-13 10:33 keltezéssel, Richard Hammerl írta:

    Am 12.05.2016 um 14:51 schrieb Joern Paschedag:

    Am 12.05.2016 um 09:15 schrieb Morten Leikvoll:

    Just a comment to 1)

    I'd like to have the option for auto direction on this arrow. Since pin

    directions are defined in the devices, eagle can resolve wether the

    segment is connected to some output net, or only input nets, and choose

    direction according to this.

     

    That would be nice image

     

     

    Hi,

     

    currently there are no concrete plans. It's in the todo list, but

    with low priority. I will bring this up for V8 again.

    - Direction for xref labels

    - xref for a bus

     

    Hello Richard,

     

    Just for curiosity: do you have any goal date range about the V8?

     

    Thanks!

     

    However, not everyone is actively using pin directions on their devices

    (the lazy, sloppy and unskilled ones just set them to i/o or pas), so

    maybe there is a need for a manual direction too. The options for arrow

    direction should be:

    -Auto (based on segment pinrefs)

    -in (always pointing toward the end of the wire)

    -out (always pointing away from the end of the wire)

    -bidir (arrow in both directions)

     

    If the direction arrows are done correctly everything is nice.

    However (greetings from orcad) I once had to modify drawings and those

    people gave a damn on correct use of it. I ran into trouble until I

    completely ignored the directions.

    So I'm not  too eager on that, but would be nice to have.

     

     

    With auto, there is also some options for live ERC, like the ability to

    detect and show if the net is missing a driver or double driven by

    multiple outputs.

     

    Finally, I wouldn't mind of the xrefs got split into a new primitive

    called pageconnector, and get an attribute containing ALL the

    references. Also the full list of references should be shown at the

    tooltip on mouseover/hover event.

     

    I don't know if this is practical. Think  of a little project with 15 to

    20 pages and then select "GND"....perhaps it would be better in kind of

    an info line...

     

    It's planned to show the occurences of the net in the info dialog.

     

     

     

    Finally it should be possible to hook it to a bus too.

     

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • autodeskguest
    autodeskguest over 9 years ago in reply to autodeskguest

    2016-05-13 10:33 keltezéssel, Richard Hammerl írta:

    Am 12.05.2016 um 14:51 schrieb Joern Paschedag:

    Am 12.05.2016 um 09:15 schrieb Morten Leikvoll:

    Just a comment to 1)

    I'd like to have the option for auto direction on this arrow. Since pin

    directions are defined in the devices, eagle can resolve wether the

    segment is connected to some output net, or only input nets, and choose

    direction according to this.

     

    That would be nice image

     

     

    Hi,

     

    currently there are no concrete plans. It's in the todo list, but

    with low priority. I will bring this up for V8 again.

    - Direction for xref labels

    - xref for a bus

     

    Hello Richard,

     

    Just for curiosity: do you have any goal date range about the V8?

     

    Thanks!

     

    However, not everyone is actively using pin directions on their devices

    (the lazy, sloppy and unskilled ones just set them to i/o or pas), so

    maybe there is a need for a manual direction too. The options for arrow

    direction should be:

    -Auto (based on segment pinrefs)

    -in (always pointing toward the end of the wire)

    -out (always pointing away from the end of the wire)

    -bidir (arrow in both directions)

     

    If the direction arrows are done correctly everything is nice.

    However (greetings from orcad) I once had to modify drawings and those

    people gave a damn on correct use of it. I ran into trouble until I

    completely ignored the directions.

    So I'm not  too eager on that, but would be nice to have.

     

     

    With auto, there is also some options for live ERC, like the ability to

    detect and show if the net is missing a driver or double driven by

    multiple outputs.

     

    Finally, I wouldn't mind of the xrefs got split into a new primitive

    called pageconnector, and get an attribute containing ALL the

    references. Also the full list of references should be shown at the

    tooltip on mouseover/hover event.

     

    I don't know if this is practical. Think  of a little project with 15 to

    20 pages and then select "GND"....perhaps it would be better in kind of

    an info line...

     

    It's planned to show the occurences of the net in the info dialog.

     

     

     

    Finally it should be possible to hook it to a bus too.

     

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • autodeskguest
    autodeskguest over 9 years ago in reply to autodeskguest

    2016-05-13 10:33 keltezéssel, Richard Hammerl írta:

    Am 12.05.2016 um 14:51 schrieb Joern Paschedag:

    Am 12.05.2016 um 09:15 schrieb Morten Leikvoll:

    Just a comment to 1)

    I'd like to have the option for auto direction on this arrow. Since pin

    directions are defined in the devices, eagle can resolve wether the

    segment is connected to some output net, or only input nets, and choose

    direction according to this.

     

    That would be nice image

     

     

    Hi,

     

    currently there are no concrete plans. It's in the todo list, but

    with low priority. I will bring this up for V8 again.

    - Direction for xref labels

    - xref for a bus

     

    Hello Richard,

     

    Just for curiosity: do you have any goal date range about the V8?

     

    Thanks!

     

    However, not everyone is actively using pin directions on their devices

    (the lazy, sloppy and unskilled ones just set them to i/o or pas), so

    maybe there is a need for a manual direction too. The options for arrow

    direction should be:

    -Auto (based on segment pinrefs)

    -in (always pointing toward the end of the wire)

    -out (always pointing away from the end of the wire)

    -bidir (arrow in both directions)

     

    If the direction arrows are done correctly everything is nice.

    However (greetings from orcad) I once had to modify drawings and those

    people gave a damn on correct use of it. I ran into trouble until I

    completely ignored the directions.

    So I'm not  too eager on that, but would be nice to have.

     

     

    With auto, there is also some options for live ERC, like the ability to

    detect and show if the net is missing a driver or double driven by

    multiple outputs.

     

    Finally, I wouldn't mind of the xrefs got split into a new primitive

    called pageconnector, and get an attribute containing ALL the

    references. Also the full list of references should be shown at the

    tooltip on mouseover/hover event.

     

    I don't know if this is practical. Think  of a little project with 15 to

    20 pages and then select "GND"....perhaps it would be better in kind of

    an info line...

     

    It's planned to show the occurences of the net in the info dialog.

     

     

     

    Finally it should be possible to hook it to a bus too.

     

     

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
No Data
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2025 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube