Layers in Standard (Hobbyist) Edition

Am 16.12.2014 um 09:49 schrieb Rob Pearce:

On 16/12/14 01:12, Gary La wrote:

It has no mechanism to get past this. So that's the end of that

schematic, I guess. Very unprofessional. No excuse for this type of

behavior. A pro would've fixed the file with a placeholder or temporary

tag so that the work could be recovered. Or at the very least, prompted

the user to enter a value. Or opened the schematic but deleted the part

associated with the fault. Or about 10 other things. But not this

product -- end of schematic.

 

Your faith in this mystical "pro" astonishes me. I've used Microsoft

tools! And Orcad, and Matlab/Simulink, and all those other very

expensive professional tools. None of them do any better at this than

Eagle - most worse.

 

You can accuse me of temper tantrums all you like - without the

slightest justification, since you were the first to throw one - but it

makes no difference to the fact that the holy grail you seem to expect

from over-priced software does not exist in the real world. In my many

years of using computer software the one thing I have absolutely found

is that

 

     You DON'T get what you pay for

 

You want a program that allows a recovery mechanism for a corrupted file

(which clearly is what you had)? Use one with a plain text format

(Eagle's is now XML, which isn't perfect but...) and/or open source.

Yes, that's right, the most likely programs to survive bad files are the

FREE ones!

 

Bob, Morten and others imho you should stop the discussion.

You are just feeding a troll.

--

Mit freundlichen Grüßen / With best regards

Joern Paschedag

I fixed it myself by digging into the XML file.

The group function and cut-to-clipboard need to be streamlined.

Often clicking on objects with the anticipation that the currently-selected part will be affected by the currently-selected operation often yields no action. For example: move. Clicking on an object and dragging usually fixes the object to the mouse and the move is performed. But very often it only highlights the object.

The library manager needs to be completely rewritten. It's a disaster.

I will agree that most CAD/PCB programs are grossly over-priced. However, when I use the library manager in Eagle, I desperately wish I was using my over-priced tools.

I fixed it myself by digging into the XML file.

The group function and cut-to-clipboard need to be streamlined.

Often clicking on objects with the anticipation that the currently-selected part will be affected by the currently-selected operation often yields no action. For example: move. Clicking on an object and dragging usually fixes the object to the mouse and the move is performed. But very often it only highlights the object.

The library manager needs to be completely rewritten. It's a disaster.

I will agree that most CAD/PCB programs are grossly over-priced. However, when I use the library manager in Eagle, I desperately wish I was using my over-priced tools.