The error handling in the new MQWidget in the default branch seems not yet optimal.
If I have an applied patch + local changes and I hit the "Unapply last patch" button, mysterious things happen. On the bottom of the MQWidget appears something looking like an empty input filed with an "X" button on the right. Otherwise, I see no effect. And the patch is not unapplied (of course -- it can't, see below). Interestingly, if I click on the icon to the left of that mysterious input filed (the one looking like a small document), a window with the title "Command log" pops up, containing the text ''' abort: local changes found, refresh first [command interrupted] ''' Aha! So behind the scenes, this work reasonable. But the ui for this use case is far from ideal. Would it be possible to instead directly pop up that log window in response to the user doing "unapply last" in case of an error? Or could the unapply and apply buttons be disabled if there are local changes? Other idea: provide a small "status bar" at the bottom of the MQWidget and write there the text "local changes" if there are local changes. Or write a "+" character behind the name of the top applied patch, if there are local changes. Next question would be: do we want a "qrefresh" botton in MQWidget? Or should we add a button to get to the commit dialog instead? Quite a couple of questions... (don't get me wrong, the new MQWidget is just great!) ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Tortoisehg-develop mailing list Tortoisehg-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
