Changes in v2.3 build 134 1) Fixed bug in selection of default device during plug/unplug operations, amended dynamic content reload in Activboard Prefpane, Device Allocation, AS3/AP3 2) Improved Activote VR Server (in part of HTTP communications), updated Activote VR Web Client Activboard Prefpane: HTTP port option + according hint message were enabled 3) Activboard Prefpane's Activhardware tab: "Reset" button has been added (visible only if "Enable logging to Console" is ON, enable only if attached device is selected, it sends ":CS99" command to hardware) "Remote Command" control group is also enabled if attached device is selected (User can send commands directly on selected device) 4) Fixed coordinate input for Mac OS X 10.5 (9A559). 5) Activboard Prefpane: added check for maximum number of devices that can be registered (activotes and activslates) 6) Added workaround to fix firmware bug ("OK" response on ":GI" command) 7) Sends ":VE" command as a finalize command when removing multiple voting devices (not after each ":RDxxx" command like it was before), so, if we want to delete 2 of 3 registered devices, old: ":RD[device1 ID]" + ":VE", ":RD[device2 ID]" + ":VE". now: ":RD[device1 ID]", ":RD[device2 ID]", ":VE" 8) After sending ":VE" driver waits for OK reply from hub before sending another command, fixed synchronization of registered device set between Activstudio/Activprimary and Activboard Prefpane 9) Added post of ":CS00" command just after ":CS06" (remove all activote devices), updated activote vr command filter for ":VE" and ":CSxx" commands (these commands are sending in another way now, so I modified filter to generate notifications from driver to Activote VR server), updated appearance of Activote VR Web client (button size are adjusted for iPod) 10) Added coordinate packet filter to command response processing so now some vital for driver startup commands are getting correct responses even pen is in board proximity region 11) Fixed bug in USB coordinate packet filter. Change in v2.3 build 121 Improved Activote VR support. Change in v2.3 build 110 Improved French localization. Changes in v2.3 build 109 1) Disabled pressure support 2) Added French and British localization 3) Enabled "Set To All" for activote device renaming Changes in v2.3 build 108 1) Improved Activhub 2.4 GHz detection (up to 5 times faster) 2) Amended work with MK II (firmware v2.57) under USB connection 3) 2.57 firmware has support for activotes and doesn't have support for activslates 4) Fixed bug with Activote VR server under Intel 5) Activote device test fixed Changes in v2.3 build 107 1) Removed loggers for activboard coordinate input under all connections 2) Fixed bug in driver API - when only activote vr devices are used for voting, device enumeration function returned incorrect error code 3) Fixed bug in activote response packet parser under RS232 connection ( activote device ID ) Changes in v2.3 build 105 1) Added Activote VR support v2.0: 2) Works with Windows and Mac Activote VR clients 3) Prefpane has "Setup…" button on Activote tab to change Activote VR settings such as service name, port, activation code 4) Works with MKII, MKIII and 2.4 GHz electronics 5) Amended API which provides ACTIVote SDK support (function _GetActivCount returns amount of attached devices) 6) Enabled Promethean correction algorithm for coordinate input preprocessing 7) Added validators for PIN and number input 8) Activote tab layout changed Changes in v2.3 build 100 Bug fixes: 1) Fixed start up crashes in ACTIVhardware.app which is responsible for communication between Promethean hardware and host. 2) ACTIVboard.prefPane - amended switch between tabs. Before it was possible to see wrong layout did not corresponded to assigned device. 3)Unique device ID for Promethean USB hardware are now generated from USB port where electronics is attached and from firmware version. So now old hub and new one attached to the same USB port will be considered by driver as different devices. 4) Calibration was amended. Changes in functionality: 1) There is a new button "Activote VR Settings" on ACTIVote tab which shows settings window. 2) At this moment only "Start"/"Stop" button works. 3) Also there is a new button "Reset Device Cach" which remove information from driver about All inactive devices and set "Defaults" device options for Activboard, Activslate, Activote. Changes in v2.3 build 98 Changes in functionality: 1) This version of driver supports 3 types of electronics - ACTIVboard/ACTIVhub (MKII, MKIII) and ACTIVhub 2.4 GHz. 2) Driver has a new architecture to communicate with more than one device at the same time. 3) Pressure not supported Changes in v2.3 build 91 Changes in functionality: Activboard and activhub can now both work normally at the same time. There is a new option to select which device should process activslate. Changes in v2.3 build 90 Changes in functionality: Coordinate input events generated by ACTIVboard driver are similar to those generated by Wacom tablets which now allows to comfortably use board/slate with PhotoShop in regards to pressure ACTIVboard prefpane now gives posibility for user to setup pens in the "Pen Options…" Changes in v2.3 build 89 Bugs fixed: There is a problem under RS232 connection: It looks like BOARD sends trash packets when pen moves across the board. I have set the same parser as we use under Bluetooth connection in this build. ACTIVboard.prefPane now has edit field to send command to BOARD. It becomes active when "Enable logging to Console" checkbox is checked. Changes in functionality: Start-up and work under Serial connections for MKII and MKIII hardware. Changes in v2.3 build 86 Bugs fixed: Ian wrote: After sending :VV command firmware will not reply to :Q3 command immediately - need to wait about 1 sec for a response Now driver checks self-test result before sending ":VV" command to know if activpod is attached. Previously, driver sent ":Q3" only if it didn't get response on ":VV" command. Changes in functionality: Start-up under USB and Serial connections for MKII hardware. Changes in v2.3 build 84 Bugs fixed: Activboard 48 not replying to the :VV command when no pod is attached. Changes in functionality: Start-up under USB and Serial connections for MKII hardware. Changes in v2.3 build 83 Bugs fixed: • Fixed startup under Bluetooth connection. VT command didn't send. So Board ID, Channel, frequency were unavailable Changes in v2.3 build 82 Bugs fixed: Changes in functionality: Changes have influence only on MK II boards (firmware v2.xx) without voting support (their processors don't support voting). Firmware v2.87 doesn't check processor model when is being asked for activote support and always tells us that such support exists, but doesn't send feedback about activpod version, frequency range, board id, channel id. And so driver startup is failed. Driver startup consists of the following steps: • Ask firmware version (by sending Q1 command) • Ask hardware compatibility (by sending Q9 command)response o contains information about voting support • If voting is supported: o Ask activpod version (by sending VV command) o Ask frequency range, board id, channel id (by sending VT command) • Ask board dimensions (by sending BG command) • Ask hardware type (by sending Q0 command) • Ask self test result (by sending Q3 command) New driver startup consists of the following steps: • Ask firmware version (by sending Q1 command) • Ask hardware compatibility (by sending Q9 command)response o contains information about voting support • If voting is supported: o Ask activpod version (by sending VV command) ? If feedback is absent and firmware has version 2.xx -> ask activpod version again ? Repeat previous step 5 times and if feedback is absent then disable voting support and skip the next step o Ask frequency range, board id, channel id (by sending VT command) • Ask board dimensions (by sending BG command) • Ask hardware type (by sending Q0 command) • Ask self test result (by sending Q3 command) Changes in v2.3 build 81 Bugs fixed: Crash on ACTIVboard.prefpane quit Changes in v2.3 build 79 Bugs fixed: • Serial and Bluetooth connection are amended (parser of data from slate and activboard was broken) • Calibration was broken Changes in functionality: There are set of important changes in this release: • ACTIVsupport background application: o tablet/mouse event creation; o starts on user login, sets ACTIVboard calibration, launches ACTIVote VR Server; o stores information about currently selected ACTIVboard prefpane tab, country region, barrel button and context menu settings; o pref file you can find at /Library/Preferences/com.prometheanworld.activsupport.plist. • ACTIVote VR Server: o doesn't have network connections with ACTIVstudio apps (ACTIVstudio, ACTIVprimary, Device Allocation, ACTIVboard.prefpane); o communicates via network only with ACTIVote VR apps; o put responses from ACTIVote VR clients directly to driver data input queue. • IOACTIV.kext: o client notification scheme is now based on kernel message notification system instead of custom thread synchronization; o each client (app which communicates with driver) has 4 queues (for pointer (from slate and board) events, for slate events, for board events, for activote responses). Special Notes: Pay special attention for mouse event generation (normal, right click). Calibration (which starts via click on "Globe" and from ACTIVboard.prefpane) utility disables mouse pointer event generation on start and enables on quit. ACTIVboard.prefpane doesn't switch to the corresponding tab when is opening from ACTIVstudio/ACTIVprimary. Changes in v2.3 build 76 Fixed bugs: -No difference between states of "Enable logging to console " checkbox. Fixed for BT and RS232 connections. -Register slate button is enabled and does nothing when ACTIVboard is deactivated Changes in v2.3 build 73 1) ACTIVslate activation/deactivation (increased delay between commands it gives MK II ACTIVboard chance to process all commands which are in the input buffer one by one without restart); 2) Detect of USB plug/unplug (Driver uses now deferred device probing approach before we occupied device just after it was attached to the computer); 3) Activate/Deactivate of USB device. Changes in v2.3 build 71 1) crash of Activboard.prefpane when device label contains special symbols 2) crash when new bluetooth Activboard name contains more than 200 symbols 3) fix for the problem with keyspan driver on Mac Intel Changes in v2.3 build 58 1) Universal Binary - works on both Mac Intel and Mac PowerPc 2) Improved behaviour when plugging/unplugging Activboard via USB 3) Calibration now appears on the main screen (i.e. one with the menu bar) when using multiple monitors. 4) Support for driver auto-starting when connecting board via Serial or Bluetooth