<body><div id="__MailbirdStyleContent" style="font-size: 12pt;font-family: calibri;color: #000000">
Well, "Smalltalk cleanUp:except:" does exactly that, it iterates over all classes. :-) The call "UserInterfaceTheme cleanUp: true" was just an ad-hoc, oversimplified example for programmers to try out.<div><br></div><div>I just added a new test for the themes. If the integrity of a theme is broken, one can just browse all senders of #userInterfaceTheme and debug. I claim that it is quite simple to diagnose. :)</div><div><br></div><div>Best,</div><div>Marcel</div><div class="mb_sig"></div><blockquote class="history_container" type="cite" style="border-left-style:solid;border-width:1px; margin-top:20px; margin-left:0px;padding-left:10px;">
<p style="color: #AAAAAA; margin-top: 10px;">Am 18.09.2017 11:12:52 schrieb Stéphane Rollandin <lecteur@zogotounga.net>:</p>> As for your GC concerns: Can you construct a more elaborate example? If <br>> your environment experiences a severe memory issue, you should just try <br>> to clean-up the system like in the release process:<br><br>I have no problem in my images, it's just by perusing the code that I <br>saw that #userInterfaceTheme requires a specific handling.<br><br>What worries me is not the normal usage of #userInterfaceTheme, which <br>works fine, it is how technically easy it is to mess things up, although <br>I do not see that happening too often or at all actually. But if it <br>happens sometime, somewhere, it will be a silent bug difficult to diagnose.<br><br>BTW I see that the #cleanUp: method will indeed reset all stacks in <br>hard-coded subclasses of UserInterfaceTheme, but it will not do so for <br>possibly existing other subclasses. So if I create my own <br>MuOInterfaceTheme for example, I will also need to monkey-patch <br>#cleanUp:.. Maybe we should iterate long #allSubclasses?<br><br>Stef<br><br>
</blockquote>
</div></body>