aboutsummaryrefslogtreecommitdiffstats
path: root/src/cidschemehandler.h
diff options
context:
space:
mode:
authorDanilo M. <danix@danix.xyz>2026-08-20 12:32:46 +0200
committerDanilo M. <danix@danix.xyz>2026-08-20 12:32:46 +0200
commitfd3bd06580f6bde5d57a68b82cac46eefd89f412 (patch)
tree41947d2cc2f6f9d2daddbf6f5cf49a4eff1144cc /src/cidschemehandler.h
parent0496db64c34763c586ffad7d68ed9845a5395452 (diff)
downloadqtmaildir-fd3bd06580f6bde5d57a68b82cac46eefd89f412.tar.gz
qtmaildir-fd3bd06580f6bde5d57a68b82cac46eefd89f412.zip
docs: specify how a send shows progress, item 123
The spec said "disabled with a spinner" without saying where, which leaves a popup as a reasonable reading of it. A popup is wrong here: it would be modal over a window that is already disabled, and it can be dismissed while the operation continues, which is the indicator ambiguity items 18, 19, 28 and 54 each closed once. Progress goes in the composer's own status bar, through the three stages the operation actually has, since a failure filing the sent copy means something different from a failure sending. The window closing is the success message. The indicator is an indeterminate QProgressBar built inline, matching MainWindow's m_syncProgress rather than factoring out a shared widget: this codebase builds small UI inline, and two progress bars do not justify a third class. Also settles what the staged display implies for a sent-copy write that fails after a successful send: the composer still closes, because holding it open for a message already sent invites sending it twice, and the warning goes to the main window's status bar instead. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01YDq53rMd3AQp7QmcZzpuBM
Diffstat (limited to 'src/cidschemehandler.h')
0 files changed, 0 insertions, 0 deletions