Compass and VisualCue are clipped after scaling

8 posts, 0 answers
  1. Dzsek
    Dzsek avatar
    1 posts
    Member since:
    Sep 2014

    Posted 16 Sep 2014 Link to this post

    Hello,
    After using ScaleTransform to scale up the UI of our application the Compass and VisualCue elements are clipped to, what seems to be, the unscaled size of the RadDocking control.

    I am scaling the application by adding
    <Grid.LayoutTransform>
                <ScaleTransform ScaleX="1.5" ScaleY="1.5" />
    </Grid.LayoutTransform>

    to the root element of the main window and setting the compass and visualcue scaling with
    <telerikDocking:RadDocking.CompassStyle>
        <Style TargetType="telerik:Compass">
            <Setter Property="LayoutTransform">
                <Setter.Value>
                    <ScaleTransform ScaleX="1.5" ScaleY="1.5"/>
                </Setter.Value>
            </Setter>
        </Style>
    </telerikDocking:RadDocking.CompassStyle>
    <telerikDocking:RadDocking.RootCompassStyle>
        <Style TargetType="telerik:RootCompass">
            <Setter Property="LayoutTransform">
                <Setter.Value>
                    <ScaleTransform ScaleX="1.5" ScaleY="1.5" />
                </Setter.Value>
            </Setter>
        </Style>
    </telerikDocking:RadDocking.RootCompassStyle>
    <telerikDocking:RadDocking.VisualCueStyle>
        <Style TargetType="telerik:VisualCue">
            <Setter Property="LayoutTransform">
                <Setter.Value>
                    <ScaleTransform ScaleX="1.5" ScaleY="1.5" />
                </Setter.Value>
            </Setter>
        </Style>
    </telerikDocking:RadDocking.VisualCueStyle>

    You can see the result in the attached image.
    Are there other elements of the RadDocking control which I didn't set the scaling for, or am I approaching the whole scaling the wrong way ?
  2. Vladi
    Admin
    Vladi avatar
    749 posts

    Posted 18 Sep 2014 Link to this post

    Hello Dzsek,

    Thank you for contacting us.

    In the current version of RadDocking intentionally scaling the control is not a supported scenario. The control is designed to scale it's parts relative to the OS's resolution. As the RadDocking is a complex control that involves many visual elements created at run time using the LayoutTransform's ScaleTransform is not an applicable approach.

    We always try to improve our control and will discuss the possibility of adding such scaling feature in one of our future releases of Telerik UI for WPF.

    Regards,
    Vladi
    Telerik
     
    Check out Telerik Analytics, the service which allows developers to discover app usage patterns, analyze user data, log exceptions, solve problems and profile application performance at run time. Watch the videos and start improving your app based on facts, not hunches.
     
  3. Анатолій
    Анатолій avatar
    42 posts
    Member since:
    Oct 2012

    Posted 13 Jan 2015 in reply to Vladi Link to this post

    Hello Vladi,
    I'm glad for all telerik controls and their improves from version to version.
    Are there any futher forecasts with scalling this control?

    The main disaster is displacement of rootcompass (which replacing) and visualcue (which stay in the middle).
    Maybe there any solution to avoid displacement, is not it?
  4. Vladi
    Admin
    Vladi avatar
    749 posts

    Posted 15 Jan 2015 Link to this post

    Hi Anatoliy,

    While there are no immediate plans for implementing support for using ScaleTransform in order to scale the RadDocking control and its compasses/drop cues we always do our best to improve our controls which is why we logged the discussed feature request into our feedback portal. You can vote for it and track its status here.

    If such feature receives enough user demand we will do our best to provide it as soon as possible.

    Regards,
    Vladi
    Telerik
     

    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.

     
  5. Анатолій
    Анатолій avatar
    42 posts
    Member since:
    Oct 2012

    Posted 14 Jun Link to this post

    Hi Vladi,

    Can you update the status of current issue? 

     

    Regards, Anatoliy

  6. Stefan X1
    Admin
    Stefan X1 avatar
    737 posts

    Posted 19 Jun Link to this post

    Hello Anatoliy,

    Thanks for the update.

    Currently, this feature request is not scheduled for implementation. Please note, that this depends on various aspects. One of the major ones is the user's demand for providing a given feature. We will, however, do our best to consider it in our next planning.

    Best Regards,
    Stefan X1
    Progress Telerik
    Want to extend the target reach of your WPF applications, leveraging iOS, Android, and UWP? Try UI for Xamarin, a suite of polished and feature-rich components for the Xamarin framework, which allow you to write beautiful native mobile apps using a single shared C# codebase.
  7. Анатолій
    Анатолій avatar
    42 posts
    Member since:
    Oct 2012

    Posted 19 Jun Link to this post

    Hi Stefan,

    Nothing to thank for, yet!

    What prevents you from scheduling the implementation of this functionality for those three and half years?! Is it really difficult and need so much time...

  8. Stefan X1
    Admin
    Stefan X1 avatar
    737 posts

    Posted 22 Jun Link to this post

    Hello Anatoliy,

    Firstly, I would like shed some light on the general practice that we have when prioritizing the items in our backlog. As mentioned in my previous reply, the formula for calculating the priority of a given feature request includes various components one of which is the user's demand for it. Another important part of it is the resource that is needed for the implementation and testing of a given feature.

    For this case in particular, supporting a ScaleTransform would require the calculations of the VisualCue to be rewritten. Note, that this is not a behavior that can be achieved in a straightforward manner. Thus, for the time being, the feature request discussed in this thread is not yet implemented. However, may I kindly ask you to share some details on whether your requirement is the same as the one initially discussed in this thread? If it is not, would it be possible for you to attach a sample application in the feedback item that demonstrates the setup you are using, so we can take it in consideration when implementing the feature?

    Regards,
    Stefan X1
    Progress Telerik
    Want to extend the target reach of your WPF applications, leveraging iOS, Android, and UWP? Try UI for Xamarin, a suite of polished and feature-rich components for the Xamarin framework, which allow you to write beautiful native mobile apps using a single shared C# codebase.
Back to Top