date:20151213

Re: [Jmol-users] Jmol 14.4.1_2015.12.13 released - IMPORTANT

2015-12-13 Thread Robert Hanson

Sorry about the link - I ended up changing that (original, broken) link
from "jsmol2" to http://chemapps.stolaf.edu/jmol/jsmol-2015-12-13/jsmol.htm

Yes, Fausto, that is correct. It was an easy fix, at least for a first try.
We have to see if this sluggishness returns in additional cases, but for
the most part this seems to take care of it.
--
___
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users

Re: [Jmol-users] Jmol 14.4.1_2015.12.13 released - IMPORTANT

2015-12-13 Thread J. Bays

That dates us Otis😩

J. Philip Bays
Emeritus Professor of Chemistry
Saint Mary's College
Norte Dame, IN

Sent from my iPad

> On Dec 13, 2015, at 4:04 PM, Otis Rothenberger  wrote:
>
> I’m probably not supposed to do this, but the words of Mighty Mouse seem 
> appropriate to yet another Hanson save:
>
> MIGHTY MOUSE THEME SONG
> (Philip Scheib / Marshall Barer) - circa 1955
>
> "Mr. trouble never hangs around,
> when he hears this Mighty sound,
>
> Here I come to save the day!
> That means that Mighty Mouse is on the way!
>
> Yes sir, when there is a wrong to right,
> Mighty Mouse will join the fight!…”
>
> Otis
>
> --
> Otis Rothenberger
> o...@chemagic.com
> http://chemagic.com
>
>
>
>
>
> --
> ___
> Jmol-users mailing list
> Jmol-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jmol-users

--
___
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users

Re: [Jmol-users] Jmol 14.4.1_2015.12.13 released - IMPORTANT

2015-12-13 Thread Otis Rothenberger

I’m probably not supposed to do this, but the words of Mighty Mouse seem 
appropriate to yet another Hanson save:

MIGHTY MOUSE THEME SONG
(Philip Scheib / Marshall Barer) - circa 1955

"Mr. trouble never hangs around,
when he hears this Mighty sound,

Here I come to save the day!
That means that Mighty Mouse is on the way!

Yes sir, when there is a wrong to right,
Mighty Mouse will join the fight!…”

Otis

--
Otis Rothenberger
o...@chemagic.com
http://chemagic.com





--
___
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users

Re: [Jmol-users] Jmol 14.4.1_2015.12.13 released - IMPORTANT

2015-12-13 Thread Philip Bays

I concur with Otis, at least on my local server.

Phil

