SilverAzide wrote: ↑December 10th, 2020, 5:03 pm
IfMatch matches exactly (the way you have it written), so since "XYZ" isn't exactly "X", "Y", or "Z", then all the "not" matches will fire.
No, in fact exactly contrary: all IfMatches are true. If in the IfMatch option is posted a literally expression, it is true if the used expression is present into the checked string.
For instance:
As you can see the One, Two and Three variables are returning which IfMatch is true and which one is false. All are true in the above code. If you modify the Signs variable for instance to Signs=XAZ, One and Three are still true, but Two becomes false, because X and Z are still present into the expression, while Y isn't anymore.
balala wrote: ↑December 10th, 2020, 6:37 pm
No, in fact exactly contrary: all IfMatches are true. If in the IfMatch option is posted a literally expression, it is true if the used expression is present into the checked string.
Huh... I guess I misunderstood the manual examples. The manual implies the opposite (at least as I read it). So the example that illustrates matching, like: IfMatch=.*Green.*, would also return true if the expression was simply IfMatch=Green?
SilverAzide wrote: ↑December 10th, 2020, 10:37 pm
Huh... I guess I misunderstood the manual examples. The manual implies the opposite (at least as I read it). So the example that illustrates matching, like: IfMatch=.*Green.*, would also return true if the expression was simply IfMatch=Green?
Correct... The question being asked is "does the following exist in the string?"
SilverAcide you are right. i missed DynamicVariables and now it works well.
Balala wrong this time. It helped double refresh. One refresh did partial job. Double full job. With DV now it works with 1.
TX
nikko wrote: ↑December 18th, 2020, 6:17 pm
Balala wrong this time. It helped double refresh. One refresh did partial job. Double full job. With DV now it works with 1.
I still doubt, to be honest, because a refresh is a completely destructive procedure. The whole skin is rebuilt when you refresh it, all previous changes are lost, excepting what is written with !WriteKeyValue bangs. But you know.
However I still am curious. Could you please pack the config which contains the skin which has to be double refreshed and post the package here, along with a description on what to do, please?