Mercurial > dive4elements > river
comparison artifacts/doc/datacage.txt @ 6082:806fa23dffb3
Add some debugging tips
| author | Andre Heinecke <aheinecke@intevation.de> |
|---|---|
| date | Fri, 24 May 2013 09:22:39 +0200 |
| parents | 5aa05a7a34b7 |
| children |
comparison
equal
deleted
inserted
replaced
| 6081:cdd9759b15b6 | 6082:806fa23dffb3 |
|---|---|
| 143 </dc:macro> | 143 </dc:macro> |
| 144 | 144 |
| 145 and invoked from another location within the document, e.g. with | 145 and invoked from another location within the document, e.g. with |
| 146 | 146 |
| 147 <dc:call-macro name="basedata_4_heightmarks"/> | 147 <dc:call-macro name="basedata_4_heightmarks"/> |
| 148 . | 148 |
| 149 Debugging Tips: | |
| 150 - You can send a message to the Log (log level info) during the evaluation | |
| 151 of the datacage by using the <dc:message> element. | |
| 152 For example to activate a basic macro tracing you could do something like: | |
| 153 %s@\(<dc:macro name="\)\(.*\)\(".*>\)@\1\2\3\r<dc:message>\2</dc:message> | |
| 154 - To dump the variables that are currently on the stack you can use the | |
| 155 dc:dump-variables() fuction. | |
| 156 For example: | |
| 157 <dc:message>{dc:dump-variables()}</dc:message> |