> On Dec 13, 2015, at 2:42 PM, Otis Rothenberger  wrote:
> 
> Bob,
> 
>  http://chemapps.stolaf.edu/jmol/jsmol/jsmol.htm 
>    on Chrome Mac (Latest 
> versions OS and Chrome) works fine after cache clear.
> 
> On my site, I swapped out JSmol.min.nojq.js and this also works fine after 
> cache clear.
> 
> “Fine” means a quick check. I’ll play around a bit to make sure.
> 
> Otis
> 
> --
> Otis Rothenberger
> o...@chemagic.com 
> http://chemagic.com
> 
>> On Dec 13, 2015, at 1:56 PM, Robert Hanson > > wrote:
>> 
>> This new version is now available at SourceForge:
>> 
>> Download Jmol-14.4.1_2015.12.13-binary.zip (60.3 MB) 
>> 
>> 
>> 
>> IMPORTANT: A very recent modification of Chrome makes Chrome unusable with 
>> all previous versions of JSmol, at least until sometime in January. The 
>> WebGL version of JSmol is not impacted. 
>> 
>> This appears to be the result of a well-meaning attempt by Chromium 
>> developers to enhance smooth scrolling of pages by lowering the priority of 
>> setTimeout calls. However, the unanticipated fallout of that change results 
>> in extremely rough rotation of models. You can follow the issue here: 
>> https://code.google.com/p/chromium/issues/detail?id=568725 
>>   Note that one 
>> of the last comments on Dec. 11 indicates that there indicates this issue 
>> will not be addressed until sometime in January. 
>> 
>> But there is a workaround. This release of Jmol 14.4.1 should correct that 
>> problem and, at the same time, may improve performance with Microsoft Edge. 
>> 
>> I have put up two versions of JSmol that illustrate the problem and the fix:
>> 
>> (original) http://chemapps.stolaf.edu/jmol/jsmol/jsmol.htm 
>> 
>> (fixed) http://chemapps.stolaf.edu/jmol/jsmol2/jsmol.htm 
>> 
>> 
>> Testing of that second site would be appreciated.
>> 
>> The work-around is simple, and if you want, you can implement this yourself 
>> on your site.  Really (in terms of this bug) it is just a single coding 
>> change in jsmol/js/JSmol.js, where one "setTimeout(f)" has been replaced 
>> with "requestAnimationFrame(f)". Thus, if you prefer, you should be able to 
>> just swap in a new JSmol.min.js or JSmol.min.nojq.js for the old one. I have 
>> not tried this. Of course, if you do that, then the other bugs listed below 
>> will still be there. If you want to try that, here is the link to that file 
>> specifically:
>> 
>> http://chemapps.stolaf.edu/jmol/jsmol2/JSmol.min.js 
>> 
>> 
>> Bob
>> 
>> Jmol.___JmolVersion="14.4.1_2015.12.13"
>> 
>> bug fix: JavaScript Chrome/Edge fix for slow response due to setTimeout 
>> issues; uses requestAnimationFrame instead in JSmol.js 
>> bug fix: zoomTo not setting time to 0 in the case of scriptWait
>> bug fix: set selectAllModels should restrict action of display/hide as well
>> bug fix: set selectAllModels not working appropriately
>> bug fix: set selectAllModels should not be saved in state
>> bug fix: JmolData.jar does not update atom screen positions upon REFRESH or 
>> select {visible}
>> bug fix: JmolData.jar -p flag does not work properly
>> bug fix: model 0 issued when more than one PDB file is open does not execute 
>> model *
>> 
>> -- 
>> Robert M. Hanson
>> Larson-Anderson Professor of Chemistry
>> Chair, Department of Chemistry
>> St. Olaf College
>> Northfield, MN
>> http://www.stolaf.edu/people/hansonr 
>> 
>> 
>> If nature does not answer first what we want,
>> it is better to take what answer we get. 
>> 
>> -- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900
>> 
>> --
>> ___
>> Jmol-users mailing list
>> Jmol-users@lists.sourceforge.net 
>> https://lists.sourceforge.net/lists/listinfo/jmol-users
> 
> --
> ___
> Jmol-users mailing list
> Jmol-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jmol-users

Philip Bays
Emeritus Professor of Chemistry
Saint Mary's College
Notre Dame, IN 46556
pb...@saintmarys.edu


--
___
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users

Re: [Jmol-users] Jmol 14.4.1_2015.12.13 released - IMPORTANT

2015-12-13 Thread Otis Rothenberger

Bob,

 http://chemapps.stolaf.edu/jmol/jsmol/jsmol.htm 
   on Chrome Mac (Latest 
versions OS and Chrome) works fine after cache clear.

On my site, I swapped out JSmol.min.nojq.js and this also works fine after 
cache clear.

“Fine” means a quick check. I’ll play around a bit to make sure.

Otis

--
Otis Rothenberger
o...@chemagic.com
http://chemagic.com

