<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Am 15.08.2020 um 01:44 schrieb Myah Caron <<a href="mailto:qsniyg@protonmail.com" class="">qsniyg@protonmail.com</a>>:</div><br class="Apple-interchange-newline"><div class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">Sorry I'm a bit new so I'm not quite sure what the rules are regarding TRACEs, but would adding a TRACE here be an issue? I think it might be helpful for future debugging if there are any other issues with it.</span><br style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""></div></blockquote></div><br class=""><div class="">Those 'rules' are somewhat inconsistent. I would say adding a TRACE here is a good idea, but not strictly necessary.</div><div class=""><br class=""></div><div class="">A lot of functions in kernel32/kernelbase and ntdll have no TRACEs because they show up in a +relay log. But since I am used to COM interfaces in d3d which don't show up in relay logs (+relay injects code into DLL exports, and COM interfaces aren't PE exports) I am very used to +ddraw showing me all ddraw calls, so at times I am confused when +winmm doesn't show half the winmm calls.</div></body></html>