Hi Alex,
In order to determine the correct number of pages, you would need to count the records in the view. The RECORDS statement won't help because of the effect of the filter on the browse.
To count the number of records is an "expensive" operation, in terms of time, but of course you are welcome to do it if you like. If you knew this number, and the current place of the data the user was browsing, you could very easily implement the feature you're thinking of.
On the other hand, I'm not sure that this is a particularly good way to navigate the data - a good locator is much better at actually getting to the data you want to find.
Cheers
Bruce