> On Dec 13, 2015, at 1:56 PM, Robert Hanson  wrote:
> 
> This new version is now available at SourceForge:
> 
> Download Jmol-14.4.1_2015.12.13-binary.zip (60.3 MB) 
> 
> 
> 
> IMPORTANT: A very recent modification of Chrome makes Chrome unusable with 
> all previous versions of JSmol, at least until sometime in January. The WebGL 
> version of JSmol is not impacted. 
> 
> This appears to be the result of a well-meaning attempt by Chromium 
> developers to enhance smooth scrolling of pages by lowering the priority of 
> setTimeout calls. However, the unanticipated fallout of that change results 
> in extremely rough rotation of models. You can follow the issue here: 
> https://code.google.com/p/chromium/issues/detail?id=568725 
>   Note that one 
> of the last comments on Dec. 11 indicates that there indicates this issue 
> will not be addressed until sometime in January. 
> 
> But there is a workaround. This release of Jmol 14.4.1 should correct that 
> problem and, at the same time, may improve performance with Microsoft Edge. 
> 
> I have put up two versions of JSmol that illustrate the problem and the fix:
> 
> (original) http://chemapps.stolaf.edu/jmol/jsmol/jsmol.htm 
> 
> (fixed) http://chemapps.stolaf.edu/jmol/jsmol2/jsmol.htm 
> 
> 
> Testing of that second site would be appreciated.
> 
> The work-around is simple, and if you want, you can implement this yourself 
> on your site.  Really (in terms of this bug) it is just a single coding 
> change in jsmol/js/JSmol.js, where one "setTimeout(f)" has been replaced with 
> "requestAnimationFrame(f)". Thus, if you prefer, you should be able to just 
> swap in a new JSmol.min.js or JSmol.min.nojq.js for the old one. I have not 
> tried this. Of course, if you do that, then the other bugs listed below will 
> still be there. If you want to try that, here is the link to that file 
> specifically:
> 
> http://chemapps.stolaf.edu/jmol/jsmol2/JSmol.min.js 
> 
> 
> Bob
> 
> Jmol.___JmolVersion="14.4.1_2015.12.13"
> 
> bug fix: JavaScript Chrome/Edge fix for slow response due to setTimeout 
> issues; uses requestAnimationFrame instead in JSmol.js 
> bug fix: zoomTo not setting time to 0 in the case of scriptWait
> bug fix: set selectAllModels should restrict action of display/hide as well
> bug fix: set selectAllModels not working appropriately
> bug fix: set selectAllModels should not be saved in state
> bug fix: JmolData.jar does not update atom screen positions upon REFRESH or 
> select {visible}
> bug fix: JmolData.jar -p flag does not work properly
> bug fix: model 0 issued when more than one PDB file is open does not execute 
> model *
> 
> -- 
> Robert M. Hanson
> Larson-Anderson Professor of Chemistry
> Chair, Department of Chemistry
> St. Olaf College
> Northfield, MN
> http://www.stolaf.edu/people/hansonr 
> 
> 
> If nature does not answer first what we want,
> it is better to take what answer we get. 
> 
> -- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900
> 
> --
> ___
> Jmol-users mailing list
> Jmol-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jmol-users

--
___
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users

Re: [Jmol-users] Jmol 14.4.1_2015.12.13 released - IMPORTANT

2015-12-13 Thread trematodeo

Hi Bob,

I need to ask because it's still confusing to me, the problem with the new
chrome version is when you drag - rotate - some model on the screen using
the mouse?

I updated my chrome and that's the problem I'm facing in my page. The model
rotation isn't smooth anymore.

To fix I need to update to the last jmol version?

I don't know about the chrome internals but seems to be a bad decision from
google, I'm glad that you have found a way to fix this, thanks.

Best regards
Fausto

On 13 December 2015 at 14:05, lisensky  wrote:

> I am getting a file not found for
> (fixed) http://chemapps.stolaf.edu/jmol/jsmol2/jsmol.htm
>
> Did you post it?
>
> Thanks for working on this Chrome issue?
>
>
> --
> George Lisensky lisen...@beloit.edu
> Chemistry Department608-363-2225
> Beloit College  fax 608-363-2052
> 700 College Street
> Beloit, WI 53511
>
> http://chemistry.beloit.edu/classes/lisensky
>
>
>
> --
> ___
> Jmol-users mailing list
> Jmol-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jmol-users
>
--
___
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users

Re: [Jmol-users] Jmol 14.4.1_2015.12.13 released - IMPORTANT

2015-12-13 Thread lisensky

