benini / scid

Other
43 stars 12 forks source link

gamebrowser with variants, comments and popupboards #99

Closed ukscid closed 1 year ago

ukscid commented 1 year ago

first version of modified gamebrowser. s. feature request https://sourceforge.net/p/scid/feature-requests/88/ new functions: show comments, show variants, enable/disable this show evalbar, materialbar, enable/disable this 2 buttons for resize board (workaround for keys) show popupboard on right mouse click this includes the ability to flip the popupboard like the browser board and a function for convert FEN to board ( this should be better implemented in cpp)

benini commented 1 year ago

Uwe, I don't understand. I keep asking you to create small pull requests, and you keep creating ones with hundres of changed lines. There are many guidelines on the internet, let's just pick stockfish's one: https://github.com/glinscott/fishtest/wiki/Creating-my-first-test In particular points #2 and #4.

I don't think you appreciate how this will help you too. Just the first line is so wrong:

But if you made a pull request just for that: "add a flip parameter to ::board::popup". It would be clear that you just wanted to add a {flip false} parameter.

The same applies to the single line change in ::board::material. When you try to describe what you are doing, you'll notice that you are changing a dynamic fen, which is updated when the function is called, with a static fen which is changed who knows when. That's huge. There is now an implicit requirement that $::board::_data is always updated before ::board::popup is invoked. It not only takes a lot of time to test that, but what about future changes? How should one know/remember this implicit requirement? But if you made a pull request just for that: "Let ::board::material accept the FEN as a parameter", it would be clear that all the above pain is not necessary.