On 2009-04-15 at 09:57:14 [+0200], Truls Becken <truls.becken@xxxxxxxxx> wrote: > Stephan Aßmus wrote: > > > Ingo just had the most elegant idea: The vector icon format could be > > extended to know that it's an overlay (like a marker in the data). > > Something which you can set in Icon-O-Matic. And then add support in > > the icon resolving code to keep resolving the icon from super types and > > composing them together. This means you would use the regular API to > > set an icon on a file, only this icon is set to be an "overlay". (There > > would be new API to fetch or create overlay icons for certain > > purposes.) The writing of the regular icon attribute would trigger > > Tracker to update the pose as always, only the icon retrieval methods > > (they are all channelled through BIconUtils now) would be aware of the > > icon being an overlay, keep resolving the icon from type and super type > > like it would if the node had no icon, and then compose the overlay on > > top. > > This sounds nice and efficient for the most part, but it has one > limitation; you can't put an overlay on a node that already has an icon. > For instance, directories with custom icons can't have VC status overlays. > > Maybe this is not really a problem, but one needs to be aware of the > limitation. It will mostly affect people who use custom icons extensively. Good point. That would be supposed to work, though, so maybe back to thinking... Best regards, -Stephan