manual/html/functions.html in taskjuggler-3.6.0 vs manual/html/functions.html in taskjuggler-3.7.1

- old
+ new

@@ -1,7 +1,7 @@ <!DOCTYPE html> -<!-- This file has been generated by tj3man v3.6.0 --> +<!-- This file has been generated by tj3man v3.7.1 --> <html lang="en" xml:lang="en"> <head> <title>functions</title> <meta content="text/html; charset=utf-8" http-equiv="Content-Type"/> <meta content="IE=9" http-equiv="X-UA-Compatible"/> @@ -38,13 +38,13 @@ </colgroup> <tr align="left"> <td class="tag">Purpose</td> <td class="descr" colspan="2"><div> <p>The following functions are supported in logical expressions. These functions are evaluated in logical conditions such as hidetask or rollupresource. For the evaluation, implicit and explicit parameters are used.</p> - <p>All functions may operate on the current property and the scope property. The scope property is the enclosing property in reports with nested properties. Imagine e. g a task report with nested resources. When the function is called for a task line, the task is the property and we don't have a scope property. When the function is called for a resource line, the resource is the property and the enclosing task is the scope property.</p> - <p>These number of arguments that are passed in brackets to the function depends on the specific function. See the reference for details on each function.</p> - <p>All functions can be suffixed with an underscore character. In that case, the function is operating on the scope property as if it were the property. The original property is ignored in that case. In our task report example from above, calling a function with an appended dash would mean that a task line would be evaluated for the enclosing resource.</p> + <p>All functions may operate on the current property and the scope property. The scope property is the enclosing property in reports with nested properties. Imagine e. g. a task report with nested resources. When the function is called for a task line, the task is the property and we don't have a scope property. When the function is called for a resource line, the resource is the property and the enclosing task is the scope property.</p> + <p>The number of arguments that are passed in brackets to the function depends on the specific function. See the reference for details on each function.</p> + <p>All functions can be suffixed with an underscore character. In that case, the function is operating on the scope property as if it were the property. The original property is ignored in that case. In our task report example from above, calling a function with an appended underscore would mean that a task line would be evaluated for the enclosing resource.</p> <p>In the example below you can see how this can be used. To generate a task report that lists all assigned leaf resources for leaf task lines only we use the expression</p> <div codesection="1"><pre codesection="1">hideresource ~(isleaf() &amp; isleaf_()) </pre></div> <p>The tilde in front of the bracketed expression means not that expression. In other words: show resources that are leaf resources and show them for leaf tasks only. The regular form isleaf() (without the appended underscore) operates on the resource. The isleaf_() variant operates on the enclosing task.</p> </div></td> @@ -73,8 +73,8 @@ <td style="text-align:center; width:30%;"><a href="toc.html">Table Of Contents</a></td> <td style="text-align:right; width:35%;">&gt;&gt; <a href="gapduration.html">gapduration</a> &gt;&gt;</td> </tr></table> <hr/> <br/> - <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div> + <div align="center" style="font-size:10px;">Copyright (c) 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016, 2017, 2018, 2019, 2020 by Chris Schlaeger &lt;cs@taskjuggler.org&gt;.<a href="http://www.taskjuggler.org">TaskJuggler</a> is a trademark of Chris Schlaeger.</div> </body> </html>