mirror of
https://github.com/X11Libre/xserver.git
synced 2026-03-24 10:14:52 +00:00
b0f94e1c5c
Right now, extensions that need to be called after the CreateScreenResources proc had been run, must wrap the screen proc vector directly (all of them forming kind of daisy chain), and so - when called - temporarily restore the previous one, call it, wrap again, and if the call was successful finally doing it's own stuff. (same is done for many other procs) While that approach is looking nice and elegant on the drawing board, it's complicated, dangerous like a chainsaw and makes debugging hard, leading to pretty blurred API borders. Instead introducing a simple approach for letting extension hook into a post-CreateScreenResources callback list safely, w/o having to care much about side effects with the call chain. Extensions now can simply register their business logic and get called back - w/o ever having to mess with the ScreenRec's internal structures. Note that these hooks are executed *AFTER* the original CreateScreenResources() proc had been called SUCCESSFULLY (returned TRUE), so callees can rely on the DDX/driver had already done it's job. Signed-off-by: Enrico Weigelt, metux IT consult <info@metux.net>