you will terribly fragment dbcache and annoy your users. for the sake of them I ask you to completely reconsider your problem, because you are DEFINITELY doing something wrong if your event callback spans segments...
On 9/3/08, Hynek Sladky <[EMAIL PROTECTED]> wrote: > It is because of speed. Notification through PilotMain is terribly slow (if > it is used for eg. EventDequeuedEvent). So I need to lock all code in memory > because it seems that sometimes it is moved by system and Palm crashes :-( > So I am looking for way how to lock it in memory... > > Thanks, > Hynek Sladky > > > > Lionscribe wrote: > > > Why don't you just use the launch method, and save the hassle. > > If you are doing it to save speed, and you only need the notification in a > few instances, > > then just have the locked function do the checking if you should handle > it, and ifyou do then it should send it's own launch code when necessary. > > Lionscribe > > > > > > -- > For information on using the ACCESS Developer Forums, or to unsubscribe, > please see http://www.access-company.com/developers/forums/ > -- ---- Best Regards, Dmitry Grinberg (847) 226 9295 -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
