> From: Dave Lippincott > > Don't pass NULL in your alert, use " " (quotes with a space or nothing). > That's partially correct, Dave. If your custom alert contains ^1 ^2 and ^3, you have to pass in a string containing at least 1 blank for each unused replaceable parameter (^2 and ^3). However, if your alert only contains ^1, you have to pass in NULL for the omitted parameters (^2 and ^3). Don't pass in a string for any omitted parameters, and don't pass in NULL for any parameter that is used in your alert. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
- Strange behavior with static arrays in CW7 David Leland
- Re: Strange behavior with static arrays in CW7 Jeff Collins
- RE: Strange behavior with static arrays in CW7 Richard Burmeister
- Re: Strange behavior with static arrays in CW7 David Leland
- Re: Strange behavior with static arrays in CW7 David Leland
- Re: Strange behavior with static arrays in CW7 Steve Mann
- Re: Strange behavior with static arrays in CW7 Richard M. Hartman
- Re: Strange behavior with static arrays in CW7 David Leland
- RE: Strange behavior with static arrays in CW7 Richard Burmeister
- Re: Strange behavior with static arrays in CW7 Dave Lippincott
- Re: Strange behavior with static arrays in CW7 Richard Burmeister
- Re: Strange behavior with static arrays in CW7 David Leland
- Re: Strange behavior with static arrays in CW7 David Leland
- Re: Strange behavior with static arrays in CW7 David Leland
- Re: Strange behavior with static arrays in CW7 Keith Rollin
- Re: Strange behavior with static arrays in CW7 Ben Combee
- Re: Strange behavior with static arrays in CW7 David Leland
- Re: Strange behavior with static arrays in CW7 David Leland
- Re: Strange behavior with static arrays in CW7 Craig Torell
- Re: Strange behavior with static arrays in CW7 Marshall Clow
- RE: Strange behavior with static arrays in CW7 Richard Burmeister
