Hello,

Actually you can use the

setDatepicker PHP method – see demos.

Kind Regards,

Will

Hello,

Thank you for the feedback

Regards,

Will

Hello,
 
Thank you for the test case.
 
1. Yes the autcomplete fire on blur. Currently this is the default behaviour.
We use the autocomplete change event . Normally ww should use the select event, but as I say in my previous post it causes problems in some modules.
 
We will change the code so that you can select which event to use change or select – but this will be maybe in the next release. Alternatively you you can use your own dataInit fiunction for that field where the autocomplete use select event.
 
 
2. It seems you have not look at the demo carefully. Use the datepicker option showOn : focus in dataInit function
 

3. We need to lock the full source code related to this field.
(It seems you have bind some on change events )
 

Kind Regards,
Will

Hello,

1.Yes this is true and is caused by autocomplet plugin itself and some problem in search dialog. In order to make your custom autocomplete you may pickup your own using dataInit event.

2. Not sure that I understand the question. Did you mean that if the date is the first column the datepicker does not popup. Can you please demostarte the problem. You may want to look here

3. Sorry I do not understand the problem. Casn you please make a simple demo with description step by step.

Kind Regards,

Will

Hello,
 
Unfortunately we do not support such feature. I see two possible solutions of the problem.
 
1. I possible define additional incremental/serial field which should be used as primary key
 
2. Disable automatic add/edit and use setAfterCrudAction as demonstrated here
 

Kind Regards,
Will

Hell,

The problem is that you query a cell which is ExpandColumn. Any other cell will give you the right content.

This is a bug and we have fixed it here

You can download the latest build and test it.

Kind Regards

Will

Look at your serializeData functions.

Hello,

Without formatter select the post in grid is what you post to the server.

From one side you return the text for the select in grid, but you post the value. Having formatter select will solve your problem.

The link you mentioned is before 3 years and the change is caused by other important bugs of posting and comparing data.

Another solution what we can do for you is to define a new event similar to afterSubmit where you can change the posted values to the grid (not to the server), but I think with formatter select is a more elegant solution.
More over in buildSelect function you have a possibility to update the values for the select in colModel.

Kind Regards,
Will

• This reply was modified 9 years, 9 months ago by guriddo.support.