[ quesa-Bugs-902988 ] Add view statistics API

[SourceForge.net <no...@so...>]

Bugs item #902988, was opened at 2004-02-23 21:10
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442052&aid=902988&group_id=45158

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Dair Grant (grantd)
Assigned to: Nobody/Anonymous (nobody)
Summary: Add view statistics API

Initial Comment:
It would be useful to have an API for gathering statistics about a 
view, so that Quesa could maintain statistics about current 
performance. Sort of info which could be gathered includes number 
of objects culled due to visibility, number of TriMeshes which hit 
the fast path (or slow path) through the renderer, number of 
objects submitted per frame, number of submit loops performed, 
min/max/average FPS, etc.

Interface would probably be something like:

TQ3Status Q3View_ResetStatistics(TQ3ViewObject theView);
TQ3Status Q3View_GetStatistics(TQ3ViewObject theView, 
TQ3ViewStatistics *theStatistics);

Note that there's no enable/disable API, as this information would 
be collected continually (it's really just a bunch of counters that get 
incremented, so no overhead), but an app could reset+get over 
whatever time period they wanted (once per frame, over 5 
minutes, over the lifetime of their app).

The TQ3ViewStatistics structure would need to be extensible for 
the future: either with a size/version tag as the first field, or with 
enough space for say 100 TQ3Uns32 counters (probably a mixture 
of both: include a version/size for the long term, and reserve say 
30 fields for easy expansion).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=442052&aid=902988&group_id=45158