Version 7.3 fixed absolutely nothing?

Am 30.06.2015 um 22:55 schrieb Paul Badger:

It was my impression (from a CadSoft USA rep I believe) that the

infuriating and pointless error message

"Net name 'Foo' already exists,

please use the name command to combine nets"

 

had been killed, but it's still there. I upgraded my OS to be able to

use 7.3 and got ...    NADA

 

If you don't count  the library browser.  How damn hard is it to set

whatever property is being set in the Name dialog from the Properties

dialog, or to just pop open the name dialog with the new name already

filled in?

 

Eagle continues to be the dumbest, most infuriating GUI I use on a

regular basis, but the most infuriating part is that fully half of what

sucks in the interface, is trivially easy to fix.

 

Paul

 

--

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

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

 

Attachments:

Screen Shot 2015-06-30 at 4.42.29 PM.png

 

Reading your post I do not think that you are interested in an

explanation why EAGLE asks you in this situation to use the NAME

command.....

Anyway I will forward your email to our development team and wait

for a solution in a future release.

--

Mit freundlichen Gruessen / Best regards

Richard Hammerl

  CadSoft Support -- hotline@cadsoft.de

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

Am 30.06.2015 um 22:55 schrieb Paul Badger:

It was my impression (from a CadSoft USA rep I believe) that the

infuriating and pointless error message

"Net name 'Foo' already exists,

please use the name command to combine nets"

 

had been killed, but it's still there. I upgraded my OS to be able to

use 7.3 and got ...    NADA

 

If you don't count  the library browser.  How damn hard is it to set

whatever property is being set in the Name dialog from the Properties

dialog, or to just pop open the name dialog with the new name already

filled in?

 

Eagle continues to be the dumbest, most infuriating GUI I use on a

regular basis, but the most infuriating part is that fully half of what

sucks in the interface, is trivially easy to fix.

 

Paul

 

--

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

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

 

Attachments:

Screen Shot 2015-06-30 at 4.42.29 PM.png

 

Reading your post I do not think that you are interested in an

explanation why EAGLE asks you in this situation to use the NAME

command.....

Anyway I will forward your email to our development team and wait

for a solution in a future release.

--

Mit freundlichen Gruessen / Best regards

Richard Hammerl

  CadSoft Support -- hotline@cadsoft.de

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

Reading your post I do not think that you are interested in an

explanation why EAGLE asks you in this situation to use the NAME

command.....

On the contrary, I am extremely interested.

So let's see, the Properties dialog sets a certain amount of properties (but far from all unfortunately).

The name dialog sets some properties.

For the Properties dialog to set the name property, would require:

Maybe another subdialog that would ask about renaming "this segment or all the segments on the page".

Would that be the end of the world, opening another dialog that the user would have to check off?

Or there could be space for the messages that would appear if the user were changing an existing signal. etc etc etc

Then a decision would have to be made whether to close the properties dialog - or just leave it open. (Leave it open obviously)

The information would have to be put in a buffer in case the user cancelled, so it could be undone.

(Although you don't worry about this in the Layers dialog - If the user checks "apply", changes don't revert on cancel.)

Is this stuff that hard?

While I'm putting in requests...

Why doesn't the text tool just open the properties dialog when you click on the tool, so I could set size, layer in one go?

That's an absolutely trivial change to make, you just call the properties dialog instead of the (mostly useless text dialog box).

    Yes, you have in initialize a text object and put it in a buffer so the user can still cancel. Tools need to clean up after themselves.

Why can't I select a whole group of items and open the property dialog, changing all of the items at once.

     For properties that vary from part to part - the field should be grayed out. Yeah it requires work, but what about the users time?

Maybe the "reverse click paradigm" makes this stuff a bit more tricky to code - another excellent reason to throw it overboard.

This might be the case why the Undo buffer works in such a crazy way - that is absolutely counter-intuitive to either Mac or Windows users.

There may be software that is this awkward somewhere, but I don't come across it in all the things I do with:

Graphics packages (see Inkscape - not up to Adobe standards but very useable), Photoshop etc, etc

CAD packages - AutoCAD etc

Text, Word processors, Excel etc etc

Paul