Re: Scintilla 5.0.3 released

But why does mac need reinterpret_cast back into the old SCNotification 
instead of using the new one?
Is there any way to make it align with others?

void ScintillaCocoa::NotifyParent(NotificationData scn) {
scn.nmhdr.hwndFrom = (void *) this;
scn.nmhdr.idFrom = GetCtrlID();
if (notifyProc != NULL)
notifyProc(notifyObj, WM_NOTIFY, GetCtrlID(), (uintptr_t) &scn);
if (delegate)
[delegate notification: reinterpret_cast<SCNotification *>(&scn)];
if (scn.nmhdr.code == Notification::UpdateUI) {
NSView *content = ContentView();
if (FlagSet(scn.updated, Update::Content)) {
NSAccessibilityPostNotification(content, 
NSAccessibilityValueChangedNotification);
}
if (FlagSet(scn.updated, Update::Selection)) {
NSAccessibilityPostNotification(content, 
NSAccessibilitySelectedTextChangedNotification);
}
}
}


Neil Hodgson 在 2021年6月2日 星期三清晨5:26:43 [UTC+1] 的信中寫道：

> Scintilla 5.0.3 is now available from the scintilla.org web site.
>
> Scintilla 5.0.3 is an unstable release.
>
> A more type-safe binding of Scintilla's API that can be used from C++ is 
> implemented in the ScintillaTypes.h, ScintillaMessages.h, and 
> ScintillaStructures.h headers. This particularly impacts Qt where type 
> names are encoded into signal names. Qt users should check their signal 
> connection code and change as necessary. For example, “SCNotification” 
> becomes “Scintilla::NotificationData”.
>
> Drawing of selections, carets, caret line, and hot-spots have changed 
> significantly with more modes and drawing options. You should check whether 
> your current selection settings work well in all modes: normal, additional 
> (or rectangular), inactive and, on Unix, secondary. If there are problems, 
> the newer APIs should be used: first decide which layer you want the 
> selection to be drawn on (SCI_SETSELECTIONLAYER) then use the element APIs 
> (starting with SCI_SETELEMENTCOLOUR) to choose colour/translucency for each 
> state. On macOS + Cocoa experiment with using system settings with 
> SCI_RESETELEMENTCOLOUR.
>
> It is likely that there will only be bug fix releases before a stable 
> 5.1.0. The only planned upcoming (rarely) incompatible change is to update 
> the representation feature with representations always in UTF-8.
>
> Idle actions, wrapping and styling, may be smoother as they measure speed 
> by byte instead of line which could be perturbed by huge lines.
>
> Primary selection fixed on GTK 3 + Wayland.
>
> A C++17 compiler is required to build Scintilla. Microsoft Visual C++ 
> 2019, GCC 7.3, Clang 6.0, Xcode 9.2 Clang or newer will work. Some slightly 
> older compilers may still work.
>
> A list of changes is available on the history page.
> http://www.scintilla.org/ScintillaHistory.html
>
> Scintilla uses Mercurial (Hg) for source code control. The repository can 
> be cloned with
> hg clone http://hg.code.sf.net/p/scintilla/code scintilla
>
> Thanks to the contributors of code and documentation and to the testers.
>
> Neil
>
>

-- 
You received this message because you are subscribed to the Google Groups "scintilla-interest" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To view this discussion visit https://groups.google.com/d/msgid/scintilla-interest/3c2a5041-ef5c-4fb5-a63b-2270e2a142ban%40googlegroups.com.