<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Here's my earlier reply to Matt that I accidentally did not sent to chimera-dev.</div><div><br></div><div>Hi Matt,<br><br> I've attached some Python showing how to position various dialogs on the screen. It just requires knowing the dialog name. Have to paw through Chimera code to find that -- hard for you. Sorry we do not have Chimera programming documented. It is a goal of Chimera 2 that all the programming info will be documented.<br><br> Not sure why the keyboard shortcuts are only sometimes active. But I'd bet it is because the graphics window doesn't have the focus. If you automatically start the command-line and keyboard shortcuts, it may be random which one wins and gets the keyboard input. I have keyboard shortcuts on by default but not command-line and I believe on the Mac they always work first time for me.<br><br> You can set the volume rendering transfer function to a window using the volume command. For example,<br><br><span class="Apple-tab-span" style="white-space: pre; "> </span>volume #0 style solid level 1.1,0.8 level 2.3,0.8<br><br>sets the brightness and opacity to .8 (on a scale of 0 to 1) over density value interval 1.1 to 2.3. The brightness and opacity unfortunately cannot be independently controlled. Chimera is capable of it, but it would require low level function calls. Also if you set opacities all to 1 you tend to get a black cube unless you add "colorMode rgba".<br><br><span class="Apple-tab-span" style="white-space: pre; "> </span>Tom</div><div><br></div><div><br></div><div></div></body></html>