On 9/1/05, Sean <[EMAIL PROTECTED]> wrote:
> > BTW, did you sometimes notice lines you can't click at all?
> > An example is the red line on the most left side of the graph
> > by SHA 66129f88c4cc719591f687e5c8c764fe9d3e437a.
> For what it's worth, everything near that SHA1 works here as expected.
On Thu, September 1, 2005 4:10 pm, Alex Riesen said:
> That's a fine feature :)
>
> BTW, did you sometimes notice lines you can't click at all?
> An example is the red line on the most left side of the graph
> by SHA 66129f88c4cc719591f687e5c8c764fe9d3e437a.
> It goes from blue up-arrow through g
On 8/30/05, Paul Mackerras <[EMAIL PROTECTED]> wrote:
>
> Try now... :)
>
> It also makes the current graph line thicker now, so it's easier to
> pick out where the line you clicked on goes.
>
That's a fine feature :)
BTW, did you sometimes notice lines you can't click at all?
An example is th
Paul Mackerras <[EMAIL PROTECTED]> writes:
> It also makes the current graph line thicker now, so it's easier to
> pick out where the line you clicked on goes.
Very nice, and quite helpful for colour challenged ones.
Thanks.
-
To unsubscribe from this list: send the line "unsubscribe git" in
th
Junio C Hamano writes:
> The new output looks a lot less cluttering and I like it very
> much, but it is confusing to me on one count. I clicked one
> arrowhead pointing downward, expecting that the pane would jump
> scroll to show the counterpart arrowhead, and was dissapointed
> that it did not
Paul Mackerras <[EMAIL PROTECTED]> writes:
> OK, you're the second person to ask for that, so I'll see what I can
> do about it. I can think of 3 possible behaviors when you click on
> the arrowhead:
>
> 1. scroll to bring the other arrowhead on-screen and briefly make it
>larger or something
Hi, Sean wrote:
> The line flowing from this commit extends ~200 more commits downward
> before it is finally terminated with an arrowhead. It would be nice if
> this line could be made shorter, such that the arrowhead was drawn much
> closer to commit in question.
Good point. The arrowheads te
Hi, Paul Mackerras wrote:
> http://ozlabs.org/~paulus/gitk/gitk.hs
>
Unfortunately, this fails on my git-plus-assorted-crap archive:
can't read "mainlinearrow(c1a9ddb1e9f30029384bd687d90af5796a280283)": no such
element in array
can't read "mainlinearrow(c1a9ddb1e9f30029384bd687d90af5796a280283)
Junio C Hamano writes:
> The new output looks a lot less cluttering and I like it very
> much, but it is confusing to me on one count. I clicked one
> arrowhead pointing downward, expecting that the pane would jump
> scroll to show the counterpart arrowhead, and was dissapointed
OK, you're the s
On Wed, August 17, 2005 2:58 am, Junio C Hamano said:
> Paul Mackerras <[EMAIL PROTECTED]> writes:
>
>> My reasoning is that it is the local short-range connections which are
>> interesting and informative. The long-range connections aren't really
>> visually informative; if you want to know about
Paul Mackerras <[EMAIL PROTECTED]> writes:
> My reasoning is that it is the local short-range connections which are
> interesting and informative. The long-range connections aren't really
> visually informative; if you want to know about the long-range
> connections, the parent and child lists in
On Wed, 17 Aug 2005, Paul Mackerras wrote:
>
> I would like to get some feedback about what people think of the
> visual effect of this new approach, and in particular whether having
> the lines jump into hyperspace loses information that people find
> useful.
Me likee. Maybe some knob to tune
I have been trying a new approach to drawing the commit graph in gitk.
This involves sending a lot of the really long lines into
"hyperspace", by terminating them with an arrow pointing down when the
graph gets too wide, and then reintroducing them later with an arrow
pointing up, as though they ha
13 matches
Mail list logo
