Description Mathieu Velten 2011-08-18 04:11:04 EDT

The biggest problem was performance : compute a search on a big model takes a lot of time, so do it for each key typed does not really work with big models.

What I did :
- change the dialog by replacing the ok button with a "Launch search"
- add a cancelable monitor during search
- make the dialog non-modal so we can access the properties view for example without leaving the search dialog

There is still something that I don't really know which option is the best :
currently when hitting next the current selection in the model explorer is retrieved and the next element in the search results is calculated from there.
it can be weird with a non modal dialog since we can change the selection (if it doesn't find the current selection in the search results it go back to the beginning).

I suggest to just use an integer to store the current search index.

I am commiting this so you can see my work and comment.