Ext.ux.DatePickerPlus: MultiMonth, MultiSelection, WeekNumbers, Custom CSS Days,...

[wm003]

There is a typo in DateFieldPlus, just search for "showWeekNumer", with this fixed the window shows the week number as default.

Thx for this nice extension!

Thanks for reporting this. I'll check out the issue from pcsernyik and will post a corrected version the next minutes.

[Nohcs777]

I just picked up this extention and trying to integrate it into my code. Please excuse my ignorance if I have some how missed it, but it appears that




Ext.ux.form.DateFieldPlus does not support multiSelection. ie. taken from the Ext.ux.form.DateFieldPlus code:

Ext.apply( 
this.menu.picker, {
minDate : this.minValue,
maxDate : this.maxValue,
...
multiSelectByCTRL: this.multiSelectByCTRL, 
fillupRows: this.fillupRows,
multiSelection: false,
...
});

Is this correct? I suppose this would make sense given the field value can only hold a single date?

[wm003]

Hello,
First, the datepickerplus is a very excellent work!
But i have a little problem:

I put the datepickerplus in the second tab of a tabpanel.
When the first tab is active tab (config: activeTab: 0) the month selector doesn't work properly.
If activeTab:1 (this tab contains the datepicker), the month selector is perfect.

What may cause the problem?

Sorry, but i can't reproduce the problem with this code. The monthpicker works fine, no matter what value activeTab has....Do you use Ext 2.0.2?

[wm003]

Please excuse my ignorance if I have some how missed it, but it appears that Ext.ux.form.DateFieldPlus does not support multiSelection. ie. taken from the Ext.ux.form.DateFieldPlus code:

[Is this correct? I suppose this would make sense given the field value can only hold a single date?

Yes, this is correct. DateFieldPlus can only hold a single date, thus the multiSelection config option is always set to false. I have a DateList Item on my roadmap for future development.
In the meantime use Datemenu which supports multiSelection.

[Nohcs777]

Unfortunately my client prefers to see (and potentially manipulate the trigger Field) after multiselection so it seems I may need to extend the Ext.ux.form.DateFieldPlus. I am still looking over the code, but what I was thinking was to just augment this type to populate a comma (or configurable delimiter) list of the values found in Ext.ux.DatePickerPlus.menu.picker.selectedDates[] and potentially override Ext.ux.DatePickerPlus.setValue() & Ext.ux.DatePickerPlus.getValue(). I would also have to modify the behavior of the menuItem to not close on click as well. Would this not be (temporarily) sufficient?

Additionally, it might make sense to update your demo page. In the description for "DateFieldPlus 1" is accurately describes mutiselect:false however "DateFieldPlus 2" ommits from its comment about multiselect all together. It seems a bit misleading to me if multiselect is always set to false. Am I missing a more complete description of this somewhere in the release notes or something?

[wm003]

Unfortunately my client prefers to see (and potentially manipulate the trigger Field) after multiselection so it seems I may need to extend the Ext.ux.form.DateFieldPlus. I am still looking over the code, but what I was thinking was to just augment this type to populate a comma (or configurable delimiter) list of the values found in Ext.ux.DatePickerPlus.menu.picker.selectedDates[] and potentially override Ext.ux.DatePickerPlus.setValue() & Ext.ux.DatePickerPlus.getValue(). I would also have to modify the behavior of the menuItem to not close on click as well. Would this not be (temporarily) sufficient?

The main problem i see is the Dateparsing, as you could manually enter anything in the datefield (if not set to readonly)...The idea with a delimiter sounds quite easy to realize, but the value(s) need to get passed by the hidden format field also. i'll take that into my roadmap for 1.1.

Additionally, it might make sense to update your demo page. In the description for "DateFieldPlus 1" is accurately describes mutiselect:false however "DateFieldPlus 2" ommits it a comment about multiselect all together. It seems a bit misleading to me if multiselect is always set to false. I am missing this fact say somewhere in the release notes or something?

i choosed to set multiSelection default to false, so it just act like the original datepicker (if anybody upgrades from original datepicker, their apps should act like always then)

I agree with the release_notes...i copied them from this forum now (more clear and its stated that multiSelection is false by default)

[Nohcs777]

Yea. I think I am going to stay away from date parsing at this point and make the field readOnly to avoid this senario for the time being. My client also would like some TextMasking in that senario anyway and that could be relately difficult to accomplish as well.

After making the changes, would you like me to post the changes to this forum?

[wm003]

After making the changes, would you like me to post the changes to this forum?

Yes,please! That would be very interesting in how you accomplished it

[pcsernyik]

Sorry, but i can't reproduce the problem with this code. The monthpicker works fine, no matter what value activeTab has....Do you use Ext 2.0.2?

Yes, I do that.
Please, look at my example here: http://www.ats.hu/test/

[wm003]

Yes, I do that.
Please, look at my example here: http://www.ats.hu/test/

Here is the problem:

                deferredRender: false, 

Delete this line and it works