1 <!DOCTYPE HTML PUBLIC
"-//W3C//DTD HTML 4.01 Transitional//EN""http://www.w3.org/TR/html4/loose.dtd">
5 >The dynamic part of a module : the viewer
</TITLE
8 CONTENT=
"Modular DocBook HTML Stylesheet Version 1.79"><LINK
10 TITLE=
"Linux Trace Toolkit Viewer Developer Guide"
11 HREF=
"index.html"><LINK
13 TITLE=
"Linux Trace Toolkit Viewer Graphical Module Tutorial"
16 TITLE=
"The static part of a module"
19 TITLE=
"How to request background computation"
20 HREF=
"x81.html"></HEAD
31 SUMMARY=
"Header navigation table"
40 >Linux Trace Toolkit Viewer Developer Guide
</TH
56 >Chapter
3. Linux Trace Toolkit Viewer Graphical Module Tutorial
</TD
77 >3.3. The dynamic part of a module : the viewer
</A
80 > The dynamic part starts with the constructor of the viewer. It is called by the
81 main window when the corresponding button or menu item is selected. See
82 h_guicontrolflow() from control flow viewer eventhooks.c for an example. It does
83 basic connexion to the tab's events available : time window change notification,
84 current time notification, redraw notification, continue notification. All these
85 function should be implemented in your viewer if you want the data you shown to
86 be synchronised with the main window and the other viewers. It also calls the
87 background computation, which will be discussed in the next section.
90 > This is also at this point that the viewer does create it's own memory footprint
91 : its inner structure. This structure will have to be passed as hook_data to
92 each function registered by the viewer : this is what makes the functions
93 "belong" to this instance of the viewer.
101 SUMMARY=
"Footer navigation table"
140 >The static part of a module
</TD
154 >How to request background computation
</TD