Hi, cyclops. Thanks for taking a look and all the feedback! Just a few responses ...
1. Yes, a clipboard format that could paste across sessions would be interesting. A lot of what I implemented while learning WPF was what I use when reviewing games, or as you said somewhere, little things I've wanted
. I only cut/paste within a single game, but I hear you on the comment.3. Only undo is going back a move and creating a branching move. You can then cut the move you did not like. If you paste immediately after cutting, it is effectively and undo. But, yes, you are right that a very clear undo button would be nice.
5. I repair misplaced stones by going back, making the move I want, cutting the part I like from the old branch, pasting it where it should after the new move, then deleting the dangling move (if any).
6. I have discussed the general design off on and on with folks, and I think the basic architecture is fine in terms of layers, an MVVC, etc., but yeah, substantial new functionality may require some more isolation and restructuring of abstractions or factoring of code into more files/classes. Also, the code review will shine a light on many cleanups
.9. Yeah, I don't handle ko yet for disallowing moves, which I should document in the notes.txt file. This is something I should add soon to be more useful as just a go board
.10. I like the idea of the primitive scoring functionality and will add a note about that.
11. I created a "Just a Build" v0.7 release on the downloads page to just get a .zip of the executable since a couple of people asked about that.
12. Yeah, I lack several adornments. My excuse is I worried about those I see in 99% of games I edit today and review, but I'm short of the full sgf spec. I document some in the code, but I will update the notes.txt file with a more clear list of what's missing, which can serve as a punch list of things to get to
.Thanks again!
Bill
