Lookout 6.2 Bugs

[erblock]

I found a couple of small bugs in the DataTable object.

1.  Whenever you  first "Edit Data Member Configuration" of a new DataTable object, the default data member is logical.  That is ok, but when you change the pulldown type to numeric, the display does not expand to show historical, filter and alarm options as it should. You need to quit the configuration and re-enter to get the proper setup and options for numeric data members.

2.  The DataTable allows import of bad "Alias" fields.  I had a few fields in several hundred that were imported with a space at the end of the alias name.  They all imported just fine.  The problem comes when you want to edit or delete those bad entries...you CAN'T do it interactively.  More importantly, you can't make a connection to these bad entries, so my guess is that although they exist in your display, they are likely totally non-funtional!  The only way to remove the bad data members is to import a "delete" entry with the same alias field error.

Ed

Message Edited by erblock on 01-14-2009 05:04 PM

[Ryan.S]

1. I think it is because the default selected datamember is the first one, 1.1-10000.64. It is logic value. It is not readable, so there is no historical, alarm, etc.

2. I will check this one.

Thank you.

[erblock]

"1. I think it is because the default selected datamember is the first one, 1.1-10000.64. It is logic value. It is not readable, so there is no historical, alarm, etc. "

This used to work properly as long as you typed a member that was numeric and then selected the numeric pull down, the other displays would show.  I know for sure that they would show once you "saved" a numeric member without quiting and re-opening the Edit Data Member dialog.  Not a big deal, but definitely a change in behavior at some point....since Lookout....5 or 6?

Cheers,

Ed

[Ryan.S]

I see. Lookout 4 worked as you said. Since Lookout 5, it has been changed. I'm not sure why, but looks like a bug.

Message Edited by Ryan.S on 01-16-2009 01:09 AM

[erblock]

Hi,

It appears cbl.exe behavior has changed in Lookout 6.2.  When using the command line to attempt compiling a currupt .lks file, the compile appears to complete without error but no .err file is written and errors are not listed in the command window.  Of course the .l4p file is also not produced.  The .err file is produced if the compile is succesful.

Please fix this.

Errors are listed when you use lookout to open flawed .lks file.

Thanks,

Ed

[Ryan.S]

What kind of corrupt .lks file it is? I add some syntax errors, and input

cbl process1.lks process1.l4p cbl.err

I don't get error in cmd windows, but cbl.err is generated with errors.

I also tested lookout6.0, it has the same behavior.

The only difference in lookout 6.2 is that the cbl.exe will not work after the evaluation expires and no product is activated.

[erblock]

Hi Ryan,

They were "Object not defined" errors.

I like the "new" error listing in the Lookout GUI when compiling an .lks file, however, I do miss not seeing the errors in the command window when using cbl.exe from command line, and I was disturbed that no errors were announced in this case.

Ed

[Ryan.S]

Let's confirm two things first.

1. The cmd windows doesn't report error. The error will be written in the file. It is how lookout works from version 5.x.

2. Do you see the error be written to the file? If there is no file be written, this is the problem.

I try to add the "object not defined" error to a lks file. In Lookout, I get

C:\Program Files\National Instruments\Lookout 5.1\default.lks
C:\Program Files\National Instruments\Lookout 5.1\default.lks(50): error: Object is not defined: Panel10

If I compile it from cmd, the same messages will be written to the file.

Lookout 6.2 has the same behaviour as previous version.

[erblock]

Ryan,

Lookout 6.1 command window test:

1.  Edit default.lks object "Pb1" name to "Pb0" and save file.

2.  Run cbl.exe to attemp compile:  See copied command window history below in blue.

 C:\Program Files\National Instruments\Lookout 6.1>cbl default.lks default.
l4p

Lookout Process File Compiler Version 6.1 (build 3)
Copyright National Instruments 1992-2007  All rights reserved.

default.lks
default.lks(53): error: Object is not defined: Pb1

C:\Program Files\National Instruments\Lookout 6.1>

3.  cbl.err file is NOT written  to file and error IS listed in command window.

Additionally, I tried this on Lookout 6.2 (cbl build 49153) on a different machine than the machine used to originally report this issue and it gives nearly the same results in blue below.

C:\Program Files\National Instruments\Lookout 6.2>cbl default.lks default.l4p

Lookout Process File Compiler Version 6.2 (build 49153)
Copyright National Instruments 1992-2008  All rights reserved.

default.lks
default.lks(239): error: Object is not defined: Pb1

C:\Program Files\National Instruments\Lookout 6.2>

Ironically, the above behaviors are as expected, and contradict both my original issue and your last post.

Now I am officially confused!

 Ed

[Ryan.S]

Ed,

Without checking the source code, I get the following result from some tests.

cbl.exe has three parameters. If you input

cbl xxx.lks xxx.l4p

the error will be in the cmd windows.

But if you input

cbl xxx.lks xxx.l4p cbl.err

you will get no error in the cmd window, but will have the cbl.err file written.

Have a test on your computer. If you get the same behaviour, it is expected and correct.

I'm not sure what's wrong with your original issue. Did you input two paramters or three?