Thank you Peter and everybody else for their input. I think I am going to create a replacement for my use of FrmCustomAlert and a keyboard replacement function. Can anyone offer me tips or a starting point for either of these two routines?
FrmCustomAlert Replacement: Today I use a generic alert box with an OK button and ^1 ^2 ^3 in it. Then I just fill in my text. Sometimes I use another alert with yes and no buttons. I'd like to make a generic form that will serve most of my needs. I would setup one function as the entry point to bring up the form and accept parameters to specify the strings and buttons to display. My options to display a form are FrmGotoForm, FrmPopupForm, and FrmDoDialog. Which should I use and how do you know what the user tapped to close the box (which button)? FrmDoDialog is easy, but I can't catch events using FrmDoDialog, can I? And, what is the easiest way to handle the variable text without adding full blown scrolling functionality? Keyboard Replacement: I have some other reasons to do this. Someone must have done this before and I was hoping to find a source for this code somewhere. Any tips would be appreciated. Thanks again to everyone for their input. I am a bit frustrated because the MSR library uses this event technique to signal that a card was swiped, yet there are two problems: 1) it is not full-proof and you can miss an event very easily, and 2) there seems to be a bug in the MSR library causing fatal errors when you do miss the events. Thanks again. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
