in V6.0.0 manual routing got really hard

On 12/16/2011 12:55 PM, Mitch Solomon wrote:

somethings changed, when i manually route and click on the destination pad, if i dont click dead center now... im left with tiny tiny airwires

5.11 didnt do this... i have messed with alot of settings, nothing seems to help

 

Check your catch factor and select factor settings, by default they

should be 5% and 2% respectively. Perhaps on a MAC this is different or

the OS interprets the values differently it may be worth playing with

them to get everything working nicely. Try 7% and 3% or maybe 8% and 4%.

hth,

Jorge Garcia

Guest wrote:

 

On 12/16/2011 12:55 PM, Mitch Solomon wrote:

somethings changed, when i manually route and click on the destination pad, if i dont click dead center now... im left with tiny tiny airwires

5.11 didnt do this... i have messed with alot of settings, nothing seems to help

 

 

Check your catch factor and select factor settings, by default they

should be 5% and 2% respectively. Perhaps on a MAC this is different or

the OS interprets the values differently it may be worth playing with

them to get everything working nicely. Try 7% and 3% or maybe 8% and 4%.

 

hth,

Jorge Garcia

 

It's not that - you can zoom in all you want, and virtually hover over the exact centre of the pad, and it won't "ping" to let you know it's connected.

It even happens if you route a wire into another wire - if the other wire is on the grid, it doesn't think you've finished, so you have to double-click to stop it carrying on.

Just tried it in 6.0.2 (beta version) - still broken.

Steps to reproduce:

1. Move component with air wires connected to pads
2. Manually route to one of the component's pad from another one

It's easier to reproduce if the component's pads aren't on the grid.

No problem!

http://www.tribbeck.com/misc/Test5_11_0.zip is the URL for this.

It's not an exact match in terms of the original layout, but it behaves exactly the same when loaded into 6.0.0 (can't manually route after rotating Q1), and works correctly on 5.11.0.

btw, I used to run the support team for my company (which is also a software developer), so I know how useful it is to have these kind of files for developers. I'm now one of the developers (I was beforehand - just my project got cancelled, and they needed someone to run support...)

On 12/28/2011 1:37 PM, Jason Tribbeck wrote:

No problem, Jorge.

 

Do you still want a V5 version? (Now I'm at home, I've got time to prepare one as well).

 

The only other issue I've got is a MacOS X one, which I posted in the "Is there a list of open issues?" thread. That one shouldn't be too hard to see and fix But I'll leave that for you to comment on that thread instead of this one (I know you're reading this one, so it's really just a bit of a prompt!)

 

Hi Jason,

If you don't mind prepare a V5 variant and put everything together in

the test.zip file that way the developers have access to everything and

we can make they're jobs as easy as possible.

I'll go look at the other thread.

Thanks again.

Jorge

No problem, Jorge.

Do you still want a V5 version? (Now I'm at home, I've got time to prepare one as well).

The only other issue I've got is a MacOS X one, which I posted in the "Is there a list of open issues?" thread. That one shouldn't be too hard to see and fix But I'll leave that for you to comment on that thread instead of this one (I know you're reading this one, so it's really just a bit of a prompt!)

On 12/28/2011 3:49 AM, Jason Tribbeck wrote:

Hi,

 

Okay - it also happens in the Windows version as well. Unfortunately, I don't have a v5 format file (I'll need to switch the directories back over, and I really should be working at work ), but I've made it available (since I'm not NNTP, I don't have your email address, so it's on my web site).

 

http://www.tribbeck.com/misc/test.zip

 

This is a zip of my Eagle project directory, and contains the schematic and board files. It's a simple LED driver circuit that I've thrown together.

 

This is reproducable using the following command:

 

ROTATE =MR45 Q1

 

Then, try and manually route the signal from SV1 pin 1 to pin 1 of Q1.

 

I'm pretty sure it's never happened on 5.x.

 

Awesome Jason,

Thanks for preparing this, I'll forward this to our developers and