I am getting a file not found for
(fixed) http://chemapps.stolaf.edu/jmol/jsmol2/jsmol.htm

Did you post it?

Thanks for working on this Chrome issue?


-- 
George Lisensky lisen...@beloit.edu
Chemistry Department608-363-2225
Beloit College  fax 608-363-2052
700 College Street
Beloit, WI 53511

http://chemistry.beloit.edu/classes/lisensky


--
___
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users

Re: [Jmol-users] Jmol 14.4.1_2015.12.13 released - IMPORTANT

2015-12-13 Thread Robert Hanson

[slight correction]


(fixed) http://chemapps.stolaf.edu/jmol/jsmol/jsmol.htm
(original) http://chemapps.stolaf.edu/jmol/jsmol-2015-12-13/jsmol.htm

On Sun, Dec 13, 2015 at 12:56 PM, Robert Hanson  wrote:

> This new version is now available at SourceForge:
>
> *Download Jmol-14.4.1_2015.12.13-binary.zip (60.3 MB)
> *
>
>
> *IMPORTANT*: A very recent modification of Chrome makes Chrome unusable
> with all previous versions of JSmol, at least until sometime in January.
> The WebGL version of JSmol is not impacted.
>
> This appears to be the result of a well-meaning attempt by Chromium
> developers to enhance smooth scrolling of pages by lowering the priority of
> setTimeout calls. However, the unanticipated fallout of that change results
> in extremely rough rotation of models. You can follow the issue here:
> https://code.google.com/p/chromium/issues/detail?id=568725  Note that one
> of the last comments on Dec. 11 indicates that there indicates this issue
> will not be addressed until sometime in January.
>
> *But there is a workaround. *This release of Jmol 14.4.1 should correct
> that problem and, at the same time, may improve performance with Microsoft
> Edge.
>
> I have put up two versions of JSmol that illustrate the problem and the
> fix:
>
> (original) http://chemapps.stolaf.edu/jmol/jsmol/jsmol.htm
> (fixed) http://chemapps.stolaf.edu/jmol/jsmol2/jsmol.htm
>
> Testing of that second site would be appreciated.
>
> The work-around is simple, and if you want, you can implement this
> yourself on your site.  Really (in terms of this bug) it is just a single
> coding change in jsmol/js/JSmol.js, where one "setTimeout(f)" has been
> replaced with "requestAnimationFrame(f)". Thus, if you prefer, you should
> be able to just swap in a new JSmol.min.js or JSmol.min.nojq.js for the old
> one. I have not tried this. Of course, if you do that, then the other bugs
> listed below will still be there. If you want to try that, here is the link
> to that file specifically:
>
> http://chemapps.stolaf.edu/jmol/jsmol2/JSmol.min.js
>
> Bob
>
> Jmol.___JmolVersion="14.4.1_2015.12.13"
>
> bug fix: JavaScript Chrome/Edge fix for slow response due to setTimeout
> issues; uses requestAnimationFrame instead in JSmol.js
> bug fix: zoomTo not setting time to 0 in the case of scriptWait
> bug fix: set selectAllModels should restrict action of display/hide as well
> bug fix: set selectAllModels not working appropriately
> bug fix: set selectAllModels should not be saved in state
> bug fix: JmolData.jar does not update atom screen positions upon REFRESH
> or select {visible}
> bug fix: JmolData.jar -p flag does not work properly
> bug fix: model 0 issued when more than one PDB file is open does not
> execute model *
>
> --
> Robert M. Hanson
> Larson-Anderson Professor of Chemistry
> Chair, Department of Chemistry
> St. Olaf College
> Northfield, MN
> http://www.stolaf.edu/people/hansonr
>
>
> If nature does not answer first what we want,
> it is better to take what answer we get.
>
> -- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900
>
>


-- 
Robert M. Hanson
Larson-Anderson Professor of Chemistry
Chair, Department of Chemistry
St. Olaf College
Northfield, MN
http://www.stolaf.edu/people/hansonr


If nature does not answer first what we want,
it is better to take what answer we get.

-- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900
--
___
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users

Re: [Jmol-users] Fwd: Chrome: rotation unusable in JSmol

2015-12-13 Thread Robert Hanson

See my other message -- 14.4.1 fixes this.

On Sun, Dec 13, 2015 at 10:13 AM, Robert Hanson  wrote:

> Just to be clear, what is happening is that a recent feature of Chrome is
> that if a mouse event triggers a setTimeout, the system is monitored for
> how long it takes to process, and if that process time exceeds some
> threshold, then from that time forward setTimeout processing is given a
> lower priority. In our case, it means that all updating of the display is
> put off until the mouse is let go. From
>
> https://code.google.com/p/chromium/issues/detail?id=568725
>
> #20 
> alexcla...@chromium.org 
>
> As much as possible chrome tries to do scrolling and animation on the 
> compositor thread to try and make them smooth even when the mainthread is 
> very unresponsive.   Various things that can't be done by the compositor, 
> e.g, running the layout pipeline (which has to be done on the main thread).
>
> In the context of this patch, a 'frame' is generated when the compositor asks 
> the main thread to run the layout pipeline by posting a task to run 
> BeingMainFrame. If animations stop and no more frames are needed the 
> compositor will tell the main thread by calling BeginFrameNotExpectedSoon.  
> When that happens the scheduler stops trying to optimize for fps.
>
> Under some circumstances Chrome will block loading and or timer tasks, if it 
> thinks there's more important work pending.  The details of this are 
> complicated (I hope to document this properly in a public doc/blogpost), and 
> it's quite possible it's not working well in all cases.
>
> What would be really useful is a link to the web application (even a cut down 
> version) or a trace.  Then we can investigate and potentially make fixes if 
> the scheduler is doing the wrong thing.
>
> PS the scheduler team is now out till January, but I will be sure to follow 
> up if you can send us anything more.
>
>
>
> 
>



-- 
Robert M. Hanson
Larson-Anderson Professor of Chemistry
Chair, Department of Chemistry
St. Olaf College
Northfield, MN
http://www.stolaf.edu/people/hansonr


If nature does not answer first what we want,
it is better to take what answer we get.

-- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900
--
___
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users

[Jmol-users] Jmol 14.4.1_2015.12.13 released - IMPORTANT

2015-12-13 Thread Robert Hanson

This new version is now available at SourceForge:

*Download Jmol-14.4.1_2015.12.13-binary.zip (60.3 MB)
*


*IMPORTANT*: A very recent modification of Chrome makes Chrome unusable
with all previous versions of JSmol, at least until sometime in January.
The WebGL version of JSmol is not impacted.

This appears to be the result of a well-meaning attempt by Chromium
developers to enhance smooth scrolling of pages by lowering the priority of
setTimeout calls. However, the unanticipated fallout of that change results
in extremely rough rotation of models. You can follow the issue here:
https://code.google.com/p/chromium/issues/detail?id=568725  Note that one
of the last comments on Dec. 11 indicates that there indicates this issue
will not be addressed until sometime in January.

*But there is a workaround. *This release of Jmol 14.4.1 should correct
that problem and, at the same time, may improve performance with Microsoft
Edge.

I have put up two versions of JSmol that illustrate the problem and the fix:

(original) http://chemapps.stolaf.edu/jmol/jsmol/jsmol.htm
(fixed) http://chemapps.stolaf.edu/jmol/jsmol2/jsmol.htm

Testing of that second site would be appreciated.

The work-around is simple, and if you want, you can implement this yourself
on your site.  Really (in terms of this bug) it is just a single coding
change in jsmol/js/JSmol.js, where one "setTimeout(f)" has been replaced
with "requestAnimationFrame(f)". Thus, if you prefer, you should be able to
just swap in a new JSmol.min.js or JSmol.min.nojq.js for the old one. I
have not tried this. Of course, if you do that, then the other bugs listed
below will still be there. If you want to try that, here is the link to
that file specifically:

http://chemapps.stolaf.edu/jmol/jsmol2/JSmol.min.js

