-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
menu.xml and "CDATA" #972
Comments
Hi. Thanks for raising. |
...in order to support obmenu-generator output such as this: <menu id="root-menu" label="Applications"> <item label="File Manager"><action name="Execute"><command><![CDATA[xdg-open .]]></command></action></item> <item label="Terminal"><action name="Execute"><command><![CDATA[xterm]]></command></action></item> <item label="Web Browser"><action name="Execute"><command><![CDATA[xdg-open http://]]></command></action></item> <item label="Run command"><action name="Execute"><command><![CDATA[gmrun]]></command></action></item> </menu> References: - https://github.com/trizen/obmenu-generator - https://aur.archlinux.org/packages/obmenu-generator - https://trizenx.blogspot.com/2012/02/obmenu-generator.html Fixes: issue labwc#972
cool, initial testing of above the commit seems to be partially working, in that entries on the main menu work, but not on submenus. |
Submenus work for me (with obmenu-generator) Pipemenus are not supported if that’s what you mean (dynamic menus) Could you post your menu.xml |
Sorry - I get it now. My bad. I'll sort tonight. |
...in order to support obmenu-generator output such as this: <menu id="root-menu" label="Applications"> <item label="File Manager"><action name="Execute"><command><![CDATA[xdg-open .]]></command></action></item> <item label="Terminal"><action name="Execute"><command><![CDATA[xterm]]></command></action></item> <item label="Web Browser"><action name="Execute"><command><![CDATA[xdg-open http://]]></command></action></item> <item label="Run command"><action name="Execute"><command><![CDATA[gmrun]]></command></action></item> </menu> References: - https://github.com/trizen/obmenu-generator - https://aur.archlinux.org/packages/obmenu-generator - https://trizenx.blogspot.com/2012/02/obmenu-generator.html Fixes: issue labwc#972
Okay. All working now. Would appreciate another test drive (...because my testing skills are evidently not what they ought to be 🐒 ) |
...in order to support obmenu-generator output such as this: <menu id="root-menu" label="Applications"> <item label="File Manager"><action name="Execute"><command><![CDATA[xdg-open .]]></command></action></item> <item label="Terminal"><action name="Execute"><command><![CDATA[xterm]]></command></action></item> <item label="Web Browser"><action name="Execute"><command><![CDATA[xdg-open http://]]></command></action></item> <item label="Run command"><action name="Execute"><command><![CDATA[gmrun]]></command></action></item> </menu> References: - https://github.com/trizen/obmenu-generator - https://aur.archlinux.org/packages/obmenu-generator - https://trizenx.blogspot.com/2012/02/obmenu-generator.html Fixes: issue labwc#972
:) passes testing here, all levels of submenu working for me. |
...in order to support obmenu-generator output such as this: <menu id="root-menu" label="Applications"> <item label="File Manager"><action name="Execute"><command><![CDATA[xdg-open .]]></command></action></item> <item label="Terminal"><action name="Execute"><command><![CDATA[xterm]]></command></action></item> <item label="Web Browser"><action name="Execute"><command><![CDATA[xdg-open http://]]></command></action></item> <item label="Run command"><action name="Execute"><command><![CDATA[gmrun]]></command></action></item> </menu> References: - https://github.com/trizen/obmenu-generator - https://aur.archlinux.org/packages/obmenu-generator - https://trizenx.blogspot.com/2012/02/obmenu-generator.html Fixes: issue #972
i've noticed that some menu generators (eg. obmenu-generator and obamenu.py) output their xml execute sections enclosed in <![CDATA[foo]]> tags, which it appears labwc doesn't support?
could be out of scope and not a huge deal with labwc/wayland specific generators in the works.
also, as a work around it's fairly easy to hack those two examples being just scripts and remove the CDATA parts.
The text was updated successfully, but these errors were encountered: