The easiest way to make the indexing more palatable is to add some form of status update while indexing is taking place. Any multi-step action that has the potential to run more than 30 to 45 seconds should report something to the user as it processes. It is unreasonable to have a process that can last a minute or more and not report any indication of progress to the user.
Matthijs, you mentioned that on boot there are two indexing steps
Quote:
|
Originally Posted by Matthijs
The indexing has two steps:
1) Find all files and folders on the card and sync that structure with global.db
2) For each newly added file, open it and get thumbnail & metadata
|
For step one you could first just get the total number of directories that need to be scanned. Before step 2 begins you could setup a progress bar on the screen that you update every 20 seconds with the progress made as a percentage of the directories that the indexing scan as completed, the current directory being scanned, and the total time the index scan has been running.
The issue with the indexing would not be so bad if we had some idea of how much time was remaining until the end of the index scan. Updating the progress bar and current directory of the scan gives people an idea of how long they will have to wait. This makes the wait seem shorter as the user is not sitting there waiting and wondering when it is going to finish loading.
Ride