>From a useablity point of view, this is really confusing for the user.
The user *thinks* they can delete a record because they see the 'Delete'
button, or thinks that should be able to edit a record because they see
the 'Edit' button. This is causing a number of complaints from users -
most other systems do not work like this.
I understand your point about the extra check that will need to be done
when loading the view, but it makes the system look more amateurish. At
least, can developers be provided with a method to be able to remove any
of the 'New', 'Edit', 'Duplicate' or 'Delete' buttons via a condition in
the XML? That would allow developers to make the forms much more
intuitive, which affecting performance.
For example, allowing developers to be able to hide a button based on a
domain condition (like [('state','!=','draft')]) would be a a workable
solution.
--
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/389767
Title:
Buttons seen disabled in GTK are enabled in Web Client
Status in OpenERP Web Client:
Won't Fix
Bug description:
Unlike the GTK client, where buttons are disabled if the user has no
access rights... the web client shows the button.. on clicking the
same page is refreshed and the action of the button is NOT performed.
It would be nice to have the button disabled in web client also.
Guess this should go to wish list!
_______________________________________________
Mailing list: https://launchpad.net/~c2c-oerpscenario
Post to : c2c-oerpscenario@lists.launchpad.net
Unsubscribe : https://launchpad.net/~c2c-oerpscenario
More help : https://help.launchpad.net/ListHelp
