Lookout

cancel
Showing results for 
Search instead for 
Did you mean: 

Lookout displays wrong graphics

Lookout 4.5.1 (18 & 19) sometimes
displays wrong graphics upon
opening a process.

For example it can display 'knifeup'
instead of cumstom .bmp or standard
switches pictures instead of custom
ones, etc.

At the same time .lks is OK.

I have Win98 system running on HP Omnibook XE3
Notebook.

Did anyone experienced the same
unpredictable Lookout behavior?

Sergei
0 Kudos
Message 1 of 10
(3,719 Views)
Yes, this is a regular problem for me in Lookout 5.0. I have not gotten around to calling customer support yet.

As far as I can tell, this only happens with custom graphics.

This is a bug for sure.

Regards,
Tommy Scharmann
0 Kudos
Message 2 of 10
(3,719 Views)
Tommy,

It also happens with customs graphics from
'standard' Lookout set like 'Indicatr', etc.

I just found out that wrong graphics display
occurs only when aggregate objects are used.

Did you notice the same?

Any ideas on workaround?

Regards,

Sergei



tommy_scharmann wrote:

> Yes, this is a regular problem for me in Lookout 5.0. I have not
> gotten around to calling customer support yet.
>
> As far as I can tell, this only happens with custom graphics.
>
> This is a bug for sure.
>
> Regards,
> Tommy Scharmann
>
0 Kudos
Message 3 of 10
(3,719 Views)
Yes- I have noticed it to be the process calling the aggregates.

I simply keep a copy of the lks file and when the problem arises I recompile from the script.

Regards,
Tommy Scharmann
0 Kudos
Message 4 of 10
(3,719 Views)
It seems this is a problem when nested aggregates are used. I was informed by the NI help line that nested aggregates are not recommended. The section in the help file that says aggregates can be nested is a mistake- according to NI.

Regards,
Tommy Scharmann
0 Kudos
Message 5 of 10
(3,719 Views)
That's not quite right.

NI sent me a fix and my nested aggregates
work fine now.

So the help file section on aggregates nesting
is not a mistake.

Best regards,
Sergei

tommy_scharmann wrote:

> It seems this is a problem when nested aggregates are used. I was
> informed by the NI help line that nested aggregates are not
> recommended. The section in the help file that says aggregates can be
> nested is a mistake- according to NI.
>
> Regards,
> Tommy Scharmann
>
0 Kudos
Message 6 of 10
(3,719 Views)
Sergi,

I would like to know who you spoke with at NI. It was very clearly told to me via the NI help line that nested aggregates are not to be used with Lookout and that if you use nested aggregates you will get unexpected behaviors. Unexpected behaviors included the graphics issues, amongst other things, that were not made clear to me. I was explicitly told that the help file mention of nested aggregates is erroneous!

Please help me to get to the bottom of this issue.

Regards,
Tommy Scharmann
0 Kudos
Message 7 of 10
(3,719 Views)
Tommy,

Obviously you got the NI advise on
not using nested aggregates at the
time they were investigating the problem.

Meantime I got a couple of similar replies
from NI as well.

Finally when I asked them to tell me if I can
expect the fix in near future (my project was
at high risk because I noticed the bug too late),
they sent me lkworks.dll for testing.

It all works fine now. I must admit that
NI 'saved' our project (we successfully launched it
at our plant last week).

I can send you the fix so you could test
it with your project. It would be interesting
to compare our results.

Please let me have your email so I could
send you the file.

Best regards,
Sergei

tommy_scharmann wrote:

> Sergi,
>
> I would like to know who you spoke with at
NI. It was very clearly
> told to me via the NI help line that nested aggregates are not to be
> used with Lookout and that if you use nested aggregates you will get
> unexpected behaviors. Unexpected behaviors included the graphics
> issues, amongst other things, that were not made clear to me. I was
> explicitly told that the help file mention of nested aggregates is
> erroneous!
>
> Please help me to get to the bottom of this issue.
>
> Regards,
> Tommy Scharmann
>
0 Kudos
Message 8 of 10
(3,719 Views)
Sergi,

I contacted the help line again. They pointed me to the ftp directory: ftp://ftp.ni.com/support/lookout/fixes/5.0/

I asked for the reason why nested aggregates are not recommended. They said it is simply a matter of complexity. No real technical reason why you cannot nest aggregates. This is not what I was told the first time I contacted the help line about this. So we can nest aggregates now with no worries!

Regards,
Tommy Scharmann
0 Kudos
Message 9 of 10
(3,719 Views)
Tommy,

That's the good news.

Regards,
Sergei

tommy_scharmann wrote:

> Sergi,
>
> I contacted the help line again. They pointed me to the ftp directory:
> ftp://ftp.ni.com/support/lookout/fixes/5.0/
>
> I asked for the reason why nested aggregates are not recommended. They
> said it is simply a matter of complexity. No real technical reason why
> you cannot nest aggregates. This is not what I was told the first time
> I contacted the help line about this. So we can nest aggregates now
> with no worries!
>
> Regards,
> Tommy Scharmann
>
0 Kudos
Message 10 of 10
(3,719 Views)