Guriddo » Topic: Some usability suggestions

Some usability suggestions

Guriddo
Some usability suggestions

This topic has 3 replies, 2 voices, and was last updated 9 years ago by tony.

Creator

Topic
October 11, 2015 at 5:14 am #124444
krisreddy
Participant
Hello,

jqGrid is one of the best grid components out there that is easy to use and very flexible. In real world where efficiency and productivity matters, users always get frustrated with simple things.
1. When using cell edit, user makes a change and then user either has to press enter or click out of a cell to save/submit data. Is there way to save the data as soon as user makes a change.
2. Excel like data entry – when user clicks in editable cell whether using celledit or inline edit, is it possible to move to the next editable cell when user presses enter or tab.
3. When using celledit, if there is validation error or server response is false on afterSubmitCell, is there a way to position error message next to cell and when user clicks ok – focus the cursor back into cell and keep it in edit mode.
Thanks for listening.

Kris
Creator

Topic

Viewing 3 replies - 1 through 3 (of 3 total)

Author

Replies
October 12, 2015 at 12:09 pm #124445
tony
Keymaster
Hello Kris,

Thank you for your recommendations and good words.

Now to the questions.
1. Actually the program (Guriddo jqGrid) need to know when the user finish with update in order to perform the action of saving. This usually is marked with enter key. If you tell us another way how to do this we will be glad to implement it. Actually maybe is a good idea to have a possibility to define a custom saved key, but this is the same as using enter or tab key.
2. In cell edit when the user press enter the data is saved and the user stay on that cell. When a tab key (or shift tab) is pressed tha data is saved and the user is moved to the next editable cell. You can check this.
3. Yes this is possible. There is a undocumented grid property restoreCellonFail. The default is true. If you set it to false you will get the described behavior. The only exception on this is that the dialog is not positioned next to the cell when a afterSubmitCell event is used, but this can be easy implemented as on user validation.
Kind Regards,
- This reply was modified 9 years ago by tony.
October 13, 2015 at 1:36 am #124451
krisreddy
Participant
Thank you for your response Tony!
1. Well, one thing I can think of using the onchange event after the cell edit before the enter is pressed.
2. Sorry i did not know – tab key works. What would make it even better is iof the tab continued to next row editable cell. right now if stops at the last cell. Also, when enter key is pressed after cell edit, it would awesome if it move the cell below
3. yes, restoreCellonFail works for validations but the focus is lost when you click ok, it does not return to the cell. I don;t know if this is good solution – what if focus is still on cell on error and message shows next to cell and disappears after few seconds. so user does not have to click ok. Could you please point me right direction on how to position the dialog next to cell on user validation.
Thanks for your efforts.

Kris
October 13, 2015 at 4:42 pm #124452
tony
Keymaster
Hello,

Thanks for the feedback.

1. The onchange event occur when we live the input field. It is similar of pressing tab. I think that the user should know when to save filed (enter or tab) rather than to save it in all cases (which occur in onchange event).

2. Good idea, will try to implement it.

3. We will think on this too. It have sense. You can download the latest from GitHub to test the position next to the cell on validation.

Kind Regards,
- This reply was modified 9 years ago by tony.
Author

Replies