[PyMOL] Problems setting bg_rgb_top / bg_rgb_bottom
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:
PyMOLtop = cmd.get(bg_rgb_top)
PyMOLbottom = cmd.get(bg_rgb_bottom)
PyMOLprint top, bottom
0x4d 0x80
PyMOLcmd.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
PyMOLcmd.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 0x00
bg_rgb_bottom[ 0.00784, 0.0, 0.0 ]
bg_rgb_top[ 0.01098, 0.01098, 0.0 ]
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
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=154622311iu=/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
Re: [PyMOL] Problems setting bg_rgb_top / bg_rgb_bottom
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: PyMOLtop = cmd.get(bg_rgb_top) PyMOLbottom = cmd.get(bg_rgb_bottom) PyMOLprint top, bottom 0x4d 0x80 PyMOLcmd.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 PyMOLcmd.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 0x00 bg_rgb_bottom[ 0.00784, 0.0, 0.0 ] bg_rgb_top[ 0.01098, 0.01098, 0.0 ] 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 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
Re: [PyMOL] Problems setting bg_rgb_top / bg_rgb_bottom
Hi James, this was fixed in SVN rev 4094. So you may try the latest code from SVN, or apply the fix to your 1.7.0.2 code base. It's the first junk in this patch: http://sourceforge.net/p/pymol/code/4094/tree//trunk/pymol/layer1/Setting.cpp?diff=50c0fc56e88f3d0bdf694277:4093 Cheers, Thomas On 08 Oct 2014, at 03:27, 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: PyMOLtop = cmd.get(bg_rgb_top) PyMOLbottom = cmd.get(bg_rgb_bottom) PyMOLprint top, bottom 0x4d 0x80 PyMOLcmd.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 PyMOLcmd.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 0x00 bg_rgb_bottom[ 0.00784, 0.0, 0.0 ] bg_rgb_top[ 0.01098, 0.01098, 0.0 ] 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 -- Thomas Holder PyMOL Developer Schrödinger, Inc. -- 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=154622311iu=/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
