I don't agree though. If I have MeasureName=#CURRENTSECTION# on the measure, then anything I input will stay there until I either click in the input field again, or refresh the skin. Nothing in code can "set" or "unset" the value of a measure.
I get what you mean now. Hmm... not even [!CommandMeasure ... "cleartext"] clears it, not to mention setting it to something else. The command measure should work, as for setting it to something else, there are other measures that do the same and retain their value unless getting data "as they're supposed to get" again, e.g. WebParser, no? By the way, can you set the value of an InputText measure without actually typing into it?With this search skin, I want to have the field say "Everything" get the user input, use that in the search, then immediately set the field back to "Everything".
Like I said, as long as it is not mandatory, I'm fine with it. I will never use it personally.
I don't disagree with you, all I'm wondering is whether it's a behavior that other similar measures have, that's all.
Statistics: Posted by Yincognito — 36 minutes ago