What I did: 1. Launch POSE and POSE-Profile. 2. configure both so their 'serial port' is 'localhost:6000' 3. in each, open the find panel and enter 'shortcut . . s' using grafitti 4. go to the launcher in POSE, select beam, pick an application and attempt to beam it.
what i hoped for was POSE-Profile starting a receive and a beam taking place. what i got was POSE timing out the beam and saying it couldn't find any receivers. My applciation is using the low level IR api (IrBind, etc) to create a connection. I haven't figured out getting that to go in POSE either, though i know that it works to create a connection between a V and m505. Questions: should both emulators be set to have the same 'serial port' (eg. localhost:6000) or should they be different? eg. localhost:6000 and lcoalhost:6010 is there any way to verify that shortcut S has taken effect? what terminal application did you use to test? - that way i can test with it also. In article <87254@palm-dev-forum>, Keith Rollin <[EMAIL PROTECTED]> wrote: > At 7:29 AM -0700 5/25/02, Simeon Leifer wrote: > >I'm developing on Mac OS X and would like to be able to test some > >two way IR code using POSE. (I'm using version 3.5) Ideally i'd like > >to be able to run two copies of POSE (right now i've got normal and > >profiling and can run them simultaneously) and have their 'serial > >ports' connected, using shortcut-s to route the IR over serial. > > > >All POSE want to let me do for a 'serial port' is assign a TCP/IP port. > > > >Can what I want, or something close enough, be done? what piece of > >the puzzle am i missing? > > I'm not sure what you think is missing. You just described > everything you need! What steps are you taking, and what results are > you getting? > > It's been a while since I've tried this, but when I first added the > option to route serial over TCP, I was able to run Poser twice, run > terminal programs in both, type in one of them, and have the output > appear in the other. So I know it used to work! > > At least the serial part used to work; I haven't tried beaming. > There may be issues there, because part of the beaming process > appears to involve breaking the connection and re-establishing it. > This re-establishment occurs pretty much simultaneously on both > "devices", which can cause a collision in the TCP stack, resulting in > both "devices" changing from connect mode into listen mode. With > both "devices" in listen mode, they'll never re-connect to each other. > > -- Keith Rollin > -- Palm OS Emulator engineer > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
