Re: [Bug-gnubg] Maximum move string

[Joseph Heled]

I would still love an option to have all on the same line.
If you cut on the spaces for move number, abbriviate the ply, and use
W+G-OG  (i.e 62.7+28.1-14.7 for wins wins gammons lose gammons), it
should fit nicely in one line.

What do you think?

-Joseph


On 8/31/05, Jonathan Kinsey <address@hidden> wrote:
> 
> >From: Jim Segrave <address@hidden>
> >Reply-To: address@hidden
> >To: Jon Kinsey <address@hidden>
> >CC: address@hidden
> >Subject: Re: [Bug-gnubg] Maximum move string
> >Date: Wed, 31 Aug 2005 10:01:03 +0200
> >
> >On Wed 31 Aug 2005 (07:25 +0100), Jon Kinsey wrote:
> > > Jim Segrave wrote:
> > > >
> > > > One question - when you unclick Details to suppress the w/g/bg stats,
> > > > they are replaced by a blank line. Is there any way to make the
> > > > display single line so that you get twice as many moves listed when
> > > > you don't want the details?
> > > >
> > >
> > > I'm not sure what you mean here's a screen shot with/without details and
> > > it does show about twice as many moves in singe lines:
> > >
> > > http://homepage.ntlworld.com/jon_kinsey/bg/list5.png
> > > http://homepage.ntlworld.com/jon_kinsey/bg/list6.png
> >
> >Here's a capture of this window with and without details. With
> >details, there are 5 moves showing and 11 lines of text. Turning off
> >details, there are 8 moves showing. There should be 11, maybe 12, as
> >there are no spacer lines.
> 
> This is as expected.  There are 2 reasons, firstly the no-details view has a
> header, secondly the detail view has 2 text lines quite close to each other
> (or to put it another way it has one seperator per 2 lines).  I don't think
> the number of moves displayed has decreased compared to older versions?
> 
> One idea is to use the new control for both views, then the move would be
> bold for both.  I'm not sure it's too important.  I like the simple/detailed
> views.
> 
> Jon
> 
> 
> 
> 
> _______________________________________________
> Bug-gnubg mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/bug-gnubg
>