Not particularly interested in this since I don't use the plugin on a constant basis, but working a bit with FileView, I thought it would be both easy to implement internally (e.g. based on the value of Type=FileName child measures or otherwise) and useful for skin designers to have a Type=FileExists option in a FileView child measure. That would avoid having to use IfMatches (which unnecessarily adds to the skin verbosity or complexity), the size of the extracted icon (which might or might not be used) for each child measure, or a bunch of variables, in order to detect which of the associated meters should be hidden or not.
Type=FileSize would have been otherwise suited for such a check since it returns numeric values which can be used in the Hidden option of meters via conditionals, except that 0 byte files can exist. Type=FileCount would have been another candidate, except that it isn't related in any way to the IndexUp / IndexDown command bangs. The rest are string based values that lead us back to the IfMatches and separate variables or !SetOptions to set the Hidden option on the associated meters (which might or might not have a similar name with the FileView child measures, another slight inconvenience in practice).
On a second thought, since the numeric value of the Type=FileName child measure is not used at the moment anyway, an even more compact approach to this would be to have it indicate file existence via some 0 or 1 values, which could then be used via the : section variable parameter in the Hidden option of associated meters. I imagine neither approach would affect backward compatibility, by the way.
Type=FileSize would have been otherwise suited for such a check since it returns numeric values which can be used in the Hidden option of meters via conditionals, except that 0 byte files can exist. Type=FileCount would have been another candidate, except that it isn't related in any way to the IndexUp / IndexDown command bangs. The rest are string based values that lead us back to the IfMatches and separate variables or !SetOptions to set the Hidden option on the associated meters (which might or might not have a similar name with the FileView child measures, another slight inconvenience in practice).
On a second thought, since the numeric value of the Type=FileName child measure is not used at the moment anyway, an even more compact approach to this would be to have it indicate file existence via some 0 or 1 values, which could then be used via the : section variable parameter in the Hidden option of associated meters. I imagine neither approach would affect backward compatibility, by the way.
Statistics: Posted by Yincognito — Yesterday, 9:33 am — Replies 0 — Views 268