From: D. M. M. <mic...@ro...> - 2008-04-07 00:02:53
|
On Sunday 06 April 2008, Philippe Macaire wrote: > If you don't like the symbol or the color I can try to design > something less "catchy" (I'm no good graphical designer -- it should > be obvious...). The color is good, and it's very handy having a visual indicator where the marker is. I don't know if you're thinking that already, but it seems like an obvious extension is to have more of these (1 through 0) each in a different color. The little flag is very blocky looking though, and it also draws on top of any numbers. I think I'd solve the blocky problem by doing away with the point, and just drawing a vertical line. (Unless there's an easy way to antialias the little point, maybe even if that means it has to wait until QT4 for that enhancement.) I think I'd solve the number conflict problem by drawing it in the dark gray area instead. I have no idea how hard that order is to fill. I should add that I'm rather impressed with this, even though I'm nitpicking it. I don't know if I could have made the ruler draw a little red flag or not. I've attached a little mockup. Since the flag seems to match up with a particular position of the blue cursor, I'd also make the tick mark the same width as the blue cursor. And in the interest of being practical, if it turns out that drawing the mark on the lower bit of the ruler is a huge bother, could you draw the mark so that it's underneath any numbers, and they take priority? I won't merge this into the stable branch yet, but I see no reason why it shouldn't get under the door before the release. Which reminds me, we have a "you implement it, you document it" rule around here. :) The string freeze doesn't really apply to the Handbook, and it's not too late to update it to reflect new or changed behavior. Good work anyway, Philippe. I was pretty ambivalent about this whole idea of yours until you gave it a visual marker. I can see using this now. It's handy! -- D. Michael McIntyre |