<body><div id="__MailbirdStyleContent" style="font-size: 12pt;font-family: calibri;color: #000000">
Well, the class UserInterfaceTheme is independent from Morphic. It belongs to the system. Kind of a more fancy version of Preferences with a slight tendency towards visuals only instead of "interaction stuff".<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 16.09.2017 20:05:23 schrieb tim Rowledge <tim@rowledge.org>:</p><br>> On 16-09-2017, at 2:40 AM, Marcel Taeumel <marcel.taeumel@hpi.de> wrote:<br>> <br>> Hi Tim,<br>> <br>> I am sorry that the core mechanism of the User Interface Themes confuses you. :)<br><br>Ah, it’s just the price of getting old and senile. You young whipper-snappers just don’t understand. Now git orff moi lawn!<br><br>> The idea of application-specific UI properties, such as window colors, kind of overlaps/interferes with the idea of general widget theming.<br><br>I don’t have any problem with your theming as such; it’s a jolly good thing. It’s the non-implemented #customWindowColor message and the sneaky (not necessarily bad, but hard to find, follow and document) usurpation of dNU: that bothers me a bit. Instead of trapping a fairly crucial system error doohickey and performing unnatural acts upon its person why wouldn’t you just implement #customWindowColor in UserInterfaceTheme ? <br><br><br>tim<br>--<br>tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim<br>Strange OpCodes: OKP: On your Knees and Pray!<br><br><br><br></marcel.taeumel@hpi.de>
</blockquote>
</div></body>