<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Make possibly use a current value from "Input list" field as variable value" href="https://bugs.documentfoundation.org/show_bug.cgi?id=130198#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Make possibly use a current value from "Input list" field as variable value" href="https://bugs.documentfoundation.org/show_bug.cgi?id=130198">bug 130198</a> from <a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> Mike Kaganski</a> <pre>(In reply to Regina Henschel from <a href="show_bug.cgi?id=130198#c4">comment #4</a>) > To be clear, my proposal it not to allow a reference as value of a variable. > That would be complicated in regard to file format. My proposal it to allow > a reference to a drop-down field in a condition. I suppose that doing that way would be not really good: it would introduce yet other special case to the complexity, without giving full flexibility. Could adding some "extension" attribute to the drop-down list markup, which would optionally bind it to a variable, be possible? Which could get to a following revision of the standard. That could allow other uses of the drop-down, like in following "show variable", e.g. in header/footer area. Or maybe adding another field type would be better, like current two similar "Input Field"s, one on Variables tab, the other on Functions tab, and the former being bound to Variable - this would be more consistent with regard to status quo IMO, because making a field on Functions bound to Variable is not correct... and binding it to variables unconditionally would break compatibility.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>