Ext.ux.DateTimeField - DateTimePicker for ext4, also DateTimeMenu, TimePickerField

[wzl002]

I had update the thread and put the upgrade version for ext-4.1.0.

All the bugs in replays had be fixed, I guess.


Thanks again and welcome improve replay.

[immobilia]

Thank you for your prompt patch. Now is working fine with ext-4.1.0

[pkli]

Hi,

Great work ! Thanks.

I'm using it in a grid cell editor but there is a bug when any time value (H,i, s) is set to "00"

Here is my js code for the grid column :

xtype:"datecolumn"
,format:"d/m/Y H:i"
,editor:{xtype:"datetimefield",allowBlank:false,altFormats:"d/m/Y|d/m/Y H:i|d/m/Y H:i|Y-m-d H:i|Y-m-d H:i"}

but as you can see with attachement, 00 values give a decimal numberfield ...

Phil

MAJ : sorry, in fact ANY time value is set as "allowdecimal" numberfield ...
even 10 is set as 10,00

I'm using EXT 4.1 gpl.

MAJ 2 : with 4.1 ... using this plugin create a bug when using standard datefield and timefield.
As soon as you attach this plugin JS files to page, using standard datefield :

ext-all-debug.js:104399Uncaught TypeError: Object [object Object] has no method 'getSelectionModel'


Regards

[wzl002]

Hi,

Great work ! Thanks.

I'm using it in a grid cell editor but there is a bug when any time value (H,i, s) is set to "00"

Here is my js code for the grid column :

xtype:"datecolumn"
,format:"d/m/Y H:i"
,editor:{xtype:"datetimefield",allowBlank:false,altFormats:"d/m/Y|d/m/Y H:i|d/m/Y H:i|Y-m-d H:i|Y-m-d H:i"}

but as you can see with attachement, 00 values give a decimal numberfield ...

Phil

MAJ : sorry, in fact ANY time value is set as "allowdecimal" numberfield ...
even 10 is set as 10,00

I'm using EXT 4.1 gpl.

MAJ 2 : with 4.1 ... using this plugin create a bug when using standard datefield and timefield.
As soon as you attach this plugin JS files to page, using standard datefield :

ext-all-debug.js:104399Uncaught TypeError: Object [object Object] has no method 'getSelectionModel'


Regards

Can you provide your case code please?
I think the property 'altFormats' will not work as expect and the format for time part is 'H:i' and unchangeable, any format set for this part would not work.

[EmCy90]

I started to move my app to 4.1 and after i switch to this version of the ux i noticed that in dateTimeField when you open it it's current value is no longer marked in blue so i took a look. In the setValue method of the DateTimeField the value that is passed to the update method is not clear from it's time part and that caused the trouble.

 setValue: function(value) {
		  this.value = value;
		  this.changeTimeFiledValue(value);
		  return this.update( Ext.Date.clearTime( this.value, true ) );
	  }

[linyajun]

in IE this will show with1.png,can you help me ?(???????

[wzl002]

Thank you very much, I will take a look at that.

[wzl002]

in IE this will show with1.png,can you help me ?(???????

Can you provie your case code and evn infomation like IE version,os and so on

[another_i]

MAJ 2 : with 4.1 ... using this plugin create a bug when using standard datefield and timefield.
As soon as you attach this plugin JS files to page, using standard datefield :

ext-all-debug.js:104399Uncaught TypeError: Object [object Object] has no method 'getSelectionModel'

This trouble is there because .../ux/form/TimePickerField.js uses "widget.timepicker" as alias.

Ext.define('Ext.ux.form.TimePickerField', {
    extend: 'Ext.form.field.Base',
    alias: 'widget.timepicker', // <----- here
    ...
});

Same alias is used in the standart Ext JS timepicker (for the standart timefield). And so an UX's alias overrides the standart one. But this UX don't uses this alias in code as { xtype: "timepicker", ... } or Ext.widget("timepicker", { ... }). So for solve this trouble you should just change in .../ux/form/TimePickerField.js value for alias, for example on "widget.timepickerfield" (it's works good for me):

Ext.define('Ext.ux.form.TimePickerField', {
    extend: 'Ext.form.field.Base',
    alias: 'widget.timepickerfield',
    ...
});

I hope this will be helpful for you.

[felipe.duarte]

Thanks another_i !

I was getting error and now it's gone.

Works perfects in my grid!!

Regards,