Sorry, but I don't really understand what you're getting at.
Regarding: "The code I posted used a queue because it was based upon a Filter class I have been using":
But what does that have to do with basic selection set filter usage? Are you trying to teach the OP how to use your private code, or how to use a selection set filter?
Is there a point to muddying the waters or confusing them with a queue, when the basic initialization of a selection set filter neither requires nor should use a queue to begin with? In this case, where the filter itself is expressed literally in code, there is absolutely no point or purpose to using a queue.
Typically, when initializing a filter that's expressed literally in code, you just initialize the selection filter to an array of typed values, using (C#):
SelectionFilter filter = new SelectionFilter(
new TypedValue[] { new TypedValue(0, "TEXT,MTEXT"),
new TypedValue(8, "MYLAYER) });
>> And why is using a queue a horrible thing? It saves on having to set each TypedValue member by array index (which should help with maintainability). <<
Huh? Do you see any array indices in the code above?
>> I believe the code sample I posted answers the OPs question, plus it may give insight in how to use many new features in VS2005. <<
No not really.
First, the OP's and your use of logical operators in the filter list is in this case, unnecessary and needlessly overcomplicated. See the example code above where the entity type contains multiple stings separated by a comma - because it is a wildcard pattern.
Second, you didn't really introduce the OP to the basic use of SelectionFilter. You only confused the whole subject by needlessly introducing a queue, where its use is completely pointless.
Insofar as insight, it certainly does offer some. Most notably, on why one should avoid the temptation of using a particular class, inappropriately, and only for the sake of using the class.
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006/2007
http://www.acadxtabs.com