5 Answers, 1 is accepted
Your remark is correct. The customScreenRanges defined in the article should be as follows:
The article will be updated accordingly.
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
It still has not been updated!
I have 2 questions/comments on this.
1. Where is XS? "customScreenRanges.ExtraSmallScreenSizeRange = new ScreenRange(0, 360);"
2. How can I set a range with an open top end? Like customScreenRanges.ExtraLargeScreenSizeRange = new ScreenRange(1281);
I apologize that this issue has not been fixed yet. It has now been fixed and the update will go live with the next documentation update. As a side note, we have recently released public GitHub repository of our documentation, which could be modified by everyone. And as pointed in the blog post on that topic "all valuable contributions will be rewarded with Telerik points–just make sure you are using the same email for your GitHub and Telerik.com accounts."
As for the first question posed, I guess that the first one comes after comparing the RadPageLayout breakpoints and the RadDeviceDetectionFramework ranges. The RadPageLayout has different viewport breakpoints than the ones used for RadDeviceDetectionFramework due to its different purpose. The RadPageLayout is used for setting up layout, not for enabling render mode. Thus, it needs one more level for enabling different layout for different cases. In addition, the RadDeviceDetectionFramework provides the opportunity to define your own custom ranges, if the default ones does not fit your case. That is why there is no ExtraSmallScreenSizeRange for RadDeviceDetectionFramework.
And for your second question, the answer is that you cannot set a range with open top end. You could define it with a greater number as a top border, but it cannot be empty.
I do not want to sound angry or upset, but I do not want to have to update the docs myself. I pay for my Telerik subscription and I expect a professionally maintained product and not something I can update myself. While I appreciate the opportunity to earn points from time to time I think 9 months is too long to expect a simple document change.
As far as my questions regarding the commonality between PageLayout and DeviceDetection I would think it would be beneficial if they did have the same breakpoints. I think Ivan is even recommending using one to work with the other in this post.
I sincerely apologize if the information about the new opportunity for contributing to our documentation seems as an urge to fix the error by yourself. I just wanted to present you this new feature we released recently with our GitHub hosted documentation.
As far as the breakpoints inconsistency is concerned, we will update the documentation once that story is complete. Until then, you could define custom ranges as I mentioned in my previous reply. Since the custom ranges part in the help article is exactly the one that contains the repeated ExtraLarge mistake, I did not provide a link to it specifically. Please excuse me if that has caused you spend extra time searching.