Re: Filters

-----Message d'origine-----
[mailto:wdsci-l-bounces@xxxxxxxxxxxx] De la part de Kurt Anderson

David: I'm trying to grasp how you're using filter pools. I
have only found them to be a means of organization, nothing
else. It would be wonderful if each filter pool had its own
library list. You can create a library list filter for a
pool, but all it really does is expose you to the current
library list. So I'm trying to figure out. Then again, I
only have one connection, so maybe I'm not aware of how they
work across multiple connections.

I create a connection for each project I'm working on on the i. When I open a connection, there'll be the corresponding development library as the *curlib, and I may tell it to call a standard program on the i that just sets up the library list.

For each connection, the standard filter pool for that profil will show up automatically.
My filters effectively only use *curlib or *libl. So I control their contents with the connection, not the filter pool. In each connection, I see the same filters with different content.