Danny wrote:...
99999 would be 99MB. Far less than a lot of movie files.
Currently you can enter "9999999999999" which should be sufficient for most cases. (Personally I think that this limit is not so good since there are no thousand separators. Also for "No limit" another way might be found, see below).
Danny wrote:Have you actually tried clearing the field? Next time you open the program there's a "0" in there....
Currently, we have an Alpha version, so things may not work 100% properly. This is why we discuss here.
Danny wrote:And what sense does it make to disallow any filesize this way? That's the same as disabling the preview function. But you can do that via "View" menu and you'll get more free window space on top of that -> far more usefull. So anyone expecting different hasn't put enough thought into it.
Exactly. As written above the value "0" is not clear and for this reason it should not be allowed. This is why I suggested an error message when entering "0". In the error message there could be even a short explanation which values are valid.
A second way to make this clearer is by replacing "0" and the maximum value "9999999999999" with something more meaningful when leaving the field. E.g. the field could be cleared (empty), or a value "No limit", "Any", or "*" could be shown.
A third way is introducing a checkbox which enables/disables each limit (what we have in 1.80). But I think this would be confusing since we have many checkboxes on this category page, already.
A fourth way is dropdownlists: The dropdownlists could contain a value for "No limit" and meaningful, predefined limits. E.g.,
No limit
1 GB
100 MB
10 MB
1 MB
100KB
10 Kb
When choosing one of the predefined limits, the appropriate value in kilobytes would be entered in the field. Sure enough, apart from predefined values the user could enter arbitrary values.
Dreamer wrote:And as Dreamer already mentioned: most other programs (all that i know) work that way. 0 means disabled. (Azureus for example)
Hmm, that's an argument, but I don't think that this is a known and good standard. I guess in the programs you are refering to it says "Do not show files larger than". In this case, a "0" for all files makes sense and is logical since all files are larger than 0 KBytes. But in our case it says "Show files smaller than".
Personally I favour the "dropdownlists" approach. I think this would be clear regarding the value "No limit". And the predefined values also make things clearer and are convenient to use.