I am looking at using rad controls to replace a range of existing ( old asp ) controls, and there is a lot of nice stuff, but there is a number of basic gotchas..
It would seem that the datepicker cannot perform basic positioning of its popup window ( If I am wrong please advise how it works)..
It would appear that it simply adds the height to the bottom of the input ( indepenent of weather it can fit on the screen or not!!!)
This cannot be right, all know datepicker I have worked with can perform this basic requirement, and is it is unusable without such a basic funtion...
At a minium there must be at least design time setup ( even though this is pretty easly worked out by the computer), see ShowPopupCorrectPosition ..
Please conform I am not missing something very basic, and that the picker cannot work out how to position its popup, and b) there is no design support for this either..
Thanks
10 Answers, 1 is accepted
0
Hello Ray,
Unfortunately, RadDatePicker does not support screen boundary detection at the moment. We will implement this for some of our next releases (or service packs). In the meantime, you can define a popup position programmatically on the client:
http://demos.telerik.com/aspnet-ajax/calendar/examples/datepicker/clientapi/defaultcs.aspx
Regards,
Dimo
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Unfortunately, RadDatePicker does not support screen boundary detection at the moment. We will implement this for some of our next releases (or service packs). In the meantime, you can define a popup position programmatically on the client:
http://demos.telerik.com/aspnet-ajax/calendar/examples/datepicker/clientapi/defaultcs.aspx
Regards,
Dimo
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Ray
Top achievements
Rank 1
Rank 1
answered on 16 Mar 2009, 07:58 PM
Hello Ray,
Unfortunately, RadDatePicker does not support screen boundary detection at the moment.
>> This is realy unbeleivabe, do you listen to you clients ( see post six months ago on the same issue)..
New releases, no progress!..
The thread on skins is also very worrying trend.. which seems to suggest that you know better than your customers?
We will implement this for some of our next releases (or service packs).
>> See previous thread on this, this is a VERY basic requiremet of any date picker!
In the meantime, you can define a popup position programmatically on the client:
http://demos.telerik.com/aspnet-ajax/calendar/examples/datepicker/clientapi/defaultcs.aspx
>> No you cannot, this is NOT pratical... and does NOT address the issue..
See any datepicker, say peter blum (which I currently use), for an example fo what is required...
But a simple search on google for datepicker will show you what is the very basic requiremets, none of these does not understand this issue..
Very disapointing..
Unfortunately, RadDatePicker does not support screen boundary detection at the moment.
>> This is realy unbeleivabe, do you listen to you clients ( see post six months ago on the same issue)..
New releases, no progress!..
The thread on skins is also very worrying trend.. which seems to suggest that you know better than your customers?
We will implement this for some of our next releases (or service packs).
>> See previous thread on this, this is a VERY basic requiremet of any date picker!
In the meantime, you can define a popup position programmatically on the client:
http://demos.telerik.com/aspnet-ajax/calendar/examples/datepicker/clientapi/defaultcs.aspx
>> No you cannot, this is NOT pratical... and does NOT address the issue..
See any datepicker, say peter blum (which I currently use), for an example fo what is required...
But a simple search on google for datepicker will show you what is the very basic requiremets, none of these does not understand this issue..
Very disapointing..
0
Hello Ray,
I understand you disappointment, unfortunately, this task has been postponed due to other ones with higher priority.
We will implement the feature for Q2 2009.
Kind regards,
Dimo
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
I understand you disappointment, unfortunately, this task has been postponed due to other ones with higher priority.
We will implement the feature for Q2 2009.
Kind regards,
Dimo
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Jon
Top achievements
Rank 1
Rank 1
answered on 24 Apr 2009, 07:53 AM
Hi Dimo,
Is this collision detection still ontrack for the Q2 release? I've just come across the same issue. For the time being I'll leave it so that my users scroll the page to see the inputs and will add some space to the bottom of the form.
Assuming it is in the Q2 release do you know when it will be released as we are in Q2 now....
Cheers,
Jon
Is this collision detection still ontrack for the Q2 release? I've just come across the same issue. For the time being I'll leave it so that my users scroll the page to see the inputs and will add some space to the bottom of the form.
Assuming it is in the Q2 release do you know when it will be released as we are in Q2 now....
Cheers,
Jon
0
Hello Jon,
The screen boundary detection feature for RadDatePicker is scheduled for the Q2 2009 release, expected in the beginning of July. I hope that the time scale for this enhancement is not in conflict with your project finalization tasks.
Note that a public Q2 2009 Beta version will be announced about two weeks before the official release and I encourage you to try it out.
Best regards,
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Jon
Top achievements
Rank 1
Rank 1
answered on 24 Apr 2009, 11:44 AM
Hi Sebastian,
Sounds good to me - also very nice to have a rough timeframe for the launch - thank you.
It will be too late for the initial launch but I may try and adapt the javascript routine in the example to reposition the control when necessary - probably a couple of hours (or less) work. I'll post the solution on this page when done in case it's of use to anyone else.
Regards,
Jon
Sounds good to me - also very nice to have a rough timeframe for the launch - thank you.
It will be too late for the initial launch but I may try and adapt the javascript routine in the example to reposition the control when necessary - probably a couple of hours (or less) work. I'll post the solution on this page when done in case it's of use to anyone else.
Regards,
Jon
0
vbl vbl
Top achievements
Rank 1
Rank 1
answered on 18 May 2009, 05:38 AM
When added this new feature can you also check that it works when scrolling the page.
i.e. same as the issue with color picker, is also happening with the datepicker http://www.telerik.com/community/forums/aspnet-ajax/colorpicker/colorpicker-within-radsplitter-stays-static-on-the-page-when-scrolling.aspx
(me thinks you can reuse some of the code with color picker)
i.e. same as the issue with color picker, is also happening with the datepicker http://www.telerik.com/community/forums/aspnet-ajax/colorpicker/colorpicker-within-radsplitter-stays-static-on-the-page-when-scrolling.aspx
(me thinks you can reuse some of the code with color picker)
0
Hello vbl,
The forum thread that you are referencing, discusses two different issues:
1. Relatively and absolutely positioned elements inside a scrollable container do not move when the container is scrolled. This is caused by an IE bug and the solution is to add a position:relative style to the scrollable container.
2. Popup elements, which are positioned with regard to an element placed inside a scrollable container, do not update their popup position when the container is scrolled. This problem is caused by the fact that the popup elements are placed outside the scrollable container (in the body element), so that they are not hidden by elements belonging to higher stacking contexts. The popup element doesn't know when the container is scrolled, so it can't update its popup position.
Regards,
Dimo
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
The forum thread that you are referencing, discusses two different issues:
1. Relatively and absolutely positioned elements inside a scrollable container do not move when the container is scrolled. This is caused by an IE bug and the solution is to add a position:relative style to the scrollable container.
2. Popup elements, which are positioned with regard to an element placed inside a scrollable container, do not update their popup position when the container is scrolled. This problem is caused by the fact that the popup elements are placed outside the scrollable container (in the body element), so that they are not hidden by elements belonging to higher stacking contexts. The popup element doesn't know when the container is scrolled, so it can't update its popup position.
Regards,
Dimo
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
vbl vbl
Top achievements
Rank 1
Rank 1
answered on 18 May 2009, 11:47 PM
Some more info, using the datepicker popup with the popup div displayed, if I scroll the page the popup div stays it the same place on the screen, and not releative to its textbox. (edit I am testing in FF3) I also have the relative position fix this fixes it for the colorpicker
Other issue is when the datepicker is at the bottom of a scrolling page, when it is opened it is hidden of the bottom and the scoll bar is not extended. Color picker is fine
Note: timepicker also has same issue
Other issue is when the datepicker is at the bottom of a scrolling page, when it is opened it is hidden of the bottom and the scoll bar is not extended. Color picker is fine
Note: timepicker also has same issue
0
Hello,
"using the datepicker popup with the popup div displayed, if I scroll the page the popup div stays it the same place on the screen, and not releative to its textbox"
That's right, this is explained in (2) in my previous post. I am afraid that this behavior will remain the same in future versions as well.
"Other issue is when the datepicker is at the bottom of a scrolling page, when it is opened it is hidden of the bottom and the scoll bar is not extended."
Currently we are working on two features of RadDatePicker - different popup direction, which can be set declaratively, and screen boundary detection.
Kind regards,
Dimo
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
"using the datepicker popup with the popup div displayed, if I scroll the page the popup div stays it the same place on the screen, and not releative to its textbox"
That's right, this is explained in (2) in my previous post. I am afraid that this behavior will remain the same in future versions as well.
"Other issue is when the datepicker is at the bottom of a scrolling page, when it is opened it is hidden of the bottom and the scoll bar is not extended."
Currently we are working on two features of RadDatePicker - different popup direction, which can be set declaratively, and screen boundary detection.
Kind regards,
Dimo
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.