From 45afa26c0af277e61cd637b5997d5744df45a2fb Mon Sep 17 00:00:00 2001 From: =?utf8?q?Jos=C3=A9=20Fonseca?= Date: Fri, 9 Mar 2012 18:22:28 +0000 Subject: [PATCH 1/1] Document how to start the gui on a specific call. --- README.markdown | 16 ++++++++++++++-- 1 file changed, 14 insertions(+), 2 deletions(-) diff --git a/README.markdown b/README.markdown index f39ca19..d591136 100644 --- a/README.markdown +++ b/README.markdown @@ -12,8 +12,8 @@ About **apitrace** * visualize and edit trace files. -Basic usage -=========== +Obtaining **apitrace** +====================== To obtain apitrace either [download the latest binaries](https://github.com/apitrace/apitrace/downloads) for your platform if @@ -21,6 +21,10 @@ available, or follow the [build instructions](INSTALL.markdown) to build it yourself. On 64bits Linux and Windows platforms you'll need apitrace binaries that match the architecture (32bits or 64bits) of the application being traced. + +Basic usage +=========== + Run the application you want to trace as apitrace trace --api API /path/to/application [args...] @@ -48,10 +52,18 @@ Replay an OpenGL trace with Pass the `-sb` option to use a single buffered visual. Pass `--help` to glretrace for more options. + +Basic GUI usage +=============== + Start the GUI as qapitrace application.trace +You can also tell the GUI to go directly to a specific call + + qapitrace application.trace 12345 + Advanced command line usage =========================== -- 2.43.0