devnul
05-21-2002, 01:21 PM
not that this is a huge deal, but i guess it could be if you use one huge filter file
instead of parsing the filter file once and sorting out the filters into appropriate bins it scans the file once for eace category and tosses out the ones it is not currently looking for
seems like the way to do it is to pass the array of filter pointers (m_filters) and then toss them into the appropriate filter as it scans in one pass
ie
static changeFiltersFromFile(Filter *[], const QString&)
which scans the file once and puts the entry in the filter whose m_type == stype
is this very important? no.. but as long as it works this way it's an argument in favor of using zone specific filters
dn
instead of parsing the filter file once and sorting out the filters into appropriate bins it scans the file once for eace category and tosses out the ones it is not currently looking for
seems like the way to do it is to pass the array of filter pointers (m_filters) and then toss them into the appropriate filter as it scans in one pass
ie
static changeFiltersFromFile(Filter *[], const QString&)
which scans the file once and puts the entry in the filter whose m_type == stype
is this very important? no.. but as long as it works this way it's an argument in favor of using zone specific filters
dn