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
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
Am 12.01.2012 15:22, schrieb Jason Tribbeck:
I've replicated this on 6.0.0 Mac OS, and Windows XP SP3, and 6.0.2 on Mac OS.
Because this is a fairly UI independant operation, I would imagine it's across all operating systems (so I'm not surprised to see it in Linux).
The video should show that it's Mac OS that I had originally found it on, but I'm sure if Jorge wanted to know what platforms it was failing on, he would've asked
It doesn't happen all the time, and it did take a while to come up with an example that is guaranteed to fail. It normally occurs when you're being complacent and not expecting it to happen.
As I wrote it was meant in general. (And not for this special case
only). Sure cadsoft asks about details but then they have to wait for
the answer which can take long wasted time. Is it really so difficuilt
to mention the os? I'm also looking for a fast solution on the v6 trouble.
--
Mit freundlichen Grüßen / With best regards
Joern Paschedag
I've replicated this on 6.0.0 Mac OS, and Windows XP SP3, and 6.0.2 on Mac OS.
Because this is a fairly UI independant operation, I would imagine it's across all operating systems (so I'm not surprised to see it in Linux).
The video should show that it's Mac OS that I had originally found it on, but I'm sure if Jorge wanted to know what platforms it was failing on, he would've asked 
It doesn't happen all the time, and it did take a while to come up with an example that is guaranteed to fail. It normally occurs when you're being complacent and not expecting it to happen.
On 12/01/2012 13:36, Joern Paschedag wrote:
Am 16.12.2011 18:55, schrieb Mitch Solomon:
>> 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
>>
>
Gentlemen, so far I have followed all this postings and noticed that
there is is very little information about what machine and operating
system you are using.
I think to mention this would be a great help for cadsoft in eliminating
these errors.
I don't have this error on my windows xp sp3.
Using the files linked-to in this thread I can reproduce the fault under
Eagle 6.0.0 and Eagle 6.0.2 in Windows 7 x64.
I was also seeing this leftover airwires problem on Linux x64 (but with
a different (production!) board) using 6.0.0.
The exchange of messages in this thread, between Jorge Garcia and Jason
Tribbeck, suggests that the developers have all they need to be able to
reproduce this.
Hopefully 6.1 will nail it. Hopefully soon!
Andrew
0xADF
Am 16.12.2011 18:55, schrieb Mitch Solomon:
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
Gentlemen, so far I have followed all this postings and noticed that
there is is very little information about what machine and operating
system you are using.
I think to mention this would be a great help for cadsoft in eliminating
these errors.
I don't have this error on my windows xp sp3.
--
Mit freundlichen Grüßen / With best regards
Joern Paschedag
On 11/01/2012 23:00, Przemyslaw Zur wrote:
Ok, so are there only few people notising this problem?
I'm also seeing this bug with EAGLE 6.0.2.
Having used v6.0.0 to manually route a small board recently I can
confirm that this problem is highly annoying.
Andrew
0xADF
Ok, so are there only few people notising this problem? In my company we've bought 5 new licenses for eagle v6 just before it went out. Now im wondering if that was a good idea. We could have bought a floting licensenses of full featured altium for that price... I like eagle but how can you make a product worse with the new release?
Sorry for another post but I forgot to mention my system: Windows XP SP3.
--
Web access to CadSoft support forums at www.eaglecentral.ca. Where the CadSoft EAGLE community meets.
This doesn't limit to snapping to pads but into "stubs" too. If I have a
track that connects pin A to pin B and I ripup a part of that wire, and
then start to draw net from pad A into the stub, eagle doesn't snap to the
stub. It took several ratsnest commands to get eagle to snap into the stub
rather than into grid. I.E. for some reason eagle wants to snap into grid
and not that stub cap that's not on the grid. In 5.11 this was never an
issue. In 6.0.0 random ratsnest commands seem to fix this momentarily.
--
Web access to CadSoft support forums at www.eaglecentral.ca. Where the CadSoft EAGLE community meets.
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