3 # Generate node tree from verbose logfile
8 # First of all, you need to recompile modules slideshow and canvas
9 # with VERBOSE=t set in the environment, and debug=t defined at the
10 # build tool command line. Then run your slideshow and redirect stdout
13 # Then, call 'nodetree.sh trace-file > tree.ps' to generate a
14 # PostScript file for the AnimationNode tree generated during the show.
15 # Since these easily get pretty huge, use only one page, and try to
16 # limit the slide content (which have effects assigned, that is) to
17 # the bare minimum (to reproduce your bug, or whatever you need this
20 # The generated output will have all nodes color-coded with their state
21 # at the point when the tree was dumped (see colors.sh for the color
24 # When looking for the mechanics that generate the relevant output,
25 # grep for the DEBUG_NODES_SHOWTREE macros in the slideshow source:
26 # Each such place dumps the current node tree to the trace output. Thus,
27 # if you need to check the tree state at other places or times, just add
28 # a DEBUG_NODES_SHOWTREE
31 ###################################################
35 ###################################################
37 grep -E "Node connection|Node state" $1 | \
38 sed -e '/Node state/ s/.*Node state.*: \(.*\)/\1/' \
39 -e '/Node connection/ s/.*Node connection.*: \(n.*\)/\1/' | \
41 awk 'BEGIN { print "digraph Event_network {" }; { print } END { print "}" }' | \
44 # fill a complete A1 page with graph output
45 dot
-Gratio=fill
-Gsize=23,33 -Tps
46 #dot -Gratio=fill -Gorientation=land -Tps