A glimpse of the history of BT Control
changes for 3.5.1Beta (October 2003)
Postponed the integration of 3.4.2 with the XP1.0.0 version. Takes too much time right now, espescially the additional error handling in the XP1.0.0 to tackle Bluetooth errors requires more study. As many users requested support for the additional buttons on the T610/Z600 and T68, I decided to provide that in this release.
changes for 3.4.2 (December 2002)
XPbeta Changed the menu access in the phone now title 'BT control' instead of 'RemCntrl' (suggestion of a user). Modified definition/selection of COMport, it is now also possible to directly select a remote Bluetooth device. This direct device selection is only available when the operating system supports this (currently only Windows XP with service pack 1 and special patch).
changes for 3.4.0 final (September 2002)
Introduced MyMenus directory where your own modified definition files can be stored. This prevents them from disappearing when you uninstall BTcntrl, in the process of introducing a newer version ;-) The mouse control activity now also allows a keyboard command to be bound to phone button 5. When activating 'incoming call reject' while communication with phone is ongoing, the phone's silent mode is activated.
changes for 3.4.0beta5 (September 2002)
As indicated by a user, incoming calls were not blocked unless one was IN control mode (selected RemCntrl menu). An info window appears on the phone at the activation of BTcntrl communication. Help info adapted and also the info in the status bar.
changes for 3.4.0beta4 (September 2002)
Switched serial library again, the sudden input stop noted in 3.3 was still not solved as attempted in 3.4.0beta2. Should mention that I have also implemented IO time-out checking.
changes for 3.4.0beta3 (August 2002)
When btcntrl is stopped while a call is going on... the call is disconnected due to a 'clear menu' action of the tool which simulates the pressing of the 'NO' key. Removed this behaviour ;-(
changes for 3.4.0beta2 (August 2002)
Introduced possibility for mouse control, thanks to approach taken by Mikael Christersson with his tool (www.christersson.org). Introduced capability to handle display pixel settings larger then 100%. This helps people that use that setting. Funny that you have to handle things like that in your application... Switched serial interface handling library, the previous one sometimes stopped handling input :-(
changes for 3.3.0beta4 (June 2002)
Annoying these beta releases, anyway it seems I have a weird issue solved for the Toshiba stack. Sometimes the response to an AT-command only appears with an CR (carriage return) character. Most implementations also give a line feed. So I get (and expect) CR and LF. I have now changed the 'end of input event' to CR. I could make this a selectable setting hmmmmm
changes for 3.3.0beta1/2 (May 2002)
Replaced the startup delay of version 3.2.3 with a timed retry of AT commands. If a response is received within 5 seconds we continue, else we get warning info. Also introduced the possibility to disable the phone manufacturer check. If you want to try it on a non-Ericsson phone .... will not work though. Finally introduced PgUp and PgDn keys in the sendkeys field, try a mouse-rightclick there to see all.
changes for 3.2.4 (~March 2002)
Communication speed obviously differs between the various Bluetooth interface solution, as well as processing power on the machines this tool is executed. This could be the reason of big differences regarding the arrival of the phone-response string at the tool. Introduced extra checking on 'empty' (only CR-LF) strings. This could lead to misunderstanding between phone & tool.
changes for 3.2.3 (~March 2002)
Introduced 2 seconds delay after opening the COM-port. This makes it possible to use the automatic connection setup of TDK-cards. Further improvements in error handling.
changes for 3.2.2 (~February 2002)
Removed a small bug due to the storing, and especially loading of the defined COMport number (when the COMport was higher then COM7). Also disabled 'KeyLock control' as this caused problems on a T68. In general the function caused more trouble then it solved, so it is marked for removal.
changes for 3.2.1 (~February 2002)
On special request: the COMport range has been extended from Com7 to Com12. This prevents problems when you Bluetooth PCMCIA driver cannot seize one of the lower port numbers. NOTE: For T68 users I noticed that the the automatic 'keylock deactivation' seems to give problems. As soon as I can borrow a T68 again I will look into it, until then do not check this option in the tool's Edit menu entry.
changes for 3.2 (~February 2002)
Introduction of a phone-screen view which shows similar info as the phone. Useful to show an audience what is happening (on the phone). Provided two PowerPoint key definition files to tackle the difference in slide-screen activation for PP97 and PP2k. Introduced some additional features which can be activated by users with courage. See menu Edit.
changes 3.0 and 3.1 (December 2001)
This release of Bluetooth Control went through a major number of changes. While the basic capabilities were maintained (probably) all of them, and a few more, can now be accessed through full phone-menu-entry customization. Please check the helpinfo from the tool's menu. Also take a look at the provided menu-examples, to get familiar with the different capabilities. A previous installation of this tool can co-exist, but not in the same directory, this should help reducing the impact of all new capabilities ;-)
changes 2.0 (April 2001)
First release which can be distributed on a limited scale. Still rudimentary help info included.
changes 1.6 (November 2000)
Very basic functionality, fairly easy to change com-ports.
changes 0.9 (September 2000)
Managed to get the tool working via the Ericsson Bluetooth development kit. This proves that it actually possible to program something in Visual C++ (by me).
changes 0.5 (May 2000)
Mainly used to show off, based on the development kit of Digianswer and crafted on top of one of their Delphi examples.