On 04/17/2015 06:47 PM, Rolf Huehne wrote:
> On 04/17/2015 01:44 PM, Rolf Huehne wrote:
>> Hi all,
>>
>> I have some problems debugging a complex script in Jmol.
>>
>> First of all, the command 'set scriptReportingLevel' doesn't seem to
>> work in Jmol 14.3.13_2015.04.08. It is always setting the v
On Fri, Apr 17, 2015 at 6:44 AM, Rolf Huehne wrote:
> Hi all,
>
> I have some problems debugging a complex script in Jmol.
>
> First of all, the command 'set scriptReportingLevel' doesn't seem to
> work in Jmol 14.3.13_2015.04.08. It is always setting the value to zero.
>
> Q: What do the numbers
On 04/17/2015 01:44 PM, Rolf Huehne wrote:
> Hi all,
>
> I have some problems debugging a complex script in Jmol.
>
> First of all, the command 'set scriptReportingLevel' doesn't seem to
> work in Jmol 14.3.13_2015.04.08. It is always setting the value to zero.
>
> Q: What do the numbers (e.g.: $[2
On 04/17/2015 01:44 PM, Rolf Huehne wrote:
> Replacing the old syntax by the new one "for (var fileNumber FROM [1
> fileCount]) {" dosen't change the problematic behaviour. The only
> visible difference can be seen in the case of the additional loop run.
> With the old syntax 'fileNumber' is "1" in
Hi all,
I have some problems debugging a complex script in Jmol.
First of all, the command 'set scriptReportingLevel' doesn't seem to
work in Jmol 14.3.13_2015.04.08. It is always setting the value to zero.
Q: What do the numbers (e.g.: $[2.295.299]) in the debugging output
after the command '
