Andreas Linke wrote: >>IMHO, an OS API function should NEVER >> display any user interaction dialog. >>Do you remember any C library function that does a fprintf(stderr)? In those days, C was used mostly for back-end apps. There was enough disk space to afford logs and traces in response to error codes. The Palm environment is a different model. I can live with the ErrFatalDisplay. As for DmQueryRecord(), don't believe the docs! :-) So far, I've found that DmQueryRecord() returns a 0 if the record was deleted or the index out of bounds. It's DmGetRecord() that will ErrFatalDisplay. Michael Yam Y Technology, Inc. http://www.ytechnology.com [EMAIL PROTECTED]
- PalmOS improvements (was: C++ SDK wanted!) Andreas Linke
- Re: PalmOS improvements (was: C++ SDK wanted!) krollin
- Re: PalmOS improvements (was: C++ SDK wanted!) Michael Yam
- Re: PalmOS improvements (was: C++ SDK wanted!) Jason Dawes
- Re: PalmOS improvements (was: C++ SDK wanted!) David Fedor
- Re: PalmOS improvements (was: C++ SDK wanted!) Jason Dawes
- Re: PalmOS improvements (was: C++ SDK wanted!) David Fedor
- Re: PalmOS improvements (was: C++ SDK wanted!) Jason Dawes
- Re: PalmOS improvements (was: C++ SDK wanted!) B. Flaumenhaft
- Re: PalmOS improvements (was: C++ SDK wanted!) Chris Antos
- RE: PalmOS improvements (was: C++ SDK wanted!) Richard Hartman
- Re: PalmOS improvements (was: C++ SDK wanted!) Jason Dawes
- Re: PalmOS improvements (was: C++ SDK wanted!) Roger Chaplin
