priority- is implemented for DropdonwBox in a PriorityBox but not within a ContextContainer. So in the context related toolbar area priority- didn't work.
please make it possible to use DropdownBox in a ContextContainer where priority will work.
Have you tried placing PriorityBox within a ContextContainer child element per context, as i believe that should work fine, just like it works with multiple tabs of the tabbed implementation.
Please attach a sample test ui file if it didnt work?
Created attachment 132655 [details]
I change the subboxes to PriorityHBox, but it doesn't work like you descibe. what did I wrong?
thanks for your help
Created attachment 132658 [details]
amended example file
(In reply to andreas_k from comment #2)
> I change the subboxes to PriorityHBox, but it doesn't work like you descibe.
> what did I wrong?
The sample file didnt have PriorityHBox as a child of a ContextVBox. Well i've attached an amended version of what you provided and the functionality works now. I moved all the separators as child elements of PriorityHBox, as "DropdownBox should have only one child (eg. GtkBox) otherwise popup is not working correctly." - https://wiki.documentfoundation.org/Development/NotebookBar/Implementation#PriorityHBox_and_DropdownBox
For some strange reason ContextVBox renders smaller than it really is, which makes all the collapsible sections being collapsed even though there is more than sufficient space. Not sure if this is an issue with how you designed the file or not.
Everything works if PriorityHBox is inside ContextVBox (but all parent containers have to be horizontally expandable). Example:
when switch from one context to another context- area it wasn't update the notebookbar.
Szymon Kłos committed a patch related to this issue.
It has been pushed to "master":
tdf#107239 make PriorityHBox working in the compact notebookbar
It will be available in 6.0.0.
The patch should be included in the daily builds available at
http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.