<body><div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000">
Hi Subbu,<div><br></div><div>you have a point. Such defaults in tool-builder specs are interfering with defaults in morphs (or other widgets).</div><div><br></div><div>Which effects did you observe after making this change?</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 15.03.2019 07:44:34 schrieb K K Subbu <kksubbu.ml@gmail.com>:</p><div style="font-family:Arial,Helvetica,sans-serif">Hi,
<br>
<br>PluggableTextSpec>>font returns a default font if font is not specified.
<br>This results in default font overriding any fonts in the plugged
<br>textmorphs :-( as in the case of Help->FontSizeSummary. The exact font
<br>to be used to render text should be determined lazily by textMorph and
<br>not in pluggable text spec.
<br>
<br>My proposed fix has a wide ranging effect, so I am posting it here for a
<br>critique before finalizing a patch to Inbox.
<br>
<br>Thanks and Regards .. Subbu
<br><br></div></blockquote>
</div></body>