xboard-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [XBoard-devel] XBoard 4.7.3: Full board textures + maximize window


From: Joshua Pettus
Subject: Re: [XBoard-devel] XBoard 4.7.3: Full board textures + maximize window
Date: Tue, 16 Sep 2014 17:08:53 -0400

Hi,

I don’t know. I think you are overstating it a bit.  I have a 1680x1050 monitor 
on my laptop.  I just took the image, loaded it in gimp, scaled it 175% and it 
works mostly fine.  The only issue is on the diagonals as the squares tend to 
overlap it on the corner for most resolutions, save the resolution of the 
image.  But on the straights it’s fine.

Regards,
Josh



On Sep 16, 2014, at 4:23 PM, Sebastian Pipping <address@hidden> wrote:

> Hello again,
> 
> 
> we're starting to run in circles.
> 
> I didn't say I'm against scaling: I'm concerned about
> scaling-and-cutting for certain types of textures.  It might be just
> fine, for western chess and single-field wood/marble textures, nothing
> against that at all.
> 
> I just tried using a 1800x2000 Xiangqi board image as a texture for a
> fullscreen window on a 1920x1080 display.  The result looks anything but
> sane, so enlarging the board image does not seem to solve the rendering
> problem.  Since you put so much of your energy into Xiangqi support with
> *Board, I'm rather surprised that playing Xiangqi in fullscreen with a
> Chinese board (like most people would) is not supported.
> 
> Giving users new smart options (what you proposed) rather than an option
> to control directly, what they really want to change, is the wrong road
> if you ask me.  With the amount of options in *Board as of today, I
> don't see how adding one more would make any real difference.
> 
> 
> So to me all this sounds like (1) you'd be happy to support infinitely
> large boards made from enlarge-and-cut marble/wood single-field textures
> and (2) you consider Xiangqi and fullscreen display corner cases.
> While (1) is cool, status quo on Western chess doesn't to really /need/
> patching now.  I came here for (2), which does need patching.
> 
> Best,
> 
> 
> 
> Sebastian
> 
> 




reply via email to

[Prev in Thread] Current Thread [Next in Thread]