Lookout 6.2 Bugs

[erblock]

Why are Options\Modbus... and Options\Modbus Ethernet... menu items missing in Lookout 6.2?  Please put them back.

Ed

Message Edited by erblock on 04-09-2009 08:55 AM

[Ryan.S]

We don't remove them in Lookout 6.2... If you don't have Modbus object in process, you won't see these options. After you create Modbus object, they will come up.

[erblock]

Okay, Thanks Ryan!

I'm about to convert some processes to 6.2 and wanted to make sure before I did.  Makes sense I guess.

Ed

[Mike@DTSI]

New Bug

If Lookout is set to startup with the user logon, it crashes.  If setup in registry to run on user logon, it crashes.  We have a delayed start app loading lookout after logon, works correctly. Tested multiple times all failed excepted delayed starup method.

Windows Vista x64 SP1, Intel C2D, 4GB RAM, Non-admin user

Log Name:      Application
Source:        Application Error
Date:          4/14/2009 3:38:36 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      IWDSCADA09
Description:
Faulting application lookout.exe, version 6.2.0.49153, time stamp 0x48d055ac, faulting module LKSTIME.dll, version 6.0.6001.18000, time stamp 0x4791a783, exception code 0xc0000142, fault offset 0x0006ecfb, process id 0x92c, application start time 0x01c9bd519bd3ae05.

Thanks

Mike

[Ryan.S]

This may be the compatibility issue between Lookout and x64 vista. I tried both 64bit and 32bit. I got problem with 64, while 32 was fine.  

What if you set the service to "Automatic(delayed start)"?

[Mike@DTSI]

Ryan,

The Lookout program is set to only run with a specific user account.  Setting as a service runs at all times.  If I get a chance I will test it. Though it appears you have a test system too. 🙂  Our application waits 15 seconds after it loads to start Lookout currently, so Im sure a delayed start would likely work. Seems to fail looking for another service.

Thanks

Mike

[erblock]

I've had lots of crashes after "Save All" menu command while in edit mode.  Recently, the crashes were all after draging display objects to panels and/or copying objects between panels.  It is very repeatable.  Exiting edit mode prior to saves prevents crashes.

[erblock]

Lookout 6.2.  Server 2008 32-bit.  Window activates do not take position recorded in x and y connections.  They restore to last position regardless of x & y values set.  I have not seen this before, but it is totally repeatable in the process I'm developing now.  Process was completely developed on Server 2008  (panels were originally developed with Lookout 6.2 beta and Lookout was upgraded to Lookout 6.2 final recently with no issues), 32-bit machine and should behave just like Vista, yet I have not tested on Vista machine yet.  More testing to come...

[erblock]

Something is up with Panels in Lookout 6.2.

I took an older process file that was developed mostly in Lookout 6.1, but some of it was developed in Lookout 5.x.   I imported the process to the same machine problem was reported with.  All existing panels act like expected.  However, when I create a new panel under Lookout 6.2, the new panel exhibits wrong behavior and activates at last position regardless of what x & y connections are set.

Confirmation and fix please?

Ed

[erblock]

Further investigation reveals...

x and y connection positions are only "saved" within a running process if panel type "Popup no icon" is chosen.  If "Popup" is chosen, windows are restored to last position except at process startup, at which time the connected x & y values will be used.

Sorry for the false alarm, I assume this is intended function and It had been so long since I cared about this panel control.  My bad...