MATLAB App Designer uialert vs uiconfirm: Stacking Order and Focus Management

In MATLAB App Designer, both uialert and uiconfirm are modal functions that block the execution of the calling callback until the user provides input. When multiple asynchronous callbacks—such as timers or listeners—trigger these dialogs simultaneously, the behavior is governed by the MATLAB event queue.

Focus and Stacking Behavior

When two alerts are requested nearly simultaneously, MATLAB does not 'stack' them in a way that allows both to be visible at. Because these functions are modal, the first call blocks the execution of its specific callback. The second callback remains in the event queue until the first dialog is dismissed and its associated callback completes.

• Which dialog receives focus? The first dialog invoked receives focus. The second dialog will not appear (and thus cannot receive focus) until the first one is closed.
• Does MATLAB queue the dialogs? Yes, MATLAB queues the callbacks. The dialogs appear in the order the callbacks are executed, which is typically the order they were triggered in the event queue.
• Focus loss: Focus loss is rare in this scenario because the modal nature of the first alert prevents the second callback from reaching the uialert line until the first alert is cleared.

Recommended Pattern for Predictable UI

To prevent alert fatigue and ensure a predictable user experience, developers should implement a manual notification queue. Instead of calling uialert directly inside asynchronous listeners, push the notification data into a cell array and use a manager function.

% Example logic for a notification queue
if isempty(app.AlertQueue)
    app.processNextAlert();
end
app.AlertQueue{end+1} = newNotification;

function processNextAlert(app)
    if isempty(app.AlertQueue), return; end
    msg = app.AlertQueue{1};
    app.AlertQueue(1) = [];
    uialert(app.UIFigure, msg, 'Title', 'CloseButton', @(src, event) app.processNextAlert());

Assumption: This assumes you are using the standard modal UIFigure. If you are using drawnow or pause within your callbacks, the event queue may flush prematurely, leading to unexpected dialog stacking.