Editing contents of a <TabItem> causes the designer to swap back to the first <TabItem>
See original GitHub issueNormally in WPF (I believe) when editing the XAML contents of a <TabItem>
the designer will switch to that tab so you can see the controls you are adding. I can also switch to this tab by clicking on it in the designer.
In Avalonia, I can click on the tab in the designer but the moment I start modifying the XAML contents of that tab, the designer swaps back to the first tab.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:9 (9 by maintainers)
Top Results From Across the Web
c# - Changing tab item of tabcontrol on design view
I'm trying to add control to another TabItem on design view, but I can only see the first TabItem with all the controls...
Read more >Tab reloads control after switching tab in UI for Silverlight
The TabControl removes the content when no longer needed because the content of the TabItem could be anything, including something "heavy". If ...
Read more >TabControl Class (System.Windows.Forms)
A TabControl contains tab pages, which are represented by TabPage objects that you add through the TabPages property. The order of tab pages...
Read more >About Tab Controls - Win32 apps
You can apply certain characteristics to tab controls by specifying tab control styles when the control is created. For example, you can specify ......
Read more >Flutter TabBar: A complete tutorial with examples
TabBar enables you to improve the UX of your Flutter app by organizing content with tabs for users to tap and scroll through....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
BringIntoView
I think this is a bit of over-engineering, because - as I understand it - there would be special concept for tab control, to change tabs based on what it sees in designer. However I think this is not really robust, because next things will soon follow, like scroll scrollviewer to edited item etc.
I think what we really need here is Xaml hot-reload, so user may choose tabitem he wishes, and then find the subtree which needs to be modified and only that subtree is reloaded in previewer. Do we have plans to support it?