This is not a bug, more a improvement, hence I have not used the bug report template. I am using 4th Mar 2006 CVS.
When updating the movie database in the configuration dialog, the cancel button does not work effectively, and even when cancelled, the user interface does not restore itself.
The problem is that the updating of the database is running in the UI thread, instead of its own seperate thread. Hence, when the cancel button is pressed, it does not respond immediately. DoEvents is run occasionally during the process allowing the cancel command to be processed, but ideally, all the database update code should be moved into its own seperate thread. Also, when cancel is pressed, once the current operation is cancelled, the user interface should reset itself.
I don't use the movie database myself, so I don't want to touch the code as I don't know that part well enough.
Like I said, this 'bug' is really an improvement; something to take into consideration for future releases.
Sam
When updating the movie database in the configuration dialog, the cancel button does not work effectively, and even when cancelled, the user interface does not restore itself.
The problem is that the updating of the database is running in the UI thread, instead of its own seperate thread. Hence, when the cancel button is pressed, it does not respond immediately. DoEvents is run occasionally during the process allowing the cancel command to be processed, but ideally, all the database update code should be moved into its own seperate thread. Also, when cancel is pressed, once the current operation is cancelled, the user interface should reset itself.
I don't use the movie database myself, so I don't want to touch the code as I don't know that part well enough.
Like I said, this 'bug' is really an improvement; something to take into consideration for future releases.
Sam