FearCond - version_tracker.txt
----------------------------

Version numbers are stored in:

(1) .iss file (influences setup display, Control Panel)
(2) .rc file (About box)
(3) g_strVersion
(4) web site whatsnew.shtml

Version history:

1.0
1.1
- Majority of development done under this number!

2.0
- From point of introducing "default ODBC DSN" system, 15 Aug 2002.

- 22-Sep-2002 Integrated HTML Help

2.1
- Fixed horizontal scroll bar in list box
- About button

2.2 (22 Nov 2003)
- writes version number and compilation date to summary file

2.3 (8 March 2007)
- improved ease of user compilation

3.0 (12 Jan 2009)
- Server default changed from "loopback" to "localhost" (Windows Vista
  compatibility and more general standardization).

3.1 (24 Feb 2016)
- Recompiled (with necessary minor changes) for WhiskerClientLib v4.62,
  to stop this bug, as per my e-mail of 14 Apr 2015:
  
  The following have been updated, and I'd suggest using the updated versions.

    ConditionedReinforcement
    SeekTake
    SeekTakeShock
    SecondOrder
    MonkeyCantab -- also: RPI schedule added
    SimpleSchedules -- also: RPI schedule added
    AttMem
    WhiskerServer
    WhiskerSDK

  Apart from the addition of the RPI schedule, I have changed the network 
  socket code in WhiskerClientLib (now v4.62), with some corresponding changes 
  in the server just for code symmetry. I think this will fix an intermittent 
  bug in which tasks (and collectively you've told me about MonkeyCantab, 
  SeekTake, SeekTakeShock, ConditionedReinforcement, SecondOrder) don't start 
  properly and appear to sit there waiting for input and doing nothing. We had 
  been using the Microsoft CSocket class for some client-side network
  communications, and the consensus is that it's a bit duff, so I've reworked 
  it to make it safely re-entrant (I think that non-re-entrancy was the 
  problem). I didn't ever manage to make one of the tasks fail to start 
  (because the bug is intermittent), but I did get it to fail using my 
  NetThrashClient. That now works fine with some very heavy-duty network 
  testing, so I think the changes have worked.

  The problem is likely to apply to all clients using WhiskerClientLib prior to
  4.62, so I'll rebuild any others by me if anyone's having problems. Please
  pass on the message to anyone who might need to know. The software's 
  available in the usual place.

3.2 (24 Feb 2016)
- Recompiled again following bugfix in WhiskerClientLib (now v4.7)!