I want to disable dates which are not in between RangeMin and RangeMax from a selectedDates collection in an Infragistics WebMonthCalendar control, I have researched a bit but not found any clue.
Which WebMonthCalendar property should I have use?
In the WebMonthCalendar, you have two properties named MinDate and MaxDate.
They get or set the maximum and minimum date that can be selected in the calendar.
I don't know it they disable the dates outside their values, please check if this could be your answer.
Related
Very simple question (hopefully) but I can't find the answer anywhere. I have two seemingly identical date prompts for optional date ranges. One defaults to today's date. The other defaults to 'earliest' and 'latest'. But I can't for the life of me find the setting that controls this.
(I'm not trying to do anything advanced such as dynamical defaults, using javascript.)
Please help. Thanks.
A single-select date prompt with the Required property set to 'No' and the Range property set to 'Yes' will show the Earliest and Latest radio buttons and have them selected as default. When the Required property is set to 'Yes' the date prompts default to the current date. Thus, your two date prompts likely have different settings for the Required property.
I'd like to use the http://angular-ui.github.io/bootstrap/#/datepicker.
Also, I have e.g. a the Events list for, let's say - 12th January
Is it possible to change e.g. the color of that day in the datepicker that I can see that for that day some events exist ?
the reason is, I'd like to give the opportunity for users to be aware whose days contains any Events
I've found that plugin https://github.com/eternicode/bootstrap-datepicker (in the demo, set the 'multidate' textbox value to true).
Moreover, that plugin offers the method to select many dates.
That's exactly I was looking for
I Want a flex date field with particular selectable range only.
I could there are similar properties of mx:DateField to restrict the selectable date range. that are
<mx:DateField disabledRanges="{[{rangeEnd: new Date()}]}"/>
and
<mx:DateField selectableRange="{{rangeStart : new Date()}}" y="100"/>
so i would like to know what is the difference between above two properties and in which case have to use disabledRanges and selectableRange.
disabledRanges allows you to define multiple date ranges to exclude from being selected.[1]
selectableRange allows you to define a single date range to include for selection.[2]
The difference is small but powerful, the ability to define multiple exclusions allows much more customisation.
Imagine you wanted to only allow someone to pick a date in this month, that easy with selectableRange, but imagine you also wanted to exclude all weekends and national holidays? You can't do that with one inclusive date range, you need multiple exclusions.
This properties are opposite. With disabledRanges you could disable some date (dates) from choosing (and other dates will be available to user) and with selectableRange you could set date (dates) that only available (and other dates will be disabled for user).
disabledRanges
selectableRange
I'm trying to work with the ASP calendar control and (for starters) highlight the specific days on the calendar that matches DueDate in the 'task' table. I know how to highlight a cell using the DayRender event, but how do I do this in accordance to the database table?
Would then also like to be able to click on the highlighted cell and see details of the task associated to that date in some sort of box next to the calendar.
Any pointers on how I can solve this?
Pseudo-code:
Determine your desired date range (probably a certain month)
Read all the tasks that have due dates within that date range (probably need Name and DueDate at least)
In your DayRender handler you check if current day's date exists in the loaded tasks's due dates, if it does, highlight it with the color of your choice
In you SelectionChanged handler you obtain the selected day's date, and look through the loaded list of tasks for any tasks that have that date as their due date, and populate whatever box with those tasks.
I am trying do one of the following in the "Create Event" form in Plone 4, when creating events which happened in the past:
i. Set the default start/end dates in the "Start Date" and "End Date" drop-downs to a larger range of values (I cannot create events before 2001 or after 2016).
OR
ii. Allow users to input start/end dates for events as text (rather than select from a drop-down).
I can't seem to find what is controlling this form anywhere... after hours of googling!
The start and end fields are standard Archetypes DateTimeField fields, using the default CalendarWidget widgets.
The CalendarWidget reuses some fairly old and crufty calendar macros from Plone, and these read the range of selectable years from the site properties. You can change these in the ZMI, find the portal_properties tool, then the site_properties property sheet within that. The two properties to look for are:
calendar_starting_year
The starting year to show in the calendar widget. Default is 2001.
calendar_future_years_available
The number of future years, after the current year, to show in the calendar widget. Default is empty, and the widget then falls back to 5 years.
Also see the site properties documentation; you can also use a GenericSetup profile to set these.
These values apply to all usage of the calendar macros. You can also set this for just the event type, by setting the starting_year, ending_year and/or future_years properties on the CalendarWidget for the startDate and endDate fields. If you set an ending_year the future_years property is ignored.
Monkey-patch style altering of the event schema:
from Products.Archetypes.content import event
ATEventSchema['startDate'].widget.starting_year = 1999
ATEventSchema['startDate'].widget.ending_year = 2020
ATEventSchema['endDate'].widget.starting_year = 1999
ATEventSchema['endDate'].widget.ending_year = 2020
If the starting_year and ending_year are not defined on the definition level of the calendarwidget (inside the definition of the ATEvent schema implementation) then some assumptions about the year range is made inside
Products/CMFPlone/skins/plone_scripts/date_components_support.py
Modify the related code inside the date_components_support.py script.