On Wed, Sep 9, 2009 at 9:50 AM, Yuki KODAMA<endflow....@gmail.com> wrote: > On Wed, Sep 9, 2009 at 18:22, Adrian Buehlmann<adr...@cadifra.com> wrote: >> 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? > > Yep, it is in my TODO list. I know that mostly users will open "command log" > window when the operation failed. > My idea for this: when the error occurred, > * the icon of log button will change to error mark > * the last line of error message will show in progress bar (if possible) > ** -> I hope it's in red color and bold > * the error message will show with tooltip of progress bar (or log button) > ** -> you can check error message with just hovering to progress bar > >> Or could the unapply and apply buttons be disabled if there >> are local changes? >> >> Or write a "+" character behind the name of the >> top applied patch, if there are local changes. > > I'll do this idea. It's also in my TODO. > >> 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.
repo.status() can be expensive, as we often re-discover. So this will have to be taken into account. > I don't want to add more widget into MQWidget since I need > to allocate the space for patch list. > And we have the area of CmdWidget. It can be used as status bar. > >> 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? The changelog tool will be able to launch the commit tool from the launch menu.. sometime soon. > Umm... needs more thought. > You may know, actual MQWidget is embedded into only changelog viewer, > but I have a plan that embedding MQWidget into commit tool. > If MQWidget has 'qrefresh' button and I embed it to commit tool, > they will conflict with each others. > > Thus, my ideals are: > * MQWidget is not dialog, just *widget* > * MQWidget has minimal UI: patch list, move buttons > * MQWidget has all functionality related MQ extension > (it will be provide as public functions) > > I suppose "Minimal UI" are current MQWidget. > So "qrefresh" and "qnew" features will provide as public functions. > Of course, we can add these commands to context menu. > >> (don't get me wrong, the new MQWidget is just great!) > > Don't worry, I believe you always give helpful ideas :) > Thanks for a lot idea & comment, Adrian! Yep, keep them ideas coming. -- Steve Borho ------------------------------------------------------------------------------ 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