hopefully they can get on it for the next beta.

Thanks again for helping, and I apologize for the delay in getting to

you with the release of V6 it's been very crazy around here.

Best Regards,

Jorge Garcia

Hi,

Okay - it also happens in the Windows version as well. Unfortunately, I don't have a v5 format file (I'll need to switch the directories back over, and I really should be working at work ), but I've made it available (since I'm not NNTP, I don't have your email address, so it's on my web site).

http://www.tribbeck.com/misc/test.zip

This is a zip of my Eagle project directory, and contains the schematic and board files. It's a simple LED driver circuit that I've thrown together.

This is reproducable using the following command:

ROTATE =MR45 Q1

Then, try and manually route the signal from SV1 pin 1 to pin 1 of Q1.

I'm pretty sure it's never happened on 5.x.

Hi,

Okay - it also happens in the Windows version as well. Unfortunately, I don't have a v5 format file (I'll need to switch the directories back over, and I really should be working at work ), but I've made it available (since I'm not NNTP, I don't have your email address, so it's on my web site).

http://www.tribbeck.com/misc/test.zip

This is a zip of my Eagle project directory, and contains the schematic and board files. It's a simple LED driver circuit that I've thrown together.

This is reproducable using the following command:

ROTATE =MR45 Q1

Then, try and manually route the signal from SV1 pin 1 to pin 1 of Q1.

I'm pretty sure it's never happened on 5.x.

No problem!

http://www.tribbeck.com/misc/Test5_11_0.zip is the URL for this.

It's not an exact match in terms of the original layout, but it behaves exactly the same when loaded into 6.0.0 (can't manually route after rotating Q1), and works correctly on 5.11.0.

btw, I used to run the support team for my company (which is also a software developer), so I know how useful it is to have these kind of files for developers. I'm now one of the developers (I was beforehand - just my project got cancelled, and they needed someone to run support...)

On 12/28/2011 1:37 PM, Jason Tribbeck wrote:

No problem, Jorge.

 

Do you still want a V5 version? (Now I'm at home, I've got time to prepare one as well).

 

The only other issue I've got is a MacOS X one, which I posted in the "Is there a list of open issues?" thread. That one shouldn't be too hard to see and fix But I'll leave that for you to comment on that thread instead of this one (I know you're reading this one, so it's really just a bit of a prompt!)

 

Hi Jason,

If you don't mind prepare a V5 variant and put everything together in

the test.zip file that way the developers have access to everything and

we can make they're jobs as easy as possible.

I'll go look at the other thread.

Thanks again.

Jorge

No problem, Jorge.

Do you still want a V5 version? (Now I'm at home, I've got time to prepare one as well).

The only other issue I've got is a MacOS X one, which I posted in the "Is there a list of open issues?" thread. That one shouldn't be too hard to see and fix But I'll leave that for you to comment on that thread instead of this one (I know you're reading this one, so it's really just a bit of a prompt!)

On 12/28/2011 3:49 AM, Jason Tribbeck wrote:

Hi,

 

Okay - it also happens in the Windows version as well. Unfortunately, I don't have a v5 format file (I'll need to switch the directories back over, and I really should be working at work ), but I've made it available (since I'm not NNTP, I don't have your email address, so it's on my web site).

 

http://www.tribbeck.com/misc/test.zip

 

This is a zip of my Eagle project directory, and contains the schematic and board files. It's a simple LED driver circuit that I've thrown together.

 

This is reproducable using the following command:

 

ROTATE =MR45 Q1

 

Then, try and manually route the signal from SV1 pin 1 to pin 1 of Q1.

 

I'm pretty sure it's never happened on 5.x.

 

Awesome Jason,

Thanks for preparing this, I'll forward this to our developers and

hopefully they can get on it for the next beta.

Thanks again for helping, and I apologize for the delay in getting to

you with the release of V6 it's been very crazy around here.

Best Regards,

Jorge Garcia