Newton Developer Technical Information: Newton Programmer's Guide: 2.1 OS Addendum /

Chapter 9 - IrDA Communication Tool / Using the IrDA Tool

Slow IR Connect Option

A note about the last option in the previous example. Typically, one communications tool listens while the other connects. But, IrDA has the capability to connect if both devices are connecting (called symmetric connections here). Both connect and listen options must be specified for this to work and they both need to have and look for the same class names. After the connection is established, one of the two devices has (invisibly to the communications tool client) taken the role of the listener. The return value from the last option in the previous example lets you know if you are the connecter or the listener.

If the flag irActiveConnection is set in the returned connect field, then the communications tool has the role of active connecter. If this flag is not set, then the communications tool has the role of passive listener.

Note that the kCMOSlowIRConnect option is not documented in this chapter because it's already covered in the "Built-in Communications Tools" chapter of Newton Programmer's Reference, under the infrared communications tool.

Note

The pre-existing infrared communications tool required passing the kCMOSlowIRConnect option with irSymmetricConnect set in the connect field to request "symmetric connecting." But, the IrDA tool does not--the concept is part of IrDA. More importantly, don't confuse the pre-existing kCMOSlowIRConnect option and the new IrDA *kCMOIrDAConnectInformation option. They are two completely different things.