Author Topic: New Attribute Dialog is missing Apply/OK/Cancel  (Read 237 times)

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 9480
  • Karma: +266/-27
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
New Attribute Dialog is missing Apply/OK/Cancel
« on: June 12, 2019, 09:01:58 pm »
The new (single) attribute dialog does not have an Apply/OK/Cancel button.
Changes made to to an attribute in this dialog cannot be cancelled.
This dialog works differently from any other dialog in EA.

Reported

Geert

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 9480
  • Karma: +266/-27
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: New Attribute Dialog is missing Apply/OK/Cancel
« Reply #1 on: June 14, 2019, 01:46:08 pm »
Reply from Sparx:

Quote
Hello Geert,

Thanks for the email.

The workflow associated with these dialogs was intentionally changed.

If you have any further questions please let us know.

I replied:

Really?
A popup properties dialog that saves instantly goes against every UX best practice, and against every other properties dialog in EA.
I think each of such properties dialogs should behave the same way, either save directly, or save after commit.
Having one behave differently from the others is just confusing the user.

Do you really think that is not a problem?

Geert

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 6853
  • Karma: +143/-104
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: New Attribute Dialog is missing Apply/OK/Cancel
« Reply #2 on: June 14, 2019, 02:00:26 pm »
Reply from Sparx:

Quote
Hello Geert,

Thanks for the email.

The workflow associated with these dialogs was intentionally changed.

If you have any further questions please let us know.

I replied:

Really?
A popup properties dialog that saves instantly goes against every UX best practice, and against every other properties dialog in EA.
I think each of such properties dialogs should behave the same way, either save directly, or save after commit.
Having one behave differently from the others is just confusing the user.

Do you really think that is not a problem?

Geert
I've received similar responses to questions about the UX design recently.

I don't know which users get asked about their proposed UX changes but it sure isn't me (nor from what I see anyone else on the forum).

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!