Terminal.Gui/docfx/docs/multitasking.md

Multitasking and Background Operations

See also Cross-platform Driver Model

Terminal.Gui applications run on a single main thread with an event loop that processes keyboard, mouse, and system events. This document explains how to properly handle background work, timers, and asynchronous operations while keeping your UI responsive.

Threading Model

Terminal.Gui follows the standard UI toolkit pattern where all UI operations must happen on the main thread. Attempting to modify views or their properties from background threads will result in undefined behavior and potential crashes.

The Golden Rule

Always use Application.Invoke() to update the UI from background threads.

Background Operations

Using async/await (Recommended)

The preferred way to handle background work is using C#'s async/await pattern:

private async void LoadDataButton_Clicked()
{
    loadButton.Enabled = false;
    statusLabel.Text = "Loading...";
    
    try
    {
        // This runs on a background thread
        var data = await FetchDataFromApiAsync();
        
        // This automatically returns to the main thread
        dataView.LoadData(data);
        statusLabel.Text = $"Loaded {data.Count} items";
    }
    catch (Exception ex)
    {
        statusLabel.Text = $"Error: {ex.Message}";
    }
    finally
    {
        loadButton.Enabled = true;
    }
}

Using Application.Invoke()

When working with traditional threading APIs or when async/await isn't suitable:

private void StartBackgroundWork()
{
    Task.Run(() =>
    {
        // This code runs on a background thread
        for (int i = 0; i <= 100; i++)
        {
            Thread.Sleep(50); // Simulate work
            
            // Marshal back to main thread for UI updates
            Application.Invoke(() =>
            {
                progressBar.Fraction = i / 100f;
                statusLabel.Text = $"Progress: {i}%";
            });
        }
        
        Application.Invoke(() =>
        {
            statusLabel.Text = "Complete!";
        });
    });
}

Timers

Use timers for periodic updates like clocks, status refreshes, or animations:

public class ClockView : View
{
    private Label timeLabel;
    private object timerToken;
    
    public ClockView()
    {
        timeLabel = new Label { Text = DateTime.Now.ToString("HH:mm:ss") };
        Add(timeLabel);
        
        // Update every second
        timerToken = Application.MainLoop.AddTimeout(
            TimeSpan.FromSeconds(1), 
            UpdateTime
        );
    }
    
    private bool UpdateTime()
    {
        timeLabel.Text = DateTime.Now.ToString("HH:mm:ss");
        return true; // Continue timer
    }
    
    protected override void Dispose(bool disposing)
    {
        if (disposing && timerToken != null)
        {
            Application.MainLoop.RemoveTimeout(timerToken);
        }
        base.Dispose(disposing);
    }
}

Timer Best Practices

• Always remove timers when disposing views to prevent memory leaks
• Return true from timer callbacks to continue, false to stop
• Keep timer callbacks fast - they run on the main thread
• Use appropriate intervals - too frequent updates can impact performance

Common Patterns

Progress Reporting

private async void ProcessFiles()
{
    var files = Directory.GetFiles(folderPath);
    progressBar.Fraction = 0;
    
    for (int i = 0; i < files.Length; i++)
    {
        await ProcessFileAsync(files[i]);
        
        // Update progress on main thread
        progressBar.Fraction = (float)(i + 1) / files.Length;
        statusLabel.Text = $"Processed {i + 1} of {files.Length} files";
        
        // Allow UI to update
        await Task.Yield();
    }
}

Cancellation Support

private CancellationTokenSource cancellationSource;

private async void StartLongOperation()
{
    cancellationSource = new CancellationTokenSource();
    cancelButton.Enabled = true;
    
    try
    {
        await LongRunningOperationAsync(cancellationSource.Token);
        statusLabel.Text = "Operation completed";
    }
    catch (OperationCanceledException)
    {
        statusLabel.Text = "Operation cancelled";
    }
    finally
    {
        cancelButton.Enabled = false;
    }
}

private void CancelButton_Clicked()
{
    cancellationSource?.Cancel();
}

Responsive UI During Blocking Operations

private async void ProcessLargeDataset()
{
    var data = GetLargeDataset();
    var batchSize = 100;
    
    for (int i = 0; i < data.Count; i += batchSize)
    {
        // Process a batch
        var batch = data.Skip(i).Take(batchSize);
        ProcessBatch(batch);
        
        // Update UI and yield control
        progressBar.Fraction = (float)i / data.Count;
        await Task.Yield(); // Allows UI events to process
    }
}

Common Mistakes to Avoid

❌ Don't: Update UI from background threads

Task.Run(() =>
{
    label.Text = "This will crash!"; // Wrong!
});

✅ Do: Use Application.Invoke()

Task.Run(() =>
{
    Application.Invoke(() =>
    {
        label.Text = "This is safe!"; // Correct!
    });
});

❌ Don't: Forget to clean up timers

// Memory leak - timer keeps running after view is disposed
Application.MainLoop.AddTimeout(TimeSpan.FromSeconds(1), UpdateStatus);

✅ Do: Remove timers in Dispose

protected override void Dispose(bool disposing)
{
    if (disposing && timerToken != null)
    {
        Application.MainLoop.RemoveTimeout(timerToken);
    }
    base.Dispose(disposing);
}

Performance Considerations

• Batch UI updates when possible instead of updating individual elements
• Use appropriate timer intervals - 100ms is usually the maximum useful rate
• Yield control in long-running operations with await Task.Yield()
• Consider using ConfigureAwait(false) for non-UI async operations
• Profile your application to identify performance bottlenecks

See Also

• Events - Event handling patterns
• Keyboard Input - Keyboard event processing
• Mouse Input - Mouse event handling
• Configuration Management - Application settings and state