Home/ Questions/Q 943147
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T22:23:23+00:00

Why i should call Control.Invoke from non-ui thread? As i know any manipulations with

  • 0

Why i should call Control.Invoke from non-ui thread? As i know any manipulations with control are the messages to control. So when i call, for example TextBox.Text = “text”, it will produce message SendMessage(TextBox.Hanlde…). That message will be queued into UI thread message queue and dispatched by UI thread. Why i have to call invoke, even it will produce the same message?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There are two reasons MS developers made this restriction:

    1. Some UI functions have access to thread-local storage (TLS). Calling these functions from another thread gives incorrect results on TLS operations.

    2. Calling all UI-related functions from the same thread automatically serializes them, this is thread-safe and doesn’t require synchronization.

    From our point of view, we just need to follow these rules.

    • 0