On Sunday 2007 June 03, Marco Costalba wrote: > Care has been taken to allow the wheel browsing experience to be as > natural as possible, in particular a way to avoid to switch when user > just wants to scroll has been implemented. Also, getting a responsive > scroll and switch command avoiding false positives was not immediate. I'm really sorry to say it Marco, but it's really disturbing. You've obviously made great efforts to make it useable, but it just isn't. The scroll wheel behaviour being inconsistent is just annoying. Sometimes scrolling works, sometimes it doesn't, sometimes it switches content, sometimes it doesn't. It's obviously based on timeouts for the different functions, but that just means that I have no idea what a particular operation will do at any given time. I'm not sure I like the labels with arrows either; and the fonts changing size and visibility is inconsistent and discomfiting. On the plus side - I do like the idea of being able to perform these operations; jumping from revision to revision, or from log to patch is nice. However, I think it is unwise to invent a new graphical metaphor for an operation that already exists - the tabbed widget. Similarly, the up and down are obvious candidates for toolbar buttons - an already established visual. So - I think that the non-standard methods should be dropped (sorry); and be replaced with tabs for the patch/log switch and toolbar buttons for the up/down. Also, the scroll-to-switch, while an interesting idea, gives unpredictable behaviour and so is uncomfortable to use. Sorry for being so negative; it's a shame after your obvious hard work. Andy -- Dr Andy Parkins, M Eng (hons), MIET andyparkins@xxxxxxxxx - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
