https://bugs.documentfoundation.org/show_bug.cgi?id=163947
--- Comment #9 from Caolán McNamara <[email protected]> --- (In reply to Michael Weghorn from comment #8) > I've e.g. seen that the VclBuilder ctor takes a `bLegacy` flag, and that the > `NotebookBar` ctor unconditionally creates a VclBuilder instance with > `bLegacy=true`. So that use case doesn't seem to support the weld approach. > Don't know whether that's "just not implemented yet" or not meant to support > welding at all. > (I could imagine that *if* this "legacy" path uses non-standard UI files > that GtkBuilder could not handle, that might require special handling.) Yeah, we just use the gtk3 .ui file format with normal common gtk widgets nearly everywhere. And on gtk3 we just use gtk to load and generate gtk widgets for us, while on the non-gtk3 platforms we have our own .ui file loader that generates vcl widgets from the .ui file. But, yes, the notebookbar ones, like sw/uiconfig/swriter/ui/notebookbar.ui etc use the gtk .ui format, but with custom widgets like "sfxlo-NotebookbarToolBox" "sfxlo-DropdownBox" "VclOptionalBox" and a whole zoo of other weird and wonderful custom (generally just container?) widgets (that I don't know why exactly exist or what difference they are from some more 'normal' widgets). And for those the bLegacy flag is used on loading to ensure they are created from vcl widgets even for the gtk front end. The glade catalog of those notebookbar widgets is very minimal and just maps them to some pre-existing similar gtk widgets for the purpose of making it easy to move parts of the notebookbar around in glade. -- You are receiving this mail because: You are the assignee for the bug.
