On 11/14/2010 09:02 PM, J. Wesley Cleveland wrote: Hi,
On Sun, Nov 14, 2010 at 11:17 AM, Joost 't Hart <joost.t.h...@planet.nl <mailto:joost.t.h...@planet.nl>> wrote:On 11/14/2010 12:10 AM, J. Wesley Cleveland wrote: Hi,Date: Fri, 12 Nov 2010 20:06:26 +0100 From: Joost 't Hart <joost.t.h...@planet.nl <mailto:joost.t.h...@planet.nl>> Subject: [Scid-users] Games request To: scid-users@lists.sourceforge.net <mailto:scid-users@lists.sourceforge.net> Message-ID: <4cdd9032.30...@planet.nl <mailto:4cdd9032.30...@planet.nl>> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Hi, Rounding up a re-implementation of the annotation feature. What are you doing to the annotation feature? I was thinking of adding reverse annotation and also making it a menu option rather than just hidden in the annotation window.I am in the process of making it much better. Actually, most of the work is already done and I am releasing it bit by bit after pretty rigorous testing. This testing takes a lot of time, due to the (too!) many options that are there. Once I am done, making the anlysis work backwards should be an almost straightforward operation. I think only the autoplay machinery should be changed and the comparison logic in addAnnotation should be reversed. For now I suggest you wait until I am done, as you will need to resolve many stability issues along the way. Cheers, Joost. Some things I was thinking of changing that might be easy for you.1. Update the time at the top on every message received from the engine (perhaps after the first few seconds) rather than only on a new pv. This would make it easier to guess when the next iteration will finish.
Could be done, but I am not sure I like this, as the top line is designed to indicate the status as per the most recent pv. Are you aware that the Info button (4th from the right end) shows a second line at the top with some actual data? Especially the move progress indicator "Current: e4 (1/20)" on the left may be what you are looking for.
2. Add the time to the end of the PVs in multipv mode, like in single PV mode.
Will do.
3. Capture the output from stderr also. Stockfish writes to stderr on an error exit, but the message vanishes because there is no console window.
Hm, I like what you say but this could mean quite some work, as Scid is used to parse the stuff coming from the engine. So we would need to add the notion that something that cannot be understood should be sent in raw format to the engine window?
As to the implementation: Currently we open the engine's standard output as "| <engine binary>"
Should this be replaced by something like "| <engine binary> 2&>1"?I am not the expert in this respect, but I guess that this might not work in windows...?
Cheers, Joost.
------------------------------------------------------------------------------ Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev
_______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
