Guriddo » Topic: saveState and loadState

saveState and loadState

Guriddo
saveState and loadState

This topic has 3 replies, 2 voices, and was last updated 6 years, 5 months ago by guriddo.support.

Creator

Topic
April 11, 2018 at 6:10 am #126803

krisreddy
Participant

Hello,

These are great methods – which seems to store all the options of the grid even thought the some of the parameters of the grid are not defined. For example: if beforeProcessing was not defined in the grid – it is stored when save state as null. when loadState is called – it is giving an error “Cannot read property ‘beforeProcessing’ of undefined”

Not sure if this is a bug, but would be helpful to only store what is defined.

Please advise,

Kris

Guriddo Customer
Creator

Topic

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

Author

Replies
April 11, 2018 at 2:48 pm #126804

guriddo.support
Participant

Hello,

Thank you for the recommendation. Unfortunately at the moment we can’t store only the defined parameters for the grid, since they are extended when the grid is created and we do not know which are defined. (maybe it can be done when we made interception from the default and new one, but this need testing)

We can not reproduce this problem. Can you please post a simple test case which demonstrates the problem?

Thank you

Kind Regards,

Will

Guriddo Support Team

April 12, 2018 at 9:10 pm #126806

krisreddy
Participant

Thanks Will.

I was able to use saveState to save it into local storage. Then I used a my custom loadState function to apply to only info I needed.

For example: I only needed to restore colModel, if user changes it by hiding or showing columns and sort order and sort name

What I did is set the use a custom getState function to get state from localStorage and apply colModel,sortname,sortorder before building the grid.

Kris

April 13, 2018 at 10:05 am #126812

guriddo.support
Participant

Hello,

In loadState method there is a event called beforeSetGrid. To this event are passed the saved grid parameters. The event should return the new (modified) parameters, which exactly what you do with your custom function.

Docs are here

Since you point to some bug – can you please post the code which demonstrates the problem.

Kind Regards,

WIll

Guriddo Support Team
Author

Replies