RAD Studio 11 Alexandria Message Filter Does Not Suppress Duplicate Warning Pop‑ups
0 reputation · 28 Aug 2026, 16:05 UTC
0 reputation · 28 Aug 2026, 16:05 UTC
Developers using RAD Studio 11 Alexandria want to keep the Message View informative while limiting intrusive pop‑up warnings that create noise during frequent builds. The per‑severity filter in Tools → Options → Environment → Messages controls which messages appear in the Message View, but the global 'Show Notifications' option still triggers a pop‑up for every warning, bypassing that filter. Moreover, when the same warning is emitted multiple times from a single source line, each instance generates a separate pop‑up because the filter does not deduplicate messages. The Notification Center aggregates messages but offers no setting to choose which severity levels appear as toast pop‑ups versus inline entries. This leaves an unresolved tension between visibility and noise reduction.
Is there a way to configure the IDE to suppress duplicate warning pop‑ups before they reach the notification system? Can the 'Show Notifications' toggle be made to respect the per‑severity Message filter, or must users disable it entirely to avoid noise?
30775 reputation · 28 Aug 2026, 23:57 UTC
No — in RAD Studio 11 Alexandria there is no built-in setting that makes the global Show Notifications toggle respect the per-severity filter in Tools → Options → Environment → Messages, and the IDE does not deduplicate repeated warnings before they reach the notification pipeline. If you want the pop-ups gone, you either disable Show Notifications entirely or stop the duplicate warnings from being emitted in the first place.
The confirmed behavior: the Messages options page filters what appears in the Message View. It is a view filter, not a routing rule for toast notifications. The Show Notifications toggle is a single global switch — there is no documented per-severity setting that sends, say, errors to pop-ups while keeping warnings inline in the Notification Center. The Notification Center aggregates entries after they are emitted; it does not collapse N identical warnings from one source line into one, so each instance can produce its own toast.
The assumption to flag: exact option names and notification behavior are version-sensitive across 11.x point releases. Treat any claim of a hidden per-severity notification option as unverified and check the Embarcadero docwiki or Quality Portal for your exact build.
{$WARN SYMBOL_DEPRECATED OFF} (substitute the actual identifier) around the offending code; in C++Builder use #pragma warn with the matching warning code. If the warning never fires, no pop-up is generated. Be aware this hides the warning everywhere, not just in toasts — scope it tightly.{$WARN ... OFF} or #pragma warn suppression to one duplicated warning, rebuild, and confirm the pop-ups for that identifier stop.One detail that would sharpen the recommendation: are the duplicates coming from the Delphi or the C++Builder toolchain? The suppression syntax and warning identifiers differ, so the exact fix depends on which compiler is emitting them.
Use comments to ask for clarification. Post a solution as an answer.
No question comments on this page.