On Wed, 30 Jan 2013 at 11:45:21 +0100, Christophe wrote: > > ----- Carlos R. Mafra <[email protected]> a écrit : > > On Sun, 27 Jan 2013 at 18:24:08 +0100, Andreas Bierfert wrote: > > > > > > This way using an external menu file generated via 'wmmenugen > file' > > > will actually do the same as running wmmenugen as command for the > > > generated > > > menu (which currently just gives an empty menu for me). > > > > Can you please be a bit more verbose about this? How does your > > WMRootMenu look like when you use the first option ('wmmenugen > file') > > and how are you using the second option? > > > > I mean, if you can copy & paste the relevant parts of your WMRootMenu > > in these two cases that would make things easier to understand. > > > > I'm also explicitly Cc'ing Christophe Curis in the hope that he > > can share his thoughts about this :-) > > Hi Carlos, > > Sorry for the late answer...
Don't worry! > I have a little worry about the 2nd patch, because as-is it looks like > it makes the assumption that all the command-generated menus are using > the "pl" coding, which may not be the case every time (and was probably > not so far), so we may break compatibility. Good point. So the pipe menu would not handle the menu in text format after this patch? I'm afraid we can't do that. It would be great to add the functionality of proplist generated menus, but we can't lose the plain text along the way. Perhaps adding this new code for a new option like OPEN_PLMENU would be better? This way the old plain text would work unmodified. -- To unsubscribe, send mail to [email protected].
