Hi James,
Can you try:
cmd.set("bg_rgb_bottom",cmd.get_color_tuple(bottom))
The number refers to a color index, so that should probably work.
Hope it helps,
Tsjerk
On Wed, Oct 8, 2014 at 9:27 AM, James Davidson <j.david...@vernalis.com>
wrote:
> Dear All,
>
>
>
> I wonder if anyone can help with this issue? I am currently using pymol
> 1.7.0.2 (based on SVN rev. 4087). Enabling gradient backgrounds works fine
> (as in previous versions) – however, when I try to change the gradient
> colours by setting bg_rgb_top / bg_rgb_bottom I see errors.
>
>
>
> For example:
>
>
>
> PyMOL>top = cmd.get("bg_rgb_top")
>
> PyMOL>bottom = cmd.get("bg_rgb_bottom")
>
> PyMOL>print top, bottom
>
> 0x00004d 0x333380
>
> PyMOL>cmd.set("bg_rgb_top", bottom)
>
> Setting-Error: type read mismatch (color) 663
>
> Setting-Error: type read mismatch (color) 663
>
> Setting-Error: type read mismatch (color) 663
>
> Setting-Error: type read mismatch (color) 663
>
> Setting-Error: type read mismatch (color) 663
>
> Setting-Error: type read mismatch (color) 663
>
> Setting-Error: type read mismatch (color) 663
>
> Setting-Error: type read mismatch (color) 663
>
> Setting-Error: type read mismatch (color) 663
>
> Setting-Error: type read mismatch (color) 663
>
> Setting-Error: type read mismatch (color) 663
>
> Setting-Error: type read mismatch (color) 663
>
> Setting-Error: type read mismatch (color) 663
>
> PyMOL>cmd.set("bg_rgb_bottom", top)
>
> Setting-Error: type read mismatch (color) 664
>
> Setting-Error: type read mismatch (color) 663
>
> Setting-Error: type read mismatch (color) 663
>
> Setting-Error: type read mismatch (color) 663
>
> Setting-Error: type read mismatch (color) 663
>
> Setting-Error: type read mismatch (color) 664
>
> Setting-Error: type read mismatch (color) 664
>
> Setting-Error: type read mismatch (color) 664
>
> Setting-Error: type read mismatch (color) 663
>
> Setting-Error: type read mismatch (color) 663
>
> Setting-Error: type read mismatch (color) 663
>
> Setting-Error: type read mismatch (color) 663
>
> Setting-Error: type read mismatch (color) 663
>
> Setting-Error: type read mismatch (color) 663
>
> Setting-Error: type read mismatch (color) 664
>
> Setting-Error: type read mismatch (color) 664
>
> Setting-Error: type read mismatch (color) 664
>
> Setting-Error: type read mismatch (color) 663
>
> Setting-Error: type read mismatch (color) 663
>
> Setting-Error: type read mismatch (color) 663
>
>
>
> If I then look in the settings using the GUI (‘edit all’), and filter-down
> using ‘bg_rgb’, I see that (for the values I have tried to modify) the
> original hex values are now represented as (presumably string
> representations) of lists of floats (ie like the settings used to be prior
> to version 1.6?!):
>
>
>
> bg_rgb 0x000000
>
> bg_rgb_bottom [ 0.00784, 0.00000, 0.00000 ]
>
> bg_rgb_top [ 0.01098, 0.01098, 0.00000 ]
>
>
>
>
>
> If I try to modify via the GUI, by entering a string hex-value, the change
> reverts to the list-type when I press the return key…
>
> This looks related to an existing thread (
> http://sourceforge.net/p/pymol/mailman/message/31473011/), where the
> final post suggests those issues were resolved in rev. 4043.
>
>
>
> Any help/advice would be greatly appreciated!
>
>
>
> Kind regards
>
>
>
> James
>
>
>
> ______________________________________________________________________
> PLEASE READ: This email is confidential and may be privileged. It is
> intended for the named addressee(s) only and access to it by anyone else is
> unauthorised. If you are not an addressee, any disclosure or copying of the
> contents of this email or any action taken (or not taken) in reliance on it
> is unauthorised and may be unlawful. If you have received this email in
> error, please notify the sender or postmas...@vernalis.com. Email is not
> a secure method of communication and the Company cannot accept
> responsibility for the accuracy or completeness of this message or any
> attachment(s). Please check this email for virus infection for which the
> Company accepts no responsibility. If verification of this email is sought
> then please request a hard copy. Unless otherwise stated, any views or
> opinions presented are solely those of the author and do not represent
> those of the Company.
>
> The Vernalis Group of Companies
> 100 Berkshire Place
> Wharfedale Road
> Winnersh, Berkshire
> RG41 5RD, England
> Tel: +44 (0)118 938 0000
>
> To access trading company registration and address details, please go to
> the Vernalis website at www.vernalis.com and click on the "Company
> address and registration details" link at the bottom of the page..
> ______________________________________________________________________
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> PyMOL-users mailing list (PyMOL-users@lists.sourceforge.net)
> Info Page: https://lists.sourceforge.net/lists/listinfo/pymol-users
> Archives: http://www.mail-archive.com/pymol-users@lists.sourceforge.net
>
--
Tsjerk A. Wassenaar, Ph.D.
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
PyMOL-users mailing list (PyMOL-users@lists.sourceforge.net)
Info Page: https://lists.sourceforge.net/lists/listinfo/pymol-users
Archives: http://www.mail-archive.com/pymol-users@lists.sourceforge.net
