<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - cairo 1.12.16: minor fixes to the docs" href="https://bugs.freedesktop.org/show_bug.cgi?id=82741#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - cairo 1.12.16: minor fixes to the docs" href="https://bugs.freedesktop.org/show_bug.cgi?id=82741">bug 82741</a> from <a class="email" href="mailto:bryce@osg.samsung.com" title="Bryce Harrington <bryce@osg.samsung.com>"> Bryce Harrington</a> <pre>I'll go ahead and take the removal of the doxygen for cairo_set_opacity(). I can't discern why it was disabled or what side effects re-enabling it might incur, but looks like it deserves future study if/when someone has the inclination. Potentially it could be removed, as it's been 7 years with no complaints about its omission... commit 35fccff6ec393ccca3d3ced79093ca491ce32df4 Author: Bryce Harrington <<a href="mailto:bryce@osg.samsung.com">bryce@osg.samsung.com</a>> AuthorDate: Mon Nov 6 12:09:53 2017 -0800 Commit: Bryce Harrington <<a href="mailto:bryce@osg.samsung.com">bryce@osg.samsung.com</a>> CommitDate: Mon Nov 6 12:18:37 2017 -0800 Un-doxygen disabled cairo_set_opacity The cairo_set_opacity() routine has been disabled since 2010. There appears to be support for it internally in the backend, so it is unclear why it is not enabled or what might break if it were re-enabled. Given the lack of bug reports about its omission, it may be vestigal. For now, just hide the doxygen for it to suppress warnings. It may be worth deeper review to either re-enable it or remove it entirely. Reported-by: Rafał Mużyło (See fdo bugzilla #82741) Signed-off-by: Bryce Harrington <<a href="mailto:bryce@osg.samsung.com">bryce@osg.samsung.com</a>></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>