This doesn't make a whole lot of sense. Add compatibility setting "HiddenParagraphMarkPerLineProperties" for RTF and DOCX compatibilityMode < 15. Apparently what Word's "Compatibility Mode" is doing in case a paragraph mark has hidden formatting is that it merges the last line of the first paragraph and the first line of the second paragraph together, and applies the first paragraph's properties to the line (and the preceding lines); but for the second line of the second paragraph, it applies the second paragraph's properties. This is now implemented here; firstly, by adding a flag to the MergedPara's Extents so that the situation can be distinguished (if the paragraphs are joined by a delete redline, Word does something different of course).
Refer to RFC 9725 4.2, "Once a session is set up, consent freshness as per [RFC7675] SHALL be used to detect non-graceful disconnection by full ICE implementations and DTLS teardown for session termination by either side"
The various game engines implement the following blit types, from the decoded result to the main canvas:- normal (opaque) blit (c37/c47/c48)- masked blit (c37/c48)- interpolated-frame blit (c48) Here an artificial frame is generated by looking up the pixels from both buffers and picking a color from the interpolation table for the artificial frame.
Add left/top offsets and clipping to codec20 (raw images), use it for the copying of codec37/47/48 images to main buffer.
Both of these encode a quarter-sized keyframe, with missing pixels interpolated from the immediate neighbours.
This adds a tester for the operations which can be performed on a sheet view, and a way to unsync sheet view if the operation is performed on the default view, which can't be synced with the sheet views.
The problem appeared, when a macro loaded a library with a class module, that had a public element (e.g., a function) with the same name, as used for a local variable in the macro without a prior DIM. Normally, there is a precaution in SbModule::Find, which hides the names in class modules.
Basically a direct port of the MMXEXT one.
This is not based on the MMXEXT one, because the latter is quite suboptimal: Motion vector types mc01 and mc03 (vertical motion vectors with remainder of one quarter or three quarter) use different neighboring lines for interpolation: mc01 uses two lines above and two lines below, mc03 one line above and three lines below.
...as seen after <
in headless vclplug too.
If there's nothing to send, skip over a bunch of code to make a list that won't be used, and hopefully make the code path clearer to both humans and static analyzers, who raise errors as seen in #1817 of dereferencing NULL pointers when count == 0.
This is beneficial size-wise: 384B of new asm functions are more than outweighted by 416B savings from simpler calls here (for size 16, the size 8 function had been called twice).
the prebuilt version for windows is 4.2.1, and lode also defaulted to newer versions for better interaction with the jobserver mode since 2023 (parallel linking with lto, accepted 4.2 if available, otherwise would have installed 4.4)
This patch addresses the actual cause of CVE-2025-5745
This patch addresses the actual cause of CVE-2025-5702
In QtBuilder evaluate the GtkWidget::width-request [1] and GtkWidget::height-request [2] properties and set the corresponding width/height as the minimum width/height for the QWidget. This matches what QtInstanceWidget::set_size_request currently does. This will e.g.
Switch the order in which the widgets in the .ui file are defined so that the order matches the visual appearance and logical order, which makes sure that tab focus order with the Qt-based VCL plugins is correct as well when using native Qt widgets (SAL_VCL_QT_USE_WELDED_WIDGETS=1), where focus order is (by default) based on widget creation order. Besides being used in "Tools" -> "Options"-> "LibreOfficeDev" -> "User Data", this is also used in a standalone dialog that can be triggered as follows: - start Writer - "Insert" -> "Field" -> "More Fields" - in the "Document" tab, select "Author" and "Name", then "Insert" and close the dialog - double-click on the newly inserted field to open the "Edit Fields" dialog - click on the "Edit" button (None of the two use cases are using native Qt widgets yet.
Since commit b664c08a6d1096d279437c883e55735a0c431ac8 (Drop support for Windows versions prior to Windows 10, 2024-12-07). See also: commit 75edcfc0569ca76fa22db451fd61138e52870a62 (no longer force -arch:SSE on Windows, 2020-05-07).
The element <table:sort> has the values 'alpha-numeric', 'double' and 'integer' in its attribute embedded-number-behavior in ODF.
The conversion has to copy contained references.
They are constant since the size 16 version is no longer emulated
This abides by the ABI (no missing emms) and yields a tiny performance improvement here.
The horizontal 10bit MC SSE2 functions are currently duplicated: They exist both in ordinary form as well as with a "sse2_cache64" suffix.