From: Krzysztof Kosiński <tweenk.pl@gm...> - 2009-02-13 00:50:10
Jon A. Cruz wrote:
> The "legacy icons" are actually special cases where there is a
> name used by themes that does not match the older name used
> internally by Inkscape.
I am 100% sure those are the only icons looked up in the theme, because I
> Looking at my current OS X config, I see eleven of the twenty-five I
> see on my main toolbar are ones that come from my local theme.
You are probably confusing GTK stock item theming with application theming.
Inkscape uses some icons from the current theme because it uses GTK stock
items. The icons used for e.g. the tool switcher ar not themed.
> Oh, I was mainly thinking of creating tables listing icons and names
> for comparisons, etc. If you want to actually end up with SVG files,
> and not PNG exports, you should just look at verbs and the "--shell"
A table with icon names is a good idea. I'll create renders and a nice table
and put it somewhere on the wiki.
No, it's a bit different. The existing code is even in there that
> tracks things as needed.
I referred to the approach where we do the following:
1. Add all our icons using gtk_icon_theme_add_builtin_icon upon startup
2. Query the theme for any icons we need
This would need all icons to be pre-rendered before the start. However, your
post gave me another idea. We might add the builtin icons lazily, e.g. when
we find an icon which doesn't exist in the theme.
Ideally I would want a fallback order like this:
1. Query the icon in the current theme, looking for any size
2. Query the icon in PNG prerenders, looking for an exact size
3. Render from icons.svg and add as a builtin icon, after which all further
attempts to load this icon would end at 1 (GtkIconTheme would return the
icon we have rendered)
However, this requires changing the search path after the first query, and I
don't know how it would affect startup performance.
> when I turned on the debugging option that puts a grid
> of dots on all Inkscape rendered icons, I saw that the dots (single
> pixels) themselves blurred out.
Were those put on the SVG canvas as 1x1 rects, or on the renders? If the
latter is true, then that's weird. I think there might be a mixup in the
relation between logical and physical sizes somewhere in
Regards, Krzysztof Kosiński
View this message in context: http://www.nabble.com/Re%3A-Tango-icons-as-default-set-tp21645227p21988160.html
Sent from the Inkscape - Dev mailing list archive at Nabble.com.