On Fri, Feb 8, 2013 at 4:37 PM, K. Fossil user < [email protected]> wrote:
> 1/ I agree with the 20-200, but my idea is this : > I would like to know which button I've pressed: 200 or 20 ? (it doesn't > matter if n=100) > That assumes that the C code knows exactly which menu entries exist on the client, and it doesn't know that with certainty. As a user i can install JavaScript which adds more options (10, 100, 437, ...). The C code also has no way of knowing whether someone clicks on the menu or typed in a value themselves. 2/ The timeline variant is strange, because I've thought that if I click > the FIRST trunk then it should say 200... not 101... > But maybe, the number of lines are 200 but the trunk IS only 101 ? > If it is the case, I like it... However, it seems not. > I don't know... > i unfortunately can't give a clear answer on that one. i've browsed through the timeline code to try to clarify it, but the timeline is surprisingly complicated due to the large number of options and combinations. (In the JSON bits, the timeline code is notably larger than another of the other JSON APIs, even though it is missing some of the newer options from the HTML timeline.) -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
