Hi Nicklas,
That's excellent -- well spotted. That has sorted the problem. If I
specify the entire header row it no longer picks up unsuitable configs.
What had happened was that I did try initially to specify whole header
rows but the file parse test kept on failing so I just went on to
specify
Thanks for the quick fix. I found another one closely related. In one of my
BASE1 plugins I had used empty string as the default value for a parameter
of type integer. Wise or not, this was allowed in BASE1. In BASE2 this gives
an exception when the empty string was tried parsed as an integer.
Th
