Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The statements don't contradict, they are quite adding up to a whole.<br> The UI-thread is responsible for refreshing the window and the controls in it, so the react when you activate them, go over them with the mouse cursor, etc.<br> If you would perform a long-running operation, for example a <code>for-loop</code> with 10000 iterations, the <code>UI would freeze</code> and become unresponsive (the window will blur and the little blue donut of death will come up). Once the <code>for-loop</code> has completed, your UI will be there again.<br> In order to relieve the UI-thread from additional burden, you put long-running tasks in seperate threads/tasks, so they execute concurrently. Your <code>UI</code> will stay responsive and accept commands (clicks, keystrokes, ...). Maybe unrelated but grappling on the basics behind it</p> <blockquote> <p>Users expect an app to remain responsive while it does computation, regardless of the type of machine. This means different things for different apps. For some this translates to providing more realistic physics, loading data from disk or the web faster, quickly presenting complex scenes and navigating between pages, finding directions in a snap, or rapidly processing data. Regardless of the type of computation, users want their app to act on their input and eliminate instances where it appears suspended while it “thinks.”</p> </blockquote> <p>Read <a href="http://msdn.microsoft.com/en-us/library/windows/apps/hh994635.aspx" rel="nofollow">this</a> article here.</p>
    singulars
    1. This table or related slice is empty.
    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. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

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