Selector buttons out of screen

10 posts, 0 answers
  1. Miroslav
    Miroslav avatar
    30 posts
    Member since:
    Feb 2012

    Posted 23 Apr Link to this post

    Hello,

    I have problem with accessing selector buttons in DatePicker and TimePicker too. When I'm running my app in emulator, than I see buttons. But when I run app on my test device (Lumia 550), buttons are hidden with navigation bar. How can I set DatePicker for soft navigation bar?

    Best Regards

    Miroslav Mareš

  2. Ivaylo Gergov
    Admin
    Ivaylo Gergov avatar
    661 posts

    Posted 27 Apr Link to this post

    Hi,

    As I am not completely sure what exactly you are trying to achieve, could you please elaborate more or send me some project or screenshot with additional explanation?

    I am looking forward to your reply.

    Regards,
    Ivaylo Gergov
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  3. DevCraft banner
  4. Miroslav
    Miroslav avatar
    30 posts
    Member since:
    Feb 2012

    Posted 28 Apr in reply to Ivaylo Gergov Link to this post

    Hello,

    I send you screenshots from my phone Lumia 550.

    Best Regards

    Miroslav Mareš

  5. Ves
    Admin
    Ves avatar
    2879 posts

    Posted 03 May Link to this post

    Hi Miroslav,

    I am afraid we are not able to reproduce the issue at hand. Still, here is a suggestion -- you can attach to Opened event of RadDatePicker and use ApplicationView.PreferredLaunchWindowingMode property. Set it to ApplicationViewWindowingMode.FullScreen. In addition, you might want to set it back to Auto when RadDatePicker closes.

    Best regards,
    Ves
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  6. Miroslav
    Miroslav avatar
    30 posts
    Member since:
    Feb 2012

    Posted 04 May in reply to Ves Link to this post

    Hello,

    this workaround not worked. Result is still same as on screens, what I posted before.

    Best Regards

    Miroslav Mareš

  7. Ivaylo Gergov
    Admin
    Ivaylo Gergov avatar
    661 posts

    Posted 10 May Link to this post

    Hi Miroslav,

    We will need some more time to investigate this and I will get back to you as soon as we have some resolution or a workaround.


    Regards,
    Ivaylo Gergov
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  8. Greg
    Greg avatar
    48 posts
    Member since:
    Sep 2010

    Posted 22 Jul Link to this post

    Any update on this?  I'm experiencing it on a Lumia 550 and have clients who are experiencing it too.

    I have gotten around it by changing the entire app to full screen when running on Windows 10 Mobile like this:

    if (Windows.System.Profile.AnalyticsInfo.VersionInfo.DeviceFamily == "Windows.Mobile")
    {
    ApplicationView.TryEnterFullScreenMode();
    }

    I don't think this is a great solution though.

    Thanks,

    Greg

  9. Lance | Tech Support Engineer, Sr.
    Admin
    Lance | Tech Support Engineer, Sr. avatar
    135 posts

    Posted 22 Jul Link to this post

    Hi Greg,

    This is unrelated to Telerik controls specifically, but rather it's a general Windows Mobile programming scenario you need to account for when your app is running on a device that does not use hardware buttons.

    Fortunately, there is a way you can detect and manage this using a little logic (usually put within your root frame). Here is an example:

    First, hook into the VisibleBoundsChanged event:

    var appView = ApplicationView.GetForCurrentView();
    appView.VisibleBoundsChanged += VisibleBoundsChanged;

    Then in the event handler, detect if the on-screen buttons are visible, if they are determine the occulded rect and adjust the height of your UI. Here's an example:

    private void VisibleBoundsChanged(ApplicationView sender, object args)
            {
                if (Windows.Foundation.Metadata.ApiInformation.IsTypePresent("Windows.UI.ViewManagement.StatusBar"))
                {
                    var statusBar = StatusBar.GetForCurrentView();
                    var appView = ApplicationView.GetForCurrentView();
                    var inputPane = InputPane.GetForCurrentView();
     
                    double newHeight;
                    double newWidth;
     
                    var orientation = DisplayInformation.GetForCurrentView().CurrentOrientation;
     
                    Debug.WriteLine($"CurrentOrientation: {orientation}");
     
                    switch (orientation)
                    {
                        case DisplayOrientations.None:
                            break;
                        case DisplayOrientations.Landscape:
                            newWidth = appView.VisibleBounds.Width +
                                (statusBar?.OccludedRect.Width) ?? 0 +
                                (inputPane?.OccludedRect.Width) ?? 0;
     
                            if ((inputPane?.OccludedRect.Width ?? 0) <= 0 || newWidth < this.Width)
                                this.Width = newWidth;
     
                            //NOTE: If you see that the Frame is centered and there is space at the top and the bottom is still clipped, you may need to shift it over
                            this.HorizontalAlignment = Windows.UI.Xaml.HorizontalAlignment.Left;
                            this.VerticalAlignment = Windows.UI.Xaml.VerticalAlignment.Top;
                            break;
                        case DisplayOrientations.Portrait:
                            newHeight = appView.VisibleBounds.Height +
                                (statusBar?.OccludedRect.Height) ?? 0 +
                                (inputPane?.OccludedRect.Height) ?? 0;
     
                            if ((inputPane?.OccludedRect.Height ?? 0) <= 0 || newHeight < this.Height)
                                this.Height = newHeight;
     
                            this.VerticalAlignment = Windows.UI.Xaml.VerticalAlignment.Top;
                            this.HorizontalAlignment = Windows.UI.Xaml.HorizontalAlignment.Stretch;
                            break;
                        case DisplayOrientations.LandscapeFlipped:
                            newWidth = appView.VisibleBounds.Width +
                                (statusBar?.OccludedRect.Width) ?? 0 +
                                (inputPane?.OccludedRect.Width) ?? 0;
     
                            if ((inputPane?.OccludedRect.Width ?? 0) <= 0 || newWidth < this.Width)
                                this.Width = newWidth;
     
                            this.HorizontalAlignment = Windows.UI.Xaml.HorizontalAlignment.Right;
                            this.VerticalAlignment = Windows.UI.Xaml.VerticalAlignment.Top;
                            break;
                        case DisplayOrientations.PortraitFlipped:
                            newHeight = appView.VisibleBounds.Height +
                                (statusBar?.OccludedRect.Height) ?? 0 +
                                (inputPane?.OccludedRect.Height) ?? 0;
     
                            if ((inputPane?.OccludedRect.Height ?? 0) <= 0 || newHeight < this.Height)
                                this.Height = newHeight;
     
                            this.VerticalAlignment = Windows.UI.Xaml.VerticalAlignment.Bottom;
                            this.HorizontalAlignment = Windows.UI.Xaml.HorizontalAlignment.Stretch;
                            break;
                        default:
                            break;
                    }
                }
            }



    We are active investigating if this is something we can add into the product, however it is unlikely we will add  this approach affects the entire application, not just the modal for the picker.

    Once the engineering team has completed the investigation into how we can mitigate this just for the UI for UWP pickers, they will come back and update this thread.

    Thank you for your patience and understanding while we investigate this further.

    Regards,
    Lance | Tech Support Engineer, Sr.
    Telerik by Progress
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  10. John Strever
    John Strever avatar
    2 posts
    Member since:
    Mar 2005

    Posted 22 Aug Link to this post

    A suggestion to Telerik Engineering...(since it seems to be on all windows phones now)

     

    Can you set a setting in the control that simply shortens the height of the control by 100px, and center it.... that would certainly do it and be a super fast super easy fix.

  11. Tsvyatko
    Admin
    Tsvyatko avatar
    832 posts

    Posted 24 Aug Link to this post

    Hi John,

    Thank you for the suggestions. With the upcoming Beta (due in the the next couple of weeks) we have addressed this issue. Now, the DatePicker popup opens in the visible screen bounds.

    Please excuse us for the delay on this issue.

    Regards,
    Tsvyatko
    Telerik by Progress
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Back to Top
DevCraft banner