menu-spec: Excluded items are Unllocated

[Mark McLoughlin]

Hi,

On Wed, 2004-12-08 at 09:40 -0500, Mark McLoughlin wrote:
> On Wed, 2004-12-08 at 14:55 +0100, Waldo Bastian wrote:
> > On Wednesday 08 December 2004 14:32, you wrote:

> > > 	Well, we could say that items which match an <Include> rule are
> > > "allocated" whether or not they are later excluded by an <Exclude> rule.
> > > If the goal of <OnlyUnAllocated/> is to catch items that don't fit in
> > > any other category, then I think that would work fine.
> > 
> > Hmm... so 
> > 
> > <Include>
> >  <And><Category>foo</Category><Not><Category>bar</Category></Not></And>
> > </Include>
> > 
> > would not allocate the "bar" items and
> > 
> > <Include>
> >  <And><Category>foo</Category></And>
> > </Include>
> > <Exclude>
> >  <And><Category>bar</Category></And>
> > </Exclude>
> > 
> > would allocate the "bar" items then?
> > 
> > I guess that would work.
> 
> 	Right, the idea being that in former example items with Category Bar
> aren't a good fit for that menu, but in the latter example they are a
> good fit, but you just don't want them displayed.
> 
> 	How does the attached patch look? Also changed the <OnlyUnallocated>
> test to catch this.

	I've gone ahead and committed that now ...

Cheers,
Mark.