Databases
StackOverflow2013
Postsdbo
POWPF performance loading user controls
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWPF performance loading user controls
    primarykey
    data
    text
    <p>I’m working on a WPF application with a tabbed MDI interface. Basically, the user clicks a menu item and this creates and adds a new tab. A new 'MyUserControl' is created and set to be the tab's Content. Something like this:</p> <pre><code> private void MenuItem_OnClick(object sender, RoutedEventArgs e) { this.TabControl.Items.Add(new TabItem() { Content = new MyUserControl() }); } </code></pre> <p>MyUserControl is composed of several nested controls (approx. 8 controls). When this approach is wired up to the actual control, the performance is unacceptable.</p> <p>Unless I’m losing my mind, I’ve noticed that the performance hit seems to be much less when declaring the tab and content in xaml ahead of time and simply toggling the tab item's Visibility property:</p> <pre><code> &lt;Controls:TabControl x:Name="TabControl" Grid.Row="1"&gt; &lt;Controls:TabControl.Items&gt; &lt;Controls:TabItem x:Name="MyTabItem" Visibility="Collapsed"&gt; &lt;Controls:MyUserControl x:Name="MyUserControl" /&gt; &lt;/Controls:TabItem&gt; &lt;/Controls:TabControl.Items&gt; &lt;/Controls:TabControl&gt; </code></pre> <p>and</p> <pre><code> private void MenuItem_OnClick(object sender, RoutedEventArgs e) { this.MyTabItem.Visibility = Visibility.Visible; } </code></pre> <p>Can anyone explain this? Is it really more efficient to build the "visual tree" in xaml rather than programmatically? Or has the performance hit in my second approach just been moved to the overall form's load instead of when the menu item is clicked as in the first approach?</p> <p>The second approach definitely seems to perform much better. Any thoughts?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDave Clemmer
    1. USJohn Russell
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. COfrom your comments, it seems your example is much-simplified from your real code. Is the complexity that you have a huge number of child controls, or is it that you're doing a lot of data work in the control load?
      singulars
      1. POWPF performance loading user controls
      1. USDan Puzey
    2. CODefinitely. I was trying to keep the example simple. Based on the comments below, I believe the complexity is related to the number of controls/styles. The control load event handlers for all the child controls are really not that complicated.
      singulars
      1. POWPF performance loading user controls
      1. USJohn Russell
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload