Hmmm - it's interesting , but pretty raw and not something i'd use. But cheers.
I thought for a second you were making a patch to draw the engine arrows on the main board, which lots of GUIs do already. This is also something i'm not too especially keen on because we have arrows everywhere already! :) And it presents lots of unresolved issues. .... But, since i *do* already have a quick patch that does this, I thought to add it to svn (which i've done just now, and also attached below). To see the arrows, you''ll have to select "Show Arrows" in Tools->AnalysisEngines. Cheers, S.A. On Tue, Dec 3, 2024 at 7:22 AM C Hanish Menon <hanish...@gmail.com> wrote: > Hi Steve, > > I have tried adding support for simple visualising of the main pv > generated by uci engine on the analysis board. The user can control > how many moves ahead to show on the board, using a spinbox I have > added next to the show analysis board checkbox/button. > > I am attaching the patch with the email and a sample image of how it > appears. > > NOTE: I have patched the scid file directly. I am not a tcl/tk > programmer, I have looked at the code in scid and tried to > structure/implement the patch to get the job done. There is a small > probability that I may not be doing things the tcltk way. > > On Sat, Nov 30, 2024 at 6:58 PM C Hanish Menon <hanish...@gmail.com> > wrote: > > > > Hi Steve, > > > > Thanks for adapting and incorporating the patches. > > > > Regarding snap, I dont think I have currently set %F, it's been a long > > time, I normally start from the command line. However it is a good > > input, which can be useful for many, will update it. > > > > Previously in the snapcraft.yaml file, which I am also bundling with > > snap, I was fetching the latest svn commit and creating a snap of it, > > so that anyone attempting to create snap on their own can get the > > latest svn commit based version. But with the new version of snapcraft > > (used to create snap), they seem to have removed/goofed up the svn > > fetch logic, so I am using the tar file of the scidvspc release. Need > > to check, how to patch in svn fetching again wrt snapcraft may be by > > overriding its default fetch flow, so that people can create snap > > using the latest commit, if possible. > > > > Given that you would be familiar with sourceforge and its svn, by any > > chance, do you know, if there is a standard url one could try to fetch > > to get an archive / tar of the latest svn commit of a project hosted > > on sourceforge svn. > > > > On Sat, Nov 30, 2024 at 3:13 AM Steve A <stevena...@gmail.com> wrote: > > > > > > Thanks Hanish. I've adopted or tweaked all your changes and made a > commit. (I've given the analysis boards identical coord setup to the main > board, but making the font smaller). > > > https://sourceforge.net/p/scidvspc/code/3485/ > > > > > > P.S. Thanks for creating the snap package. I think i recently had some > correspondence about it. Do you include the %F arg (or similar) in your > scidvspc.desktop file (ie "Exec=scid %F"). This allows opening desired > files. > > > > > > Regards Steven. > > > > > > On Sat, Nov 30, 2024 at 2:12 AM C Hanish Menon <hanish...@gmail.com> > wrote: > > >> > > >> Hi, > > >> > > >> I follow and explore chess very very infrequently, like once in a few > > >> years, usually when maybe a chess championship is going on or hear > > >> something about a new chess engine or I am experimenting something or > > >> so. > > >> > > >> So also I am not good at visualizing text chess move lines/variations > > >> without having visual hint like coordinates on a chess board. > > >> > > >> Given that currently ScidVsPC doesnt have an option for the same wrt > > >> analysis board, have created this patch (03- patch file name) to > > >> enable the same. If the user enables coordinates on all sides wrt the > > >> main board (ie boardCoords value 2), then this logic will enable > > >> coordinates on the analysis board. > > >> > > >> Inturn when working on this, noticed that the board::flip logic wasn't > > >> setting the vertical (1-8) coordinate values correctly for the > > >> analysis board always, it seemed to have a race based on when the > > >> board gets enabled and when the user toggles board coords. So have > > >> created a additional patch (04- patch file name) which sets the labels > > >> based purely on flip variable. NOTE: Not able to reproduce this > > >> currently, dont remember the sequence of enabling different options > > >> and boards, but did notice it few times initially, when I was working > > >> with only 03- patch file. Also this 04- patch file makes the logic > > >> directly depend on flip variable rather than any value that may be > > >> already there wrt the labels. So feel this may be a better logic. > > >> > > >> > > >> NOTE: I had created & inturn maintain scidvspc-hkvc snap package, to > > >> run scidvspc on linux distros with snap package system support, which > > >> again I update once in a bluemoon. These patches are included in the > > >> version which I have released there. I have added the suffix -hkvc to > > >> ensure that in future if the scidvspc team wants to release their own > > >> snap package, there is no confusion. These patches can be > > >> tested/verified by running the scidvspc-hkvc snap package, if needed. > > >> > > >> -- > > >> Keep ;-) > > >> HanishKVC > > >> _______________________________________________ > > >> Scidvspc-users mailing list > > >> Scidvspc-users@lists.sourceforge.net > > >> https://lists.sourceforge.net/lists/listinfo/scidvspc-users > > > > > > > > -- > > Keep ;-) > > HanishKVC > > > > -- > Keep ;-) > HanishKVC >
engine_arrows_on_main_board.diff.gz
Description: application/gzip
_______________________________________________ Scidvspc-users mailing list Scidvspc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scidvspc-users