Bob

Jmol.___JmolVersion="14.4.1_2015.12.13"

bug fix: JavaScript Chrome/Edge fix for slow response due to setTimeout
issues; uses requestAnimationFrame instead in JSmol.js
bug fix: zoomTo not setting time to 0 in the case of scriptWait
bug fix: set selectAllModels should restrict action of display/hide as well
bug fix: set selectAllModels not working appropriately
bug fix: set selectAllModels should not be saved in state
bug fix: JmolData.jar does not update atom screen positions upon REFRESH or
select {visible}
bug fix: JmolData.jar -p flag does not work properly
bug fix: model 0 issued when more than one PDB file is open does not
execute model *

-- 
Robert M. Hanson
Larson-Anderson Professor of Chemistry
Chair, Department of Chemistry
St. Olaf College
Northfield, MN
http://www.stolaf.edu/people/hansonr


If nature does not answer first what we want,
it is better to take what answer we get.

-- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900
--
___
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users

Re: [Jmol-users] Fwd: Chrome: rotation unusable in JSmol

2015-12-13 Thread Robert Hanson

Just to be clear, what is happening is that a recent feature of Chrome is
that if a mouse event triggers a setTimeout, the system is monitored for
how long it takes to process, and if that process time exceeds some
threshold, then from that time forward setTimeout processing is given a
lower priority. In our case, it means that all updating of the display is
put off until the mouse is let go. From

https://code.google.com/p/chromium/issues/detail?id=568725

#20 
alexcla...@chromium.org 

As much as possible chrome tries to do scrolling and animation on the
compositor thread to try and make them smooth even when the mainthread
is very unresponsive.   Various things that can't be done by the
compositor, e.g, running the layout pipeline (which has to be done on
the main thread).

In the context of this patch, a 'frame' is generated when the
compositor asks the main thread to run the layout pipeline by posting
a task to run BeingMainFrame. If animations stop and no more frames
are needed the compositor will tell the main thread by calling
BeginFrameNotExpectedSoon.  When that happens the scheduler stops
trying to optimize for fps.

Under some circumstances Chrome will block loading and or timer tasks,
if it thinks there's more important work pending.  The details of this
are complicated (I hope to document this properly in a public
doc/blogpost), and it's quite possible it's not working well in all
cases.

What would be really useful is a link to the web application (even a
cut down version) or a trace.  Then we can investigate and potentially
make fixes if the scheduler is doing the wrong thing.

PS the scheduler team is now out till January, but I will be sure to
follow up if you can send us anything more.




--
___
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users

Re: [Jmol-users] jmolScriptWait vs zoomTo

2015-12-13 Thread Robert Hanson

fixed

On Sun, Dec 13, 2015 at 7:42 AM, Robert Hanson  wrote:

> Probably a bug that the rest of the script is not executed, but there's no
> way to wait for a zoomto. Don't do that.
>
> On Sat, Dec 12, 2015 at 6:33 PM, Eric Martz 
> wrote:
>
>> Consider the following commands:
>>
>> zoomto *1.3;
>> select protein;
>> color yellow;
>>
>> In javascript, when these commands are in the string "spt",
>> jmolScript(spt)
>> produces a smooth zoom followed by protein turning yellow.
>>
>> However,
>> jmolScriptWait(spt)
>> produces a zoom in one large step (snap zoom) and the remainder of the
>> script is not executed (protein does not turn yellow).
>>
>> Is this a bug or a feature of jmolScriptWait()?
>>
>> Thanks, Eric
>>
>>
>> --
>> ___
>> Jmol-users mailing list
>> Jmol-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/jmol-users
>>
>
>
>
> --
> Robert M. Hanson
> Larson-Anderson Professor of Chemistry
> Chair, Department of Chemistry
> St. Olaf College
> Northfield, MN
> http://www.stolaf.edu/people/hansonr
>
>
> If nature does not answer first what we want,
> it is better to take what answer we get.
>
> -- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900
>
>


