|
» Subscribe » Favorite Links » What is S60? » Freeware & Trials » S60 devices » Hints and tips » About this blog |
» Blognotes (15) » Bugs and Workarounds (4) » Build tools (5) » Carbide.c++ 1.1 (4) » Carbide.c++ 1.2 (8) » Carbide.c++ 1.3.x (8) » Carbide.c++ 2.0.x (1) » Carbide Plug-Ins (4) » CodeWarrior (2) » FAQ (6) » Future directions (24) » General (46) » Off-topic (4) » On-device debugging (13) » Performance Investigator (2) » Product features (16) » Product releases (16) » Screencast (12) » Support (30) » Tool setup (5) » UI Designer (8) » Usability (15) » Work in Progress (13) » Write-build-debug (4) |
|
» Launching from the SPN View » Tips for using the CodeScanner tool! » Carbide in the summer » Austin Eclipse DemoCamp » Where's my console output? |
|
Subscribe to RSS feed For email notification, please click here ยป |
« Eclipse 3.4M7 | Main | S60 Build Performance: Don't Forget to Update Your Makefiles »
The feedback that we are getting from users when they try to debug with TRK over Bluetooth is rather unsatisfactory. One requirement is to have a serial port service over the Bluetooth is confusing, since by default it doesn't come with many Bluetooth enabled devices and users have to go to manufacturers sites to get it. The second one is to specify "Port" number on device to connect to. This is not really a port but rather service index on the host PC.
We decided to simplify at least this latest part. I am going to implement the class in TRK that would try to connect to a host PC and query which ports are available. Once serial port over the BT is discovered, TRK would automatically attempt to connect to it and inform the user of its success or failure. If we are able to connect to PC via BT, but no serial port over Bluetooth service is found, we will let the user know of this fact. At first we will let users to have the manual way of selecting Bluetooth 'port'. This is because we have no ability to make sure that will work over all possible Bluetooth radios. In the second stage, if we get positive feedback, automatic port selection will become the only choice. If you debug with TRK and have any concerns, now it is a good time to let us know!