Very nice! 

A suggestion: Might be worth adding a section for 'Known OS Bugs and
Issues' broken down by OS version. Just a thought because I've wasted
plenty of debug time chasing stuff that turned out to be broken in the
OS and this will no doubt drive new developers nuts. Damn, wish I'd kept
a list now. Things that immediately spring to mind are:

1) WinDrawBitmap doesn't support 4bpp gray scale properly until OS 3.3
(even if your device does).
2) SysBinarySearch is broken until about 3.3 as well (unless you set the
findFirst parameter to true)
3) Odd launcher and UI event behaviours in older OS versions.

My 2c as always.

Stuart Nicholson
Programmer
Firepad Inc.

-----Original Message-----
From: Adam Wozniak [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 11, 2000 11:37 AM
To: Palm Developer Forum
Subject: FAQ (was Re: To beginner programmers (was Re: This is not
fair))



[EMAIL PROTECTED] wrote:
>
> Sounds like someone just volunteered...
>

Here is a start.  Comments are welcome.

===

PalmFAQ.txt
Version 0.0
07-AUG-2000

This is the Palm Dev Forum Frequently Asked Questions List,
posted monthly to the palm-dev-forum mailing list.

Questions / comments / criticisms can be sent to
[EMAIL PROTECTED]

This document is maintained as a flat text file for widest
accessability.

==== Section 0: Questions about this list ====

Q0.1 Where is this list archived?

A0.1 Archives are incredibly useful sources of information.  If you have
a
     question, it is a good idea to search the archives first before
posting.
     Most of the time the problem you're staring at blankly has been
stared
     at blankly by others, and is somewhere in the archives.  Archives
are
     maintained at the following locations:

     http://www.escribe.com/findgroup.html?query=palm
     http://www.egroups.com/list/palm-dev-forum/info.html

Q0.2 What other sources of information exist?

A0.2 There are several resources on the web which can help you.

     Palm's "Getting Started" web page
        http://www.palmos.com/dev/started/

     Wade's Pilot Programming FAQ
        http://www.wademan.com/Pilot/Program/FAQ.htm

     The Palm Developer Knowledge Base
        http://oasis.palm.com/dev/kb/

==== Section 1: Questions about Development Environments ====

Q1.1 What development environments and toolchains exist?

A1.1 Many. http://www.palmos.com/dev/tech/tools/ contains a
comprehensive
     list.

Q1.2 What does the CodeWarrior error "The registry key 'BDWM' cannot be
found"
     mean?

A1.2 There was a problem with connecting to the emulator or device for
     debugging.  This can have many causes.  Fortunately, Metrowerks
     has fixed many of these problems so you don't see this error very
     often any more.  See http://oasis.palm.com/dev/kb/faq/1790.cfm

Q1.3 I've just downloaded the Palm emulator POSE.  Where do I get a ROM
image?

A1.3 The quickest way is to download them from a real device using the
     RomTransfer.prc that came with POSE.  You can get other ROM images
by
     registering as a developer at http://www.palmos.com/dev/program/
     and then going to the ROM Image Clickwrap area of the Provider
Pavilion.

==== Section 2: Questions about C / C++ ====

Q2.1 How do I declare a variable?  How do I make a string?  What's a
pointer? 

A2.1 The palm-dev-forum is not the best place to ask generic questions
     about the C or C++ programming languages.  There are plenty of good
     sources of information.  I recommend the following:

     Books:

     "The C Programming Language"
        Brian W. Kernighan and Dennis M Ritchie
     "The C++ Programming Language"
        Bjarne Stroustrup

     Online:

     Introductory C course by Steve Summit
        http://www.eskimo.com/~scs/cclass/cclass.html
     Comp.lang.c USENET FAQ
        http://www.eskimo.com/~scs/C-faq/top.html
     Comp.lang.c newsgroup
        news:comp.lang.c

     
==== Section 3: Questions about the PalmOS API ====

Q3.1 What does the error value 5647 mean?

A3.1 Error values are two byte values.  The most significant byte tells
     you what class the error came from.  The least significant byte
     tells you the specific error in that class.  Working through this
     example:

     first convert 5647 to the hex value 0x160F
     look for the corresponding class entry 0x1600 in ErrorBase.h
     note that this is the fileErrorClass
     find the header file which uses that error class
        (FileStream.h in this case)
     Convert the least significant byte 0x0F back to decimal 15
     Look for the error in the error list of that header file.  It
should
        look something like this:
        #define fileErrIOError   (fileErrorClass | 15)


-- 
For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/tech/support/forums/

-- 
For information on using the Palm Developer Forums, or to unsubscribe, please see 
http://www.palmos.com/dev/tech/support/forums/

Reply via email to