On Fri, 9 Apr 2010, Brad Jorsch wrote: > > "line that reads "OPEN_MENU" in the example above... well, it happens > > that appearance.menu has to be in the old format" > > > > that would be "take a file that is a complete menu definition on it's > > own right, and make it a submenu by inserting it into this-and-this > > position of this menu i am building right now", if i'm not mistaken? > > Could be, I don't know. Or it could be referring to the way > appearance.menu takes advantage of the cpp stuff.
it seems the meaning is that an included (in the OPEN_MENU sense) menu can not be a proplist one, so my hunch seems right so far. i'll look into making this a possibility. > > but having your menu change all of a sudden in the middle of a session > > just because your admin has decided to install a new app, not such a > > good idea > > Why not? Note that that's only if you are still referencing the > system-wide menu from your ~/GNUstep/.../WMRootMenu anyway. oh? that... explains a lot. i for some reason thought it backwards, ie. that by some magic doohickey mumbo-jumbo deb-specific mechanism it somehow... *poof* just gets there. ok, let me digest this some more. it doesn't at all look so cloudy now. -- [-] mkdir /nonexistent -- To unsubscribe, send mail to [email protected].
