From 18eaa221d326032cd4e69579b1168441e5587fc2 Mon Sep 17 00:00:00 2001 From: Bartosz Taudul Date: Thu, 6 Aug 2026 22:37:24 +0200 Subject: [PATCH] Regenerate markdown manual. --- manual/tracy.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/manual/tracy.md b/manual/tracy.md index 22cc1e80..4ab65bc7 100644 --- a/manual/tracy.md +++ b/manual/tracy.md @@ -11,7 +11,7 @@ The user manual **Bartosz Taudul** [\](mailto:wolf@nereid.pl) -2026-07-28 +2026-08-06 # Quick overview {#quick-overview .unnumbered} @@ -2045,7 +2045,7 @@ Unlike C++, there's no automatic destruction mechanism in C, so you will need to [^55]: GCC and Clang provide `__attribute__((cleanup))` which can used to run a function when a variable goes out of scope. -Zone text and name may be set by using the `TracyCZoneText(ctx, txt, size)`, `TracyCZoneValue(ctx, value)` and `TracyCZoneName(ctx, txt, size)` macros. Make sure you are following the zone stack rules, as described in section [3.4.2](#multizone)! +Zone text and name may be set by using the `TracyCZoneText(ctx, txt, size)`, `TracyCZoneValue(ctx, value)` and `TracyCZoneName(ctx, txt, size)` macros. For printf-style formatting, use the `TracyCZoneTextF(ctx, fmt, ...)` and `TracyCZoneNameF(ctx, fmt, ...)` variants, which accept a format string and arguments instead of a fixed-length text buffer. Make sure you are following the zone stack rules, as described in section [3.4.2](#multizone)! #### Zone context data structure {#zonectx}