<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class="">On Dec 3, 2019, at 1:15 AM, Healey, Joseph <<a href="mailto:J.Healey.1@warwick.ac.uk" class="">J.Healey.1@warwick.ac.uk</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><ol start="1" type="a" style="margin-bottom: 0cm; 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=""><li class="MsoListParagraph" style="margin-right: 0cm; margin-left: 0cm; font-size: 11pt; font-family: Calibri, sans-serif;"><span class="">On a related note, is there a need to programmatically ‘refresh’ rangecol/RBA after defining the attribute, as there is with the dialogue box, or should it be happy once the attr is set?</span></li></ol></div></blockquote><br class=""></div><div>rangecolor will work without any nudging. The Render By Attribute dialog will remain blissfully unaware of the new attributes until you use its refresh menu item. You can use that dialog’s refreshAttrs() method to programatically nudge it. Look at MultAlignViewer/MAViewer.py in your Chimera distribution for an example (search for refreshAttrs).</div><div><br class=""></div><div>—Eric</div><br class=""><div class=""><div class=""><div class=""><span class="Apple-tab-span" style="white-space: pre;"><br class="Apple-interchange-newline"> </span>Eric Pettersen</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>UCSF Computer Graphics Lab</div><div class=""><br class=""></div><br class="Apple-interchange-newline"></div><br class=""><div><blockquote type="cite" class=""></blockquote></div></div></body></html>