Community
Participate
Working Groups
20040423 The indexer process can take quite a while and I suspeced it several times to slow down my system. I had to do a ctrl+break to see that the indexer really was doing something. Instead of ctrl+break, the indexer should show that it is doing something in the progress view. It dooesn't have to be ported to the core Jobs infrastructure, but just create a 'dummy' (system-) Job and push the progress message to its progress monitor. Note that more feedback also helps with debugging problems, e.g. if the indexer would get stalled, ect...
Interesting suggestion. A system job could do the trick, being non cancellable. Should investigate for M9
Downgrading. This is feature work which will be deferred post 3.0.
Post 3.0
Actually, intriguing if couldn't be done still.
Added system job that reports progress when the indexer is running. The job terminates when there is no progress to report any longer.
Verified in 200405180816 that a system job can be seen in the progress view when set in verbose mode.
*** Bug 42761 has been marked as a duplicate of this bug. ***