mirror of
https://github.com/brues-code/ClassicAPI.git
synced 2026-11-16 16:10:36 +00:00
ScrollingMessageFrame:RemoveMessagesByPredicate(predicate), retail's: the predicate is called with each message's GetMessageInfo values, oldest first, and the messages it returns true for are removed; the rest keep their order. It covers 4.3.4's RemoveMessagesByAccessID / ByExtraData, whose int fields the retail-shaped records here do not have. 1.12's ring has no compaction of its own; the removal is 4.3.4's RemoveLines loop over it: every kept record moves forward in ring order to the first free slot (freeing the text it lands on, nulling the one it left), the position moves back by the removed count, and the extra-argument tables move with their records. Then the engine's own layout (0x00788750) from the record at the kept scroll offset, clamped to the oldest, and its re-arm (0x00788B80) - a layout at the bottom keeps the fade state, so 4.3.4 re-arms after - or its Clear (0x007882B0) when nothing is kept. The predicate runs for every message before anything moves, through the engine's error handler; a predicate that errors keeps that message, as retail's safesecurecall does. GetMessageInfo shares its record lookup and value push with it.