On Sun, 27 Jan 2013 18:18:20 +0000 "Carlos R. Mafra" <[email protected]> wrote:
> 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.
Sure,
the relevant parts are:
(
"Generated Submenu",
OPEN_MENU,
"|| find /usr/share/applications -type f -name '*desktop' | xargs wmmenugen
-parser:xdg"
),
("External Submenu", OPEN_MENU, "~/wmmenugen-file"),
where wmmenugen-file is generated via
find /usr/share/applications -type f -name '*desktop' | xargs wmmenugen
-parser:xdg > ~/wmmenugen-file
Currently opening "External Submenu" shows a valid submenu, "Generated Submenu"
does not, as the parsing codepath ist different.
By adding WMReadPropListFromPipe to WINGs and simply calling getPropList as is
done in WMReadPropListFromFile the same codepath is used for submenu generation
of both menus. This actually makes "Generated Submenu" work as expected and
more importantly making it work the same way as "External Submenu" does...
Hope this makes it clearer.
Regards,
Andreas
--
BR Andreas Bierfert, M.Sc. | phone: +49 6897 1721738 | GPG: C58CF1CB
[email protected] | fax: +49 6897 1722828 | signed/encrypted
http://lowlatency.de | cell: +49 170 9665206 | mail preferred
signature.asc
Description: PGP signature
