This question is locked. New answers and comments are not allowed.
Look at the sample code
https://skydrive.live.com/redir.aspx?cid=17feeb61afe2dbeb&resid=17FEEB61AFE2DBEB!14873&parid=17FEEB61AFE2DBEB!14837&authkey=!ALUjO9J6Zjtu6_0
and video demonstrating problem
https://skydrive.live.com/redir.aspx?cid=17feeb61afe2dbeb&resid=17FEEB61AFE2DBEB!14874&parid=17FEEB61AFE2DBEB!14837&authkey=!ALDxgc2ymsfJHkA
Code is simple, but it doesn' work in browser with SLV5 x64. (may be in another frameworks too..)
Detailed investigation showed that if MaskedTextInput defined with property TextMode locally (not via resources) this exception is not thrown
https://skydrive.live.com/redir.aspx?cid=17feeb61afe2dbeb&resid=17FEEB61AFE2DBEB!14873&parid=17FEEB61AFE2DBEB!14837&authkey=!ALUjO9J6Zjtu6_0
and video demonstrating problem
https://skydrive.live.com/redir.aspx?cid=17feeb61afe2dbeb&resid=17FEEB61AFE2DBEB!14874&parid=17FEEB61AFE2DBEB!14837&authkey=!ALDxgc2ymsfJHkA
Code is simple, but it doesn' work in browser with SLV5 x64. (may be in another frameworks too..)
<UserControl.Resources> <Style TargetType="telerik:RadMaskedTextInput"> <Setter Property="Mask" Value="a20"/> <Setter Property="Height" Value="30"/> <Setter Property="TextMode" Value="PlainText"/> </Style> </UserControl.Resources> <Grid x:Name="LayoutRoot" Background="White"> <sdk:TabControl > <sdk:TabItem Header="tabItem1" Name="tabItem1" > <telerik:RadMaskedTextInput /> </sdk:TabItem> <sdk:TabItem Header="tabItem2" Name="tabItem2"> <telerik:RadMaskedTextInput /> </sdk:TabItem> </sdk:TabControl> </Grid>Detailed investigation showed that if MaskedTextInput defined with property TextMode locally (not via resources) this exception is not thrown
8 Answers, 1 is accepted
0
Accepted
Hello Vitaliy,
Thank you for this report and for the detailed explanation.
This is actually a bug in the RadMaskedTextInput control and it is logged in our bug tracking system here, where you can check its status and vote for it. We will do our best to provide a fix for it in some of our forthcoming releases.
Your Telerik points are updated according your report.
Regards,
Vladislav
the Telerik team
Thank you for this report and for the detailed explanation.
This is actually a bug in the RadMaskedTextInput control and it is logged in our bug tracking system here, where you can check its status and vote for it. We will do our best to provide a fix for it in some of our forthcoming releases.
Your Telerik points are updated according your report.
Regards,
Vladislav
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>
0
Vit100
Top achievements
Rank 1
Rank 1
answered on 12 Jan 2012, 03:12 PM
The most important that you are aware abt this problem, so eventually fix will be created...
Btw, I've noticed that telerik controls have more and more issues lately... Is it related to complexity of controls or quality of development?
Btw, I've noticed that telerik controls have more and more issues lately... Is it related to complexity of controls or quality of development?
0
Hi Vitaliy,
Thank you for getting back to us. I don't think that the increase of the issues you noticed is caused by the complexity of controls or quality of development. As we are constantly trying to provide award-winning controls, we have defined a customers-needs-based process in which we want to cover most of the scenarios that our users want to implement with the controls.
Naturally when we start working on a control, we always plan what features and functionality will be supported and how to facilitate the efforts needed to use the control in a set of designated scenarios. Unfortunately initially we cannot cover every scenario in which our customers will use our controls and this is why we highly appreciate the feedback we get on them. And as we are constantly striving to improve our controls, we log every case, every issue that the implementation of our controls causes in this case and every feature request in our Public Tracking System. But then we also have to make sure that our set of controls is expanding to allow our customer to create even more powerful applications.
This is why we have a long to-do list which is constantly updated and the tasks it contains have to be prioritized based on the customers demands and requirements. And if you feel that there are issues that are not being addressed and they are preventing you from building your application, please let us know. We will definitely look into them and prioritize them accordingly.
Also, this may be a bit off-point here, but you recently made a suggestion on how to improve our online documentation by keeping a list of fixes/what's new for every control. In this context, I wanted to ask you how you think we should updated this page - as we have 3 official releases each year, we can update the article with every one of them. Is this what you had in mind? Also, how long do you think we should keep such a release history - for 3/4 releases back? We'll need this information when considering your suggestions and discussing how and if they can be implemented.
Greetings,
Tina Stancheva
the Telerik team
Thank you for getting back to us. I don't think that the increase of the issues you noticed is caused by the complexity of controls or quality of development. As we are constantly trying to provide award-winning controls, we have defined a customers-needs-based process in which we want to cover most of the scenarios that our users want to implement with the controls.
Naturally when we start working on a control, we always plan what features and functionality will be supported and how to facilitate the efforts needed to use the control in a set of designated scenarios. Unfortunately initially we cannot cover every scenario in which our customers will use our controls and this is why we highly appreciate the feedback we get on them. And as we are constantly striving to improve our controls, we log every case, every issue that the implementation of our controls causes in this case and every feature request in our Public Tracking System. But then we also have to make sure that our set of controls is expanding to allow our customer to create even more powerful applications.
This is why we have a long to-do list which is constantly updated and the tasks it contains have to be prioritized based on the customers demands and requirements. And if you feel that there are issues that are not being addressed and they are preventing you from building your application, please let us know. We will definitely look into them and prioritize them accordingly.
Also, this may be a bit off-point here, but you recently made a suggestion on how to improve our online documentation by keeping a list of fixes/what's new for every control. In this context, I wanted to ask you how you think we should updated this page - as we have 3 official releases each year, we can update the article with every one of them. Is this what you had in mind? Also, how long do you think we should keep such a release history - for 3/4 releases back? We'll need this information when considering your suggestions and discussing how and if they can be implemented.
Greetings,
Tina Stancheva
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>
0
Vit100
Top achievements
Rank 1
Rank 1
answered on 16 Jan 2012, 07:52 PM
Hi Tina,
Regarding documentation.
For example, customer/developer wants to use RadMaskedInput control.
Ok, he opens TDN =telerik developers network library(kind of MSDN library) url and reads all instructions, etc...
Project is compiled, released and is in production....
After some time developer decided to upgrade libs to the latest version (could be few Rad releases in between)... He reads release notes for current build, nothing suspicios there, a lot of stuff fixed. Cool !!!
Ok , dll's replaced, project hopefully builds, but during run time something goes wrong (different behaviour, for example RadGrid RowActivation event or RadMaskedInput Text property)...
Now, only one way to find what wrong is - find somewhere release notes, try to find what was changed and when..
But instead it would be nice if open documentation for trouble control, and have section: release notes history. There you could put what was changed/added, when. Release history could be long - either last few years or all releases.
In this case developer can see that something was changed in "trouble" control without looking at release note for whole library, where only changed controls mentioned and link to each control's release note provided (info could be duplicated in main release note as well).
Something like this -).
Now one more small improvement suggestion. In http://www.telerik.com/help/silverlight/ would be nice to have left panel in independent frame with scroll, same as MSDN classic view left panel. In MSDN click on a link keeps left selected branch active, and you don't need to scroll whole page to find tree branch again.
In case of Telerik, lets say you see documentation for controls which are on the very bottom of the tree (RadWindow or RadZip). Click on any link refreshes page and you have to scroll to very buttom again to find where you were.
If would be nice if left panel is not updated.
Anyway, hard to explain, easier to show -)) look at msdn lib (classic view) to see difference.
Regarding documentation.
For example, customer/developer wants to use RadMaskedInput control.
Ok, he opens TDN =telerik developers network library(kind of MSDN library) url and reads all instructions, etc...
Project is compiled, released and is in production....
After some time developer decided to upgrade libs to the latest version (could be few Rad releases in between)... He reads release notes for current build, nothing suspicios there, a lot of stuff fixed. Cool !!!
Ok , dll's replaced, project hopefully builds, but during run time something goes wrong (different behaviour, for example RadGrid RowActivation event or RadMaskedInput Text property)...
Now, only one way to find what wrong is - find somewhere release notes, try to find what was changed and when..
But instead it would be nice if open documentation for trouble control, and have section: release notes history. There you could put what was changed/added, when. Release history could be long - either last few years or all releases.
In this case developer can see that something was changed in "trouble" control without looking at release note for whole library, where only changed controls mentioned and link to each control's release note provided (info could be duplicated in main release note as well).
Something like this -).
Now one more small improvement suggestion. In http://www.telerik.com/help/silverlight/ would be nice to have left panel in independent frame with scroll, same as MSDN classic view left panel. In MSDN click on a link keeps left selected branch active, and you don't need to scroll whole page to find tree branch again.
In case of Telerik, lets say you see documentation for controls which are on the very bottom of the tree (RadWindow or RadZip). Click on any link refreshes page and you have to scroll to very buttom again to find where you were.
If would be nice if left panel is not updated.
Anyway, hard to explain, easier to show -)) look at msdn lib (classic view) to see difference.
0
Hi Vitaliy,
Thank you for getting back to us. Your feedback raised a discussion and we decided to describe the release history of each control in its documentation. With the Q1 2012 release the documentation of the RadControls will include articles on what's new and fixed in each control as well as a list of breaking changes in case there are any.
We'll also consider the left pane scroll suggestion.
As a small sign of appreciation for your feedback, I updated your Telerik account.
All the best,
Tina Stancheva
the Telerik team
Thank you for getting back to us. Your feedback raised a discussion and we decided to describe the release history of each control in its documentation. With the Q1 2012 release the documentation of the RadControls will include articles on what's new and fixed in each control as well as a list of breaking changes in case there are any.
We'll also consider the left pane scroll suggestion.
As a small sign of appreciation for your feedback, I updated your Telerik account.
All the best,
Tina Stancheva
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>
0
Hi Vitaliy,
We want to inform you, that this issue is fixed and the fix will be available in our next internal build and in the upcoming official releases.
It will be great if you can give it a try (once it is available) and let us know if it fits your scenario(s)/expectation(s).
Any additional feedback on the subject is highly appreciated.
Greetings,
Vladislav
the Telerik team
We want to inform you, that this issue is fixed and the fix will be available in our next internal build and in the upcoming official releases.
It will be great if you can give it a try (once it is available) and let us know if it fits your scenario(s)/expectation(s).
Any additional feedback on the subject is highly appreciated.
Greetings,
Vladislav
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get it now >>
0
Vit100
Top achievements
Rank 1
Rank 1
answered on 08 Feb 2012, 03:57 PM
i did test today with the latest intenal build - 2011.3.1406.1040 - same story - bug is still there.
0
Hi Vitaliy,
Please accept our apology for this. Unfortunately the fix wasn't included in the internal build but it will be included in the upcoming Q1 2012 official release later this month. We will appreciate your feedback once the release is out.
Regards,
Tina Stancheva
the Telerik team
Please accept our apology for this. Unfortunately the fix wasn't included in the internal build but it will be included in the upcoming Q1 2012 official release later this month. We will appreciate your feedback once the release is out.
Regards,
Tina Stancheva
the Telerik team
Sharpen your .NET Ninja skills! Attend Q1 webinar week and get a chance to win a license! Book your seat now >>