> I also believe that some warnings are best "handled" by turning them off. > > The critical point is knowing when it's ok to turn the warning off and > when it's not. At the moment I don't have enough palm experience to > know when to ignore gremlin warnings and when not to (although it > appears that the insertion point warning may be one to be ignored).
i had to re-read what was written here, and, i have to admit - i was shocked to see what you had written. if you want to write high quality applications the prerequisites are: - use debug roms - turn on all warnings if your application successfully runs, then its approaching a state of high quality (approaching palm platinum certification approval level). gremlins barfs for a reason, theres a problem in your code. its the same thing when debug roms barf. sure, your application may work on existing devices; however, the tools provided allow you to test how well things will work on future devices. all warnings you see, will, most likely cause your application to have some problem on future devices. when it comes to 'turning off' warnings, there are times when you may. more specifically, we do this a lot with gaming. the warnings we turn off are: - direct UI mgr structure access - screen access - CPU register access however, we dont do this blindly. we poke UI mgr structures, mess with the screen and CPU registers :) yes, we are evil. however, we only do this if we know 100% for certain that we can. at all other times, we are 100% strict at using API's to do the same thing. poking UI mgr, screen and CPU registers gives us huge speed advantages on known units; however, our applications run fine on OS5 units. it takes time, however, but, you'll figure it out eventually :) --- Aaron Ardiri [EMAIL PROTECTED] CEO - CTO +46 70 656 1143 Mobile Wizardry http://www.mobilewizardry.com/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
