BladeItem as UserControl

[Pinox]

Hi Guys,

I have a bladeview control that works great , but the control is getting too big and slow to manage in Visual Studio so I want to create UserControls for the BladeItems.

`controls:BladeView

            <controls:BladeItem IsOpen="True" TitleBarVisibility="Visible" />

            <usercontrols:Blade1 IsBladeOpen="True"  />

</controls:BladeView>`

When I apply the above code I always get an extra BladeItem that can be seen from the title bar below.

With the extra BladeItem you cannot close your intended blade item.

Hello Pinox, thank you for opening an issue with us!

I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌

[Kyaa-dost]

Thanks, @Pinox! let's see if anyone from the community can look into this and provide insight regarding what could be causing the issue.

[michael-hawker]

@Pinox is your 'UserControl' still inheriting from UserControl? If you make it inherit from BladeItem instead, then it should work fine. If so, what's happening here is the parent panel is implicitly wrapping the UserControl in a BladeItem as it's not the child type for the container, so it creates one for you in case you were using a data-model and template. This is usually the standard XAML behavior.

[Pinox]

magic !!! thanks @michael-hawker.

[michael-hawker]

@Kyaa-dost does it make sense for us to move questions to discussion after and mark answers? Not sure if we have old ones in the repo we could do this for to build a bit of a database?

[Kyaa-dost]

@michael-hawker I was thinking more in terms of opening/asking questions in "discussions" so our community would be in the habit of checking the Discussions tab as well and provide input. We certainly want questions to be answered and by emphasizing Discussions, we will be bringing as much traffic. This way we can prioritize essential issues and features in the Issues section and keep the issues decluttered. Again we can certainly discuss more pros and cons and come to conclusion?