X-Git-Url: http://winboard.nl/cgi-bin?a=blobdiff_plain;f=whats_new%2F4.6.0%2Findex.html;h=e85a0e52d32b73fa948798661bb45e33ca1284b1;hb=111cb5deba58e6ca98ca540bd1ccfcb6cce6a177;hp=3b0dcbcded7d29ab119dd849f67bf6c4a3464fa3;hpb=a88309b032a6a5158e2ec3b7f3d93030f88a48c9;p=xboard.git diff --git a/whats_new/4.6.0/index.html b/whats_new/4.6.0/index.html index 3b0dcbc..e85a0e5 100644 --- a/whats_new/4.6.0/index.html +++ b/whats_new/4.6.0/index.html @@ -26,6 +26,8 @@
-Experimental and future stuff -
- + + +
@@ -190,6 +199,12 @@ You release when you see the piece you want.
A plain right-click will start with a black Pawn,
pressing the Shift key with it will start with a white Pawn.
+The side to move, as indicated by the clock, +can be altered by clicking on the clock of the other side, +as is (and already was in previous versions) also the case when using the piece menu. +But in sweep-selection mode, clicking on the clock of the side that +already has the move ('highlighted' in black) will clear the board. + This manner of placing pieces is especially handy in variants, where you might need piece types that are not in the piece menu, which can only be obtained by promoting or demoting other pieces. @@ -221,7 +236,7 @@ through -fcp and -scp options on the command line when XBoard is started. (WinBoard at least had a startup dialog, where you could select engines through a combobox, displaying a list of engines configured in the settings file.) -This experimental patch allows you to change engines during a session, +This new feature allows you to change engines during a session, (or even during a game!), through a new menu dialog. @@ -301,7 +316,7 @@ You can both specify a number of games per pairing (which are played consecutive and a number of 'cycles', i.e. repeats of the entire pairing scheme after all pairings are played. When multiple instances of XBoard are working on the same tournament, you can make them wait for each other at the end of a round or cycle. -For a more elaborate description, look here. +For a more elaborate description, look here. |
-WinBoard now keeps track of which engines are used (as first engine at startup, or through the Load Engine dialog). +XBoard and WinBoard now keep track of which engines are used (as first engine at startup, or through the Load Engine dialog). This information is stored in the settings file as the string option -recentEngineList, -and next time you start WinBoard, this list will be displayed at the bottom of the Engine menu. +and next time you start XBoard, this list will be displayed at the bottom of the Engine menu. When you select one of these items, the corresponding engine will be loaded as first engine, exactly like you went to Load Engine, selected it from the combobox, and pressed OK.
@@ -657,7 +672,7 @@ or recaptures that leave the King in a check that already existed before the cap
-Structuring the list of installed engines+Structuring the list of installed engines (WB)The engine list (-firstChessProgramNames, for those used to editing the ini file) upto now has always been a large, unstructured pool of engines. @@ -688,7 +703,7 @@ I.e., you can make groups within groups.
Associating file types with icons and actions+
Dragging all windows as a unit++The option -stickyWindows, known from WinBoard, now also works in XBoard. +An checkbox in the General Options menu dialog was added to switch it on or off. +With this option, auxiliary windows (Game List, Engine Output, Move List and Eval Graph) which touch the main window +will move together with it when the latter is dragged over the screen. +Such 'docked' windows will also be repositioned and resized as needed +to preserve their tiling relationship with each other and the main window, +whenever the latter changes size because of a variant change. + ++Whether this feature works can depend on your system's window manager. +XBoard will order the repositioning of the windows as needed, +but this obviously can only have the desired effect if the window manager actually obeys such orders. +Some window managers don't, so it might be that this feature does not work at all, or causes erratic behavior. +The best solution in that case is to leave it switched off. + + |