I had always been under the impression that keeping the database open
would be problematic for other reasons. But now, I can't recall what my
original thinking was. I've also always been leery to do anything other
than modal dialog type stuff from the lib. Again, I don't know why.
-jjf
-----Original Message-----
From: Danny Epstein [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 26, 2000 2:54 PM
To: Palm Developer Forum
Subject: Re: Resources in a Shared Library
"Adam Wozniak" <[EMAIL PROTECTED]> wrote in message
news:9715@palm-dev-forum...
> Don't you run into similar problems if you open two shared libraries
simultaneously?
Your absolutely right. Thanks for pointing this out - it gives me an
excuse
for a more detailed explanation. :)
Reserving a range of resource IDs for shared libraries doesn't solve all
our
problems, but I think it's a step in the right direction. Some of the
problems we haven't addressed:
- app uses two libs at once
- lib uses another lib
- libs running in other tasks
You guys shouldn't have to worry about the last one. The other two will
require the libraries to agree not to stomp on each other. If a library
doesn't keep databases open, it shouldn't have any problems. If it does,
it'll have to document the range of IDs it uses so that the app can
avoid ID
conflicts when using two libraries at once.
If you have any ideas for how we can address these problems, please let
me
know. Thanks.
--
Danny Epstein
OS Engineer, Palm Inc.
--
For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palm.com/devzone/mailinglists.html
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
