You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The shortening feature is very useful, but I was wondering if it could be extended to handle other namespace delimiters, either on a per-trace basis or as a profiler setting.
This would mostly be useful for instances where Tracy is integrated with other languages, like Lua where the delimiter is ..
The text was updated successfully, but these errors were encountered:
Absolutely, here is a very simple trace: love2d_overusing_newImage.zip
It's from a proof of concept of adding Tracy instrumentation to the LÖVE engine. That engine mostly runs in Lua so it would make sense to show functions with their Lua names where they are "namespaced" into tables rather than the C++ namespaces.
In this case, it might make sense to add some code during engine startup to tell the Tracy server that for this trace, please consider . a namespace separator.
As I said, this is just a proof of concept, and there's really no rush. The actual developers of the engine haven't gotten back to me about how they feel about this integration. I mostly wanted to know your thoughts on it.
Relevant function:
tracy/profiler/src/profiler/TracyUtility.cpp
Line 19 in d1300c4
The shortening feature is very useful, but I was wondering if it could be extended to handle other namespace delimiters, either on a per-trace basis or as a profiler setting.
This would mostly be useful for instances where Tracy is integrated with other languages, like Lua where the delimiter is
.
.The text was updated successfully, but these errors were encountered: