diff options
author | Bartosz Taudul <wolf.pld@gmail.com> | 2018-06-22 01:16:53 +0300 |
---|---|---|
committer | Bartosz Taudul <wolf.pld@gmail.com> | 2018-06-22 01:16:53 +0300 |
commit | ed40a3d9899da9760f77ab543804cde4e5aaa18e (patch) | |
tree | d5082bef59fe65c505ca533867ea92ac5c7c6723 /README.md | |
parent | 63611403ff735ee6afa0c59baf66a469a6e0277b (diff) |
Discourage embedding server into client application.
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -57,7 +57,7 @@ The easiest way to get going is to build the standalone server, available in the If you prefer to inspect the data only after a trace has been performed, you may use the command line utility in the `capture` directory. It will save a data dump that may be later opened in the graphical viewer application. -Alternatively, you may want to embed the server in your application, the same which is running the client part of tracy. Doing so requires that you also include the `server` and `imgui` directories. Include the `tracy/server/TracyView.hpp` header file, create an instance of the `tracy::View` class and call its `Draw()` method every frame. Unfortunately, there's also the hard part - you need to integrate the imgui library into the innards of your program. How to do so is outside the scope of this document. +Alternatively, you may want to embed the server in your application, the same which is running the client part of tracy. #### Marking zones |