update to https://www.scintilla.org/scintilla533.zip with:
1. Released 8 February 2023.
2. Fix SCI_LINESJOIN bug where carriage returns were incorrectly retained. Bug #2372.
3. Fix SCI_VERTICALCENTRECARET to update the vertical scroll position.
4. When an autocompletion list is shown in response to SCN_CHARADDED, do not process character as fill-up or stop. This avoids closing immediately when a character may both trigger and finish autocompletion.
5. On Cocoa fix character input bug where dotless 'i' and some other extended Latin characters could not be entered. The change also stops SCI_ASSIGNCMDKEY from working with these characters on Cocoa. Bug #2374.
6. On GTK, support IME context. Feature #1476.
7. On GTK on Win32, fix scrolling speed to not be too fast. Bug #2375.
8. On Qt, fix indicator drawing past left of text pane over margin. Bug #2373, Bug #1956.
9. On Qt, allow scrolling with mouse wheel when scroll bar hidden.
and https://www.scintilla.org/lexilla522.zip with
1. Released 8 February 2023.
2. C++: Fix keywords that start with non-ASCII. Also affects other lexers. Issue #130.
3. Matlab: Include more prefix and suffix characters in numeric literals. Issue #120.
4. Matlab: More accurate treatment of line ends inside strings. Matlab and Octave are different here. Issue #18.
5. Modula-3: Don't treat identifier suffix that matches keyword as keyword. Issue #129.
6. Modula-3: Fix endless loop in folder. Issue #128.
7. Modula-3: Fix access to lines beyond document end in folder. Issue #131.
8. Python: Don't highlight match and case as keywords in contexts where they probably aren't used as keywords. Pull request #122.
9. X12: Support empty envelopes. Bug #2369.
update CMakeLists.txt to latest changes within vcxproj file
Close#13082
update to https://www.scintilla.org/scintilla532.zip with:
Released 6 December 2022.
Add SCI_REPLACETARGETMINIMAL to change text without causing unchanged prefix and suffix to be marked as modified in change history.
Draw background colour for EOL annotations with standard and boxed visuals.
Add SCI_GETSTYLEDTEXTFULL to support 64-bit document positions on Win32 replacing SCI_GETSTYLEDTEXT which is not safe for huge documents. Feature #1455.
Send SCN_AUTOCCOMPLETED for SCI_AUTOCSHOW triggering insertion because of SCI_AUTOCSETCHOOSESINGLE mode. Feature #1459.
Change 'paragraph up' commands SCI_PARAUP and SCI_PARAUPEXTEND to go to the start position of the paragraph containing the caret. Only if the caret is already at the start of the paragraph will it go to the start of the previous paragraph. Bug #2363.
Change release compilation optimization option to favour speed over space. -O2 for MSVC and -O3 for gcc and clang.
On Win32, avoid blurry display with DirectWrite in GDI scaling mode. Bug #2344.
On Win32, use the top-level window to find the monitor for DirectWrite rendering parameters. Temporarily switch DPI awareness to find correct monitor in GDI scaling mode. Bug #2344.
On Qt, implement SCI_SETRECTANGULARSELECTIONMODIFIER for all platforms.
On Qt, allow string form XPM images for SCI_REGISTERIMAGE.
and https://www.scintilla.org/lexilla521.zip with
Released 6 December 2022.
Update to Unicode 14. Feature #1461.
Change default compilation optimization option to favour speed over space. -O2 for MSVC and -O3 for gcc and clang.
Batch: Fix comments starting inside strings. Issue #115.
F#: Lex signed numeric literals more accurately. Issue #110, Issue #111.
F#: Add specifiers for 64-bit integer and floating point literals. Issue #112.
Markdown: Stop styling numbers at line start in PRECHAR style. Issue #117.
PowerShell: Recognise numeric literals more accurately. Issue #118.
Close#12624
Also mark several found occurrences in the same entry - user can click on the marked occurrence to jump among found result in the found line.
This option is enabled by default. It can be disabled in "Searching" section of Preferences dialog.
It's an alternative implementation of #11705Fix#2481, fix#1499, fix#5547, fix#2987, fix#4525, fix#3224, close#11808
For the sake of maintenance of Scintilla (future update), we try to not modify Scintilla project, or at least minimize its modification.
Hence the compiling boost part is shifted to Notepad++ project.
Fix#11014, close#11485
Update with https://www.scintilla.org/scintilla521.ziphttps://www.scintilla.org/lexilla515.zip
- fix setting to bring Scintilla::PositionCR from ScintillaStructures.h inline with Sci_Position.h Sci_PositionCR
- add workaround to enable lexer for searchResult
commented out SCI_SETILEXER call on searchResult to get one result which is correctly handled by the lexer,
added comment about the current problem with property @MarkingsStruct which seems to disappear after call to SCI_SETILEXER or CreateLexer
- corrected usage of ObjC lexer
- removed unnecessary filter stuff
- use own sections for scintilla and lexilla build targets and allow parallel builds
- as libscilex is no longer existing, changed to libscintilla
- adapt makefiles and cmake
- use VS2019
- started simple changes for createlexer adaptations, nullpointercheck missing on return of lexer name from deprecated LexerNameFromID -> undefined behaviour
- movement from id -> lexer name, mostly done via LexerNameFromID + switching off corresponding compiler warning
- changed to SCI_SETILEXER from SCI_SETLEXER, SCI_SETLEXERLANGUAGE needs to be corrected, see Scintilla5Migration.html
- just commented out: SCI_LOADLEXERLIBRARY
Fix#10504, close#11419
This fixes a bug where UDL folding breaks if 1) the file uses
non-Windows line endings and 2) delimiters are defined.
Fix#350, fix#2873, fix#3372, fix#5499, close#7930
Fixed a condition in a loop which is always true (unsigned >= 0) and can
potentially turn the loop infinite.
And removed a check after the loop which now is also always false.
Close#10597
LexerStylerArray contains a MAX_LEXER_STYLE-element array (currently 100) of LexerStyler objects. Every one of them in turn via inheritance from StyleArray contains a SCE_STYLE_ARRAY_SIZE-element array (I tested with 99) of Style objects each at least 56 bytes in size. This in my test case requires over 550k of memory, and if LexerStylerArray is allocated on stack, the stack becomes corrupted. (Ref: https://github.com/notepad-plus-plus/notepad-plus-plus/issues/10454#issuecomment-908732786)
Inline arrays are a part of an object and increase its size while std::vector uses memory from the heap and stores internally only a pointer to a chunk of memory, thus the size of an object with a vector is substantially smaller than the one with an inline array. (Ref: https://github.com/notepad-plus-plus/notepad-plus-plus/issues/10454#issuecomment-908780106)
Fix#10454, fix#10206
Rename "Unicode Debug" => "Debug", "Unicode Release" => "Release"
since there is no non-Unicode version.
Also, fix the name in other configs for Git, AppVeyor and in the docs.
Fix#10114, close#10278
The reason, why the flicker occurs, is the following: There are two Windows messages sent by Windows to Scintilla, when the mouse is moved: WM_MOUSEMOVE and WM_SETCURSOR.
WM_MOUSEMOVE informs Scintilla, that the mouse has been moved inside its window.
WM_SETCURSOR informs Scintilla, that the mouse cursor has been moved. Anywhere, not necessarily in its window.
Scintilla calls the Windows function SetCursor (, which sets the mouse cursor shape, not the position), while processing both messages. Unfortunately, Scintilla uses different ways to calculate the desired cursor shape. So, whenever the mouse cursor is moved, two SetCursor calls are applied, sometimes with two different cursor shapes.
On WM_MOUSEMOVE, Scintilla calls ButtonMoveWithModifiers, which sets the correct cursor shape.
On WM_SETCURSOR, Scintilla calls SetCursor directly, sometimes with the wrong cursor shape.
This PR shows how to eliminate this effect in the modified Scintilla version used by Notepad++. This may be the fastest way to get results without introducing new effects.
The current original Scintilla version (Version 4.4.4, downloaded 2020-07-30, 5d134721c303ceecbdcb28ec82b28f0cbbdb4a55) has the same effect and can be fixed in the same way, although the WM_SETCURSOR code has been changed a little. Before updating to a new Scintilla version, we should try to get it fixed in the original Scintilla.
Fix#8588, fix#8647, close#8641
Christian Grasser