|
From: Jeff H. <je...@ac...> - 2006-06-27 22:25:13
|
Joe English wrote: > Last week, Jeff Hobbs wrote: ... > It's not necessary to redefine the "MenuEntry" layout in=20 > every available theme -- you can define it just once in the=20 > "default" theme: ... > and all other themes will inherit it. >=20 > Same goes for the MenuEntry.icon element -- you can use: Thanks for the recommendation. > The other style settings, OTOH -- >=20 > | style configure MenuEntry -padding $pad > | style map MenuEntry -image [list disabled ::widget::img_menuentry] >=20 > *do* need to be respecified in each theme. I don't have a=20 > good solution for that. These are actually not used in the latest CVS. I actually had a = question on that ... the -padding that I eventually applied to the MenuEntry.icon = only seemed "odd", but it worked across platforms. Why is that -padding inconsistent with the general usage? > [ An aside: here, I'd recommend using a one-part name for the element = -- > "menuEntryIcon" instead of "MenuEntry.icon" -- since that's less = likely > to run into conflicts if some other custom widget in some other = theme > defines its own "*.icon" element. The full ramifications > of the theme engine's current fallback/inheritance strategies > are not entirely clear at present :-( ] I noticed that. I even tried to go through the code a bit ... = unsuccessfully. I'll modify the name, but it would be nice to have this kind of naming = "work". Jeff |