-- 
Robert M. Hanson
Larson-Anderson Professor of Chemistry
Chair, Department of Chemistry
St. Olaf College
Northfield, MN
http://www.stolaf.edu/people/hansonr


If nature does not answer first what we want,
it is better to take what answer we get.

-- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900
--
___
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users

Re: [Jmol-users] jmolScriptWait vs zoomTo

2015-12-13 Thread Eric Martz


OK, no problem. Thanks, Bob! -Eric

On 12/13/15 8:42 AM, Robert Hanson wrote:
Probably a bug that the rest of the script is not executed, but 
there's no way to wait for a zoomto. Don't do that.


On Sat, Dec 12, 2015 at 6:33 PM, Eric Martz > wrote:


Consider the following commands:

zoomto *1.3;
select protein;
color yellow;

In javascript, when these commands are in the string "spt",
jmolScript(spt)
produces a smooth zoom followed by protein turning yellow.

However,
jmolScriptWait(spt)
produces a zoom in one large step (snap zoom) and the remainder of the
script is not executed (protein does not turn yellow).

Is this a bug or a feature of jmolScriptWait()?

Thanks, Eric


--
___
Jmol-users mailing list
Jmol-users@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/jmol-users




--
Robert M. Hanson
Larson-Anderson Professor of Chemistry
Chair, Department of Chemistry
St. Olaf College
Northfield, MN
http://www.stolaf.edu/people/hansonr


If nature does not answer first what we want,
it is better to take what answer we get.

-- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900



--


___
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users


--
___
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users

Re: [Jmol-users] jmolScriptWait vs zoomTo

2015-12-13 Thread Robert Hanson

Probably a bug that the rest of the script is not executed, but there's no
way to wait for a zoomto. Don't do that.

On Sat, Dec 12, 2015 at 6:33 PM, Eric Martz 
wrote:

> Consider the following commands:
>
> zoomto *1.3;
> select protein;
> color yellow;
>
> In javascript, when these commands are in the string "spt",
> jmolScript(spt)
> produces a smooth zoom followed by protein turning yellow.
>
> However,
> jmolScriptWait(spt)
> produces a zoom in one large step (snap zoom) and the remainder of the
> script is not executed (protein does not turn yellow).
>
> Is this a bug or a feature of jmolScriptWait()?
>
> Thanks, Eric
>
>
> --
> ___
> Jmol-users mailing list
> Jmol-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jmol-users
>



-- 
Robert M. Hanson
Larson-Anderson Professor of Chemistry
Chair, Department of Chemistry
St. Olaf College
Northfield, MN
http://www.stolaf.edu/people/hansonr


If nature does not answer first what we want,
it is better to take what answer we get.

-- Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900
--
___
Jmol-users mailing list
Jmol-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jmol-users

Re: [Jmol-users] Jmol 14.4.1_2015.12.13 released - IMPORTANT

Re: [Jmol-users] Jmol 14.4.1_2015.12.13 released - IMPORTANT

Re: [Jmol-users] Jmol 14.4.1_2015.12.13 released - IMPORTANT

Re: [Jmol-users] Jmol 14.4.1_2015.12.13 released - IMPORTANT

Re: [Jmol-users] Jmol 14.4.1_2015.12.13 released - IMPORTANT

Re: [Jmol-users] Jmol 14.4.1_2015.12.13 released - IMPORTANT

Re: [Jmol-users] Jmol 14.4.1_2015.12.13 released - IMPORTANT

Re: [Jmol-users] Jmol 14.4.1_2015.12.13 released - IMPORTANT

Re: [Jmol-users] Fwd: Chrome: rotation unusable in JSmol

[Jmol-users] Jmol 14.4.1_2015.12.13 released - IMPORTANT

Re: [Jmol-users] Fwd: Chrome: rotation unusable in JSmol

Re: [Jmol-users] jmolScriptWait vs zoomTo

Re: [Jmol-users] jmolScriptWait vs zoomTo

Re: [Jmol-users] jmolScriptWait vs zoomTo

14 matches

Site Navigation

Mail list logo

Footer information