Bryce Harrington wrote:
I think what would be even cooler is to implement an Extension Editor dialog, that provides a GUI view of the extension db, that shows each extension and its status, along with error messages, info about where to get the extension, etc. This way, the error info is easily available for users curious about it, but safely hidden from those who don't.
Perhaps a first start could be to create a function that iterates through the extension db and generates a string that summarizes the status of each extension, and then just put that into a text box in a dialog. That shouldn't be too hard to implement, and while it'd be ugly, it would be enough to be able to eliminate the error dialog on startup.
Great idea, Bryce.
Which is probably why I'm in the middle of coding that up today. :-)