Hi Daniel, thanks for your input!
On Wednesday 29 April 2009 10:47:32 Daniel Teske wrote: > > attached is a patch that adds a shortcut to move to the next Task in the > > TaskList (using F6 currently). > > I'm not a fan of adding a shortcut for next Build Issue. Some of the > reasons are: > > The next tasks is often not the next location you want to go. > That is the build issue lists often lists multiple locations per error. > E.g. listing the include chain, listing stuff that results from previous > errors or for template stuff, the definition of templates. Thats absolutely right. Though I'm more with Oswalds opinion here: My experience shows me, that in maybe 90 % of the the task the error is what I'm looking for. And I have cases where not the error itself but maybe something like "instantiated here" is the the point to focus on. But in such cases I still can use F6+Alt-1+Up/Down to get to the task of interest. On Friday I did a huge refactoring in our project replacing std::strings with QStrings. Unfortunately our logging facility does not like QStrings, so I had to use myString.toStdString() in those very cases. Every error had something like 6 lines of "?" before the error and about 20 lines of "?" after the error. Using the Alt-1+Up/Down technique would have meant to scroll for about 26 items from error to error. This is not really usable :-) > There is already a way to navigate the Build Issue list. pressing Alt+1, > Cursor keys and Enter. Which is two keystrokes more per task you want to > go, but doesn't leave files open you didn't even want to go to. As I said, it's not 2 more keystrokes per task, its 25 more per task in the above example. And I have another problem with this way: When typing with 10 fingers its almost equal for me to move my right hand to the arrow-keys as to move them to the mouse. So in general I prefer to use the mouse when I have to use the arrow-keys otherwise as it slows me down anyway. Though I don't want to miss the Alt-1+Up/Down feature as there are times where this is very useful, too :-). I'd call it the pragmatic approach. > Using the above shortcut mirrors how you can use the Search Result window, > that is Alt+2, Cursor Keys and Enter work exactly the same there. (And that > also works for application output and compile output.) > > So I rather let people find out about the common way to open and navigate > the output panes. Thats true, there should be a unique way to navigate those items. So a solution could be to use F6 as a 'move to next item' shortcut and which item is used (task, search, ...) depends on what is currently opened. I'd be Ok with a solution where I have to press Alt+1 and then F6 to navigate the tasks. > The next error stuff probably should still be available, quite possible on > the toolbar of the build issue output pane. What do you mean with "the next error stuff". take care, have fun /christian _______________________________________________ Qt-creator mailing list [email protected] http://lists.trolltech.com/mailman/listinfo/qt-creator
