Same page xref

Thanks. It's nice to get this ack from the Cadsoft team. The ack/nack

reply is a great roundoff to every suggestion posts.

 

I've seen a few other suggestions that doesnt get ack'ed or nack'ed and

I have to assume you gave up following the thread on those (I can think

of several reasons why). For the cases I find important, I'd like to

keep on nagging you until you do reply either ack/nack, but so far I

haven't. How do you suggest we follow up on those?

Hi Guys,

Morten has the right idea. The devs do follow these forums, however

having an extra person commit something to paper gives it more weight.

So the way I try to handle these things, is that if I see a request that

a lot of people have or one that simply makes sense I will as a matter

of course file an enhancement request.

It's the most I can do to give a suggestion more attention. If there's

something you really want to see in EAGLE keep nagging and encourage

others to nag about the same thing ;). A request that is made a single

individual without others to back them up isn't going to be seen with as

much priority as one that a lot of people have voiced.

hth,

Jorge Garcia

On 05.02.2016 18:04, Jorge Garcia wrote:

Hi Guys,

 

I have submitted the enhancement request.

 

Let's see what happens.

Thanks. It's nice to get this ack from the Cadsoft team. The ack/nack

reply is a great roundoff to every suggestion posts.

I've seen a few other suggestions that doesnt get ack'ed or nack'ed and

I have to assume you gave up following the thread on those (I can think

of several reasons why). For the cases I find important, I'd like to

keep on nagging you until you do reply either ack/nack, but so far I

haven't. How do you suggest we follow up on those?

Jorge Garcia wrote on Fri, 05 February 2016 17:04

Hi Guys,

 

I have submitted the enhancement request.

 

Let's see what happens.

 

Best Regards,

Jorge Garcia

Isn't that what this suggest forum is supposed to be?  The implication of

having such a forum as this is that the developers and product managers are

watching for what customers are saying in order to know what problems to

fix.

James.

--

James Morrison  ~~~  Stratford Digital

Order your EAGLE license from Stratford Digital at

http://www.eaglelicenses.com

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

Hi Guys,

I have submitted the enhancement request.

Let's see what happens.

Best Regards,

Jorge Garcia

On 02/05/2016 03:28 AM, Joern Paschedag wrote:

Am 05.02.2016 um 09:21 schrieb Morten Leikvoll:

Now (7.5.0), its difficult to see if a xref is unconnected or connected

somewhere on the same page.

 

A normal XREF looks like "NETNAME/PAGE.XY". If the net is not present

elsewhere, it will only look like "NETNAME". The same happens if there

are other separated instances of the net on the same page. This

generates some difficulties when reading schematics. Yes it will be

picked up in ERC, but on a print, thats not an option. Visual search of

other present instances on a large print is not very reliable.

 

I suggest that xref what has net connections on the same page keep their

location but skip the same page reference. It could look like

"NETNAME/XY".

 

It would also look a lot better if all xrefs pointed to the page where

the net is connected to an output/power pin direction (if present), so

that the source of the signal can easily be located.

 

Count me in twice )

 

Eagle devs, Jorge,

Count all my licensed seats in as well.

    - Chuck

On 05.02.2016 13:33, James Morrison wrote:

Me too.  In fact, I mentioned this and my reasoning back in 2011!

 

http://www.eaglecentral.ca/index.php/m/140238/3cf92059246dc2169fb27e9111ace4a6/?srch=xref#msg_140238

 

James.

 

Spot on I guess cadsoft needs to be reminded now and then. I bet it

vanished from the todo list, together with other quick fixes

Joern Paschedag wrote on Fri, 05 February 2016 08:28

Am 05.02.2016 um 09:21 schrieb Morten Leikvoll:

Now (7.5.0), its difficult to see if a xref is unconnected or

connected

somewhere on the same page.

 

A normal XREF looks like "NETNAME/PAGE.XY". If the net is not

present

elsewhere, it will only look like "NETNAME". The same happens if

there

are other separated instances of the net on the same page. This

generates some difficulties when reading schematics. Yes it will

be

picked up in ERC, but on a print, thats not an option. Visual

search of

other present instances on a large print is not very reliable.

 

I suggest that xref what has net connections on the same page keep

their

location but skip the same page reference. It could look like

"NETNAME/XY".

 

It would also look a lot better if all xrefs pointed to the page

where

the net is connected to an output/power pin direction (if

present), so

that the source of the signal can easily be located.

 

Count me in twice )

Me too.  In fact, I mentioned this and my reasoning back in 2011!

http://www.eaglecentral.ca/index.php/m/140238/3cf92059246dc2169fb27e9111ace4a6/?srch=xref#msg_140238

James.

--

James Morrison  ~~~  Stratford Digital

Order your EAGLE license from Stratford Digital at

http://www.eaglelicenses.com

--

Web access to CadSoft support forums at www.eaglecentral.ca.  Where the CadSoft EAGLE community meets.

Count me in twice )

Me too!

Markus

Am 05.02.2016 um 09:21 schrieb Morten Leikvoll:

Now (7.5.0), its difficult to see if a xref is unconnected or connected

somewhere on the same page.

 

A normal XREF looks like "NETNAME/PAGE.XY". If the net is not present

elsewhere, it will only look like "NETNAME". The same happens if there

are other separated instances of the net on the same page. This

generates some difficulties when reading schematics. Yes it will be

picked up in ERC, but on a print, thats not an option. Visual search of

other present instances on a large print is not very reliable.

 

I suggest that xref what has net connections on the same page keep their

location but skip the same page reference. It could look like "NETNAME/XY".

 

It would also look a lot better if all xrefs pointed to the page where

the net is connected to an output/power pin direction (if present), so

that the source of the signal can easily be located.

Count me in twice )

--

Mit freundlichen Grüßen / With best regards

Joern Paschedag