- 0001-const-up-modifier_combining_marks.patch has been fixed upstream
This commit introduces a new hardware-accelerated video filter, scale_d3d11, which performs scaling and format conversion using Direct3D 11.
Adds D3D11 input surface support to the MediaFoundation encoder (mfenc), allowing direct encoding of GPU frames without readback to system memory.
Used e.g.
Call SfxTabDialogController::AddTabPage to add the data of the new tab to `m_pImpl->aData` before adding the page to the weld::Notebook widget.
Did the necessary now, despite it would be better to apply that where the geometry gets created (primitives) or painted (older direct-apints to OutputDevice).
When trying to set the initially active page in a tab dialog to the one that was remembered, verify that a tab with the given ID actually exists. Only try to set it as the active one if that is the case, otherwise fall back to activating the first tab, as happens when none has been remembered. One case where this is relevant are dialogs that don't always show up with the same set of tabs available, like the chart attributes one. Without this commit in place, the following scenario would trigger a warn:sfx.dialog:483586:483586:sfx2/source/dialog/tabdlg.cxx:537: Tab Page ID '' not known, this is pretty serious and needs investigation warning and leave the dialog with no tab initially selected for the VCL (SalInstanceNotebook) case, e.g.
There is no convenient way, from the command line, to figure out which formats a filter actually supports.
This will be used by an upcoming commit adding support for the Graphics test dialog that can be triggered as follows:
This means that a native Qt menu is now used for that menu when using the qt5 or qt6 VCL plugin if the menu has a native Qt widget parent and LO was started with environment variable SAL_VCL_QT_USE_WELDED_WIDGETS=1 set.
Change the approach to handling the special "expander toggle" that is documented in the weld::TreeView API: // col index -1 sets the expander toggle, enable_toggle_buttons must have been called to create that column virtual void set_toggle(const TreeIter& rIter, TriState bOn, int col = -1) = 0; // col index -1 gets the expander toggle, enable_toggle_buttons must have been called to create that column virtual TriState get_toggle(const TreeIter& rIter, int col = -1) const = 0; Instead of using a separate column for it, instead always set the checked state for the existing column at index 0. This is similar to the approach for the "expander image" implemented in commit a838839e4d191c62a9396ee65af9a116a617160f Author: Michael Weghorn Date: Fri Jul 25 07:59:01 2025 +0200 tdf#130857 qt weld: Support setting TreeView "expander image" and (similar to what is described in the above-mentioned commit for the expander image) not using a separate column will allow having a column title for the "expander toggle" and the first "normal" column together, which is e.g.
...also in -sMODULARIZE builds (and as expected to be available by the code in static/emscripten/uno.js).
Fixes AMF_INPUT_FULL errors with pre-analysis (PA) enabled.
This change improves pipeline stability and reduces dynamic GPU surface allocations when using AMF with copy_frame = 1.
- Can be used under "Paste As" by manually registering markdown mime type "text/markdown" using cli tools like xclip and wl-paste.
(Which I find useful when working on the C++ code of the Emscripten that is used to build LO and having ccache's depend mode, CCACHE_DEPEND=1, enabled: Otherwise, ccache would generally not rebuild our code when included emscripten/*.h include files have changed.)
+ move the formula insertion logic from sidebar to the uno command + use the unoCommand with parameters in the sidebar code
The rules for outputting character-level formatting to RTF are utterly convoluted.
In commit f84b33275f6cce21e93e5dd20f3de5df84df0276 (tdf#129522 ww8import/export: allow char shadow_NONE overrides, 2020-01-04), export of char shadow was implemented, which made CharBorder to be called for missing borderline.
This gives vastly improved blending results than when blending directly in the desired output colorspace.
The previous formula was introduced without justification in 6e713841e8, and the only thing Paul had to say about it over IRC was that it was copied from an unspecified source on the internet. I decided to do some testing and came to the conclusion that this term not only produces "illegal" files, but also lowers PSNR score, over the naive implementation without this extra term. Here are the results of a round-trip test, using allrgb/allyuv (respectively) as the input, and fade=alpha=yes:n=256 to cycle through every possible alpha value, comparing the round-trip output against the input: Before patch: PSNR r:26.677431 g:26.677431 b:26.677431 a:inf average:27.926818 min:6.012093 max:55.400791 PSNR y:26.677431 u:21.101981 v:21.101981 a:inf average:23.548981 min:9.013835 max:53.182303 (full) PSNR y:27.348055 u:21.101981 v:21.101981 a:inf average:23.625238 min:9.554991 max:45.652221 (limited) After patch: PSNR r:27.321996 g:27.321996 b:27.321996 a:inf average:28.571384 min:6.012093 max:52.424553 PSNR y:27.321996 u:23.187879 v:23.187879 a:inf average:25.431773 min:9.013835 max:50.199232 (full) PSNR y:27.868544 u:23.187879 v:23.187879 a:inf average:25.515660 min:9.554991 max:45.078298 (limited) It's worth pointing out that previous version sometimes artificially inflates PSNR by producing values that are too high (i.e.
Should allow for forward compatibility with newer versions.