by Mizery_Made » Sat Jan 01, 2011 8:03 pm
MDominik13 wrote:If that's the case, the buttons (Cancel and OK) should be disabled once the process starts.
They are/should be? Are they not for you?
MDominik13 wrote:however, if the process is being run in individual steps (i.e. rebuilding indexes one at a time vs. one giant script), it should be possible to cancel the process.
If the process is compartmentalized and can safely be aborted (in a similar manner to when you cancel a tagging option in that it finishes what it's doing for that specific task, then breaks the chain before moving to the next one), then I don't see why not. I'm not database expert though, so... yeah. If it is ran in parts, it might be nice if MM displayed a progress bar, displaying at what stage it's at "Cleaning up _____", etc. so that it at least appears MM is doing something and not just locked up (may also help identify when/if it actually is locked up during a Maintain Library).
[quote="MDominik13"]If that's the case, the buttons (Cancel and OK) should be disabled once the process starts.[/quote]
They are/should be? Are they not for you?
[quote="MDominik13"]however, if the process is being run in individual steps (i.e. rebuilding indexes one at a time vs. one giant script), it should be possible to cancel the process.[/quote]
If the process is compartmentalized and can safely be aborted (in a similar manner to when you cancel a tagging option in that it finishes what it's doing for that specific task, then breaks the chain before moving to the next one), then I don't see why not. I'm not database expert though, so... yeah. If it is ran in parts, it might be nice if MM displayed a progress bar, displaying at what stage it's at "Cleaning up _____", etc. so that it at least appears MM is doing something and not just locked up (may also help identify when/if it actually is locked up during a Maintain Library).