RadRibbonSplitButton causing problems with the Visual Studio 2013 Designer

7 posts, 1 answers
  1. Eric
    Eric avatar
    13 posts
    Member since:
    Jun 2015

    Posted 15 Jul 2015 Link to this post

    I am using Visual Studio 2013 with Telerik 2015.2.623.45 and I am seeing some very odd behavior with the Designer when I add a RadRibbonSplitButton to a RadRibbonView. Here is my simple test code.

    <telerik:RadRibbonView>
      <telerik:RadRibbonTab Header="Home">
        <telerik:RadRibbonGroup Header="Search">
          <telerik:RadRibbonSplitButton Text="Sketch" Size = Large" />
        </telerik:RadRibbonGroup>
      </telerik:RadRibbonTab>
    </telerik:RadRibbonView>

    When I am trying to type more XAML into the XAML tab (and the Designer is not even open, its minimized) the Designer keeps opening and selecting the RadRibbonSplitButton. Its very add (and extremely frustrating) that while I am typing or using the keyboard in the XAML tab the Designer will just take over and open directly on top of everything. I added a color picker as the content of the RadRibbonSplitButton and the color picker will draw on top of the XAML and the designer is minimized (collapsed). As it stands right now I can't even use the RadRibbonSplitButton or my Designer just takes over.

     Anyone else seeing this behavior?

     

     

     

     

  2. Answer
    Evgenia
    Admin
    Evgenia avatar
    1407 posts

    Posted 16 Jul 2015 Link to this post

    Hello Eric,

    Unfortunately I should confirm that this reproduces again with Q2 2015 binaries. I logged the issue in our feedback portal where you might track its status (here is a link to it).

    You might find your Telerik points updated as a sign of gratitude for reporting the bug to us.

    Regards,
    Evgenia
    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. UI for WPF is Visual Studio 2017 Ready
  4. Eric
    Eric avatar
    13 posts
    Member since:
    Jun 2015

    Posted 16 Jul 2015 Link to this post

    So Telerik 2015.2 (aka Q2) is out and the version we are using, right? So what are the chances that this would be fixed in 2015.2 SP1?
  5. Eric
    Eric avatar
    13 posts
    Member since:
    Jun 2015

    Posted 16 Jul 2015 Link to this post

    So Telerik 2015.2 (aka Q2) is out and the version we are using, right? So what are the chances that this would be fixed in 2015.2 SP1?
  6. Evgenia
    Admin
    Evgenia avatar
    1407 posts

    Posted 20 Jul 2015 Link to this post

    Hello Eric,

    We won't be able to provide a fix with the upcomming Q2 SP1 release. However our developers will do their best for this to be included in one of our future internal builds (released every Monday). 

    Regards,
    Evgenia
    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
  7. Gord
    Gord avatar
    20 posts
    Member since:
    Jul 2014

    Posted 09 Mar Link to this post

    I am  using 2016.1.112 for WPF and Visual Studio 2013 Pro (12.0.40629.00 Update 5), and I see a similar issue with the RadRibbonDropDown control.  Clicking on the xml node in the XAML pane immediately shifts focus to the Design pane, and I have to click a second time to be able to edit the content.  If I minimize the display so that I only have either the XAML or Design showing, and I have a dropdown selected in the design mode, clicking the XAML tab immediately jumps back to the Design tab.  The only way I can bring the XAML tab back up is to either show both, or select a control other than the dropdown (like a standard RadRibbonButton) then I am able to open the XAML tab.

     

  8. Evgenia
    Admin
    Evgenia avatar
    1407 posts

    Posted 14 Mar Link to this post

    Hi Eric,

    Unfortunately I should confirm that we reproduce the problem on our side. There is a feedback item we created where you might vote for this bug to be fixed with higher priority for the upcoming release.
    We are sorry for any inconvenience this may have caused.

    Regards,
    Evgenia
    Telerik
    Do you need help with upgrading your AJAX, WPF or WinForms project? Check the Telerik API Analyzer and share your thoughts.
Back to Top
UI for WPF is Visual Studio 2017 Ready