Hi, I fear you can’t extend the board size beyond the size of the original texture. Or it starts to look distorted, (it looks a little distorted when it’s smaller then that size as well, but usable) You can try scaling the texture to the size your screen supports. I wonder if we can use a SVG board instead?
Regards, Josh On Sep 15, 2014, at 6:18 PM, Sebastian Pipping <[email protected]> wrote: > Hello! > > > On my journey trying to get a natural-looking Xiangqi mode running with > XBoard (rather than WinBoard), I ran into problems with rendering. > > My call to xboard was > > xboard \ > -variant xiangqi \ > \ > -liteBackTextureFile ${D}/themes/textures/xqboard.png \ > -darkBackTextureFile ${D}/themes/textures/xqboard.png \ > -overrideLineGap 0 \ > \ > -pieceImageDirectory ${D}/themes/xiangqi \ > -trueColors true > > > Now when XBoard starts up this looks sane. > > When I maximize the window to full screen, the boards starts to look > very weird, see [1]. > > I started inspecting BlankSquare and CutOutSquare in draw.c. In > CutOutSquare there are guards > > if(textureW[kind] < W*squareSize) > > and > > if(textureH[kind] < H*squareSize) . > > Is my understanding correct that these are meant to detect if the > provided texture files are expected to be (a) a single field or (b) a > full board? If so we might need a new config parameter to tell XBoard > from the outside for once, instead. > > What do you think? > > Best, > > > > Sebastian > > > > [1] http://share.pho.to/7AF1Z/8g/original >
