I DO call YieldCycles. But it NEVER works. Ever... How do I know? Well, it's simple....my conduit works perfect now. If I change one of my "workarounds" to YieldCycles, my conduit will not work and the device will time-out.
It's actually a very very simple test. And the reason I KNOW YieldCycles doesn't prevent the palm from timing out. OK, so it may allow the palm to process cancel messages. And it may be nice to have, but the second requirement doesn't work. Try the simple loop in my previous post. It wont work. I'll bet you a dollar. James Jim Cooper wrote: >James, > >>I was under the impression that YieldCycles was supposed to keep >>the link active between the palm device and the PC. >> > >That's not all it does. It also allows the HSM to update the progress >dialog, and to process cancel button messages. > >>Actually, you shouldn't need YieldCycles here >> > >I believe you do. > >>My problem <snip> comes into play when we have >>long periods (over 7 seconds) of NO DATA TRANSFER >> > >In which case you should arrange to call SyncYieldCycles during that >time. > >>If you used YieldCycles in a loop reading or writing records to/from the >>device, then I ask, why? Reading or Writing within 7 seconds keeps the >>connection alive. >> > >Depends where you're getting the records from. You're probably ok on the >Palm end, but it's possible you're doing something on the PC ennd that's >taking a while. > >>Step 2 here takes WAY WAY longer than 7 seconds. >> > >So periodically call SyncYieldCycles during that time. > >> YieldCycles(1000); >> > >If you read the docs for SyncYieldCycle it says that the parameter value >is ignored, and it treats it as 1. > >Cheers, >Jim Cooper > >_____________________________________________ > >Jim Cooper [EMAIL PROTECTED] >Tabdee Ltd http://www.tabdee.ltd.uk > >TurboSync - Writing Palm conduits with Delphi >_____________________________________________ > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
