Databases
StackOverflow2013
Postsdbo
POPerformance issue when hosting a WPF form in a native C++ application
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPerformance issue when hosting a WPF form in a native C++ application
    primarykey
    data
    text
    <p>I have WPF window which runs fine when hosted in a WPF application but when I load it from within my native C++ application it takes a very long time to render and the UI Thread blocks until it completes.</p> <p>The main offender on my window is an series of items controls used to display a 9 by 12 grid of icons which represent states of components within my system.</p> <p>The whole items control takes up to 14 seconds for its initial render. (This is almost instant when running in a WPF app)</p> <p>Each line has a text header that when clicked displays a small summary of data (max, min, mean, std dev) for each of the status icons. clicking this header can take up to 4 seconds to render the summary but is instant in my WPF app.</p> <p>Are there any known tricks for making WPF perform nicely within a native application?</p> <p>[Edit]</p> <p>I have just tried launching it from a large .NET windows forms application using the following code:</p> <pre><code> public bool? ShowWpfDialog(System.Windows.Window window, Form owner) { var helper = new System.Windows.Interop.WindowInteropHelper(window) {Owner = (owner == null) ? IntPtr.Zero : owner.Handle}; return window.ShowDialog(); } </code></pre> <p>I have the same performance issues as when running from the native app. (the .net app also runs native code.)</p> <p>[Edit]</p> <p>When I don't use the WindowInteropHelper the code performs properly:</p> <pre><code> public bool? ShowWpfDialog(System.Windows.Window window, Form owner) { //var helper = new System.Windows.Interop.WindowInteropHelper(window) // {Owner = (owner == null) ? IntPtr.Zero : owner.Handle}; return window.ShowDialog(); } </code></pre> <p>What is the WindowInteropHelper doing that would cause a performance issue?</p> <p>[Edit]</p> <p>Could there be an issue with the way resources are resolved when I load it with an owner using the WindowInteropHelper?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USghnz
    1. USghnz
    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. VO
      singulars
      1. POPerformance issue when hosting a WPF form in a native C++ application
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POPerformance issue when hosting a WPF form in a native C++ application
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POPerformance issue when hosting a WPF form in a native C++ application
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAre you running/timing in the debugger?
      singulars
      1. POPerformance issue when hosting a WPF form in a native C++ application
      1. USReed Copsey
    2. COThe times are based on an observation when running a release build
      singulars
      1. POPerformance issue when hosting a WPF form in a native C++ application
      1. USghnz
    3. COAre you still running in the VS hosting process, or standalone/outside VS?
      singulars
      1. POPerformance issue when hosting a WPF form in a native C++ application
      1. USReed Copsey
 

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