[Openroad-users] OpenROAD runtime error handling
Simon Lovell
simonl at unwired.com.au
Tue Jun 19 10:54:15 EST 2007
No, there is no good way.
Perhaps every 5 seconds check to see if the w4gl.log file exists, and if it does, load it into a stringobject and append it to a back up file, remove the file and give the user a popup. Also requires disabling closing of the trace window and preferably removing the visibility of it. This last part was discussed a year or two ago.
Perhaps Ingres Corp could come up with a better idea than the trace window for trapping runtime errors, like divide by 0 etc. ABF handled it well enough.
-----Original Message-----
From: "Robert Allely" [allelyr at axis-intermodal.co.nz]
Date: 19/06/2007 08:35 AM
To: "International OpenROAD Users" <openroad-users at peerlessit.com>
Subject: [Openroad-users] OpenROAD runtime error handling
Note: Original message sent as attachment
-------------- next part --------------
An embedded message was scrubbed...
From: "Robert Allely" <allelyr at axis-intermodal.co.nz>
Subject: [Openroad-users] OpenROAD runtime error handling
Date: Tue, 19 Jun 2007 10:06:48 +1200
Size: 4673
Url: http://www.peerlessit.com/pipermail/openroad-users/attachments/20070618/08c14945/attachment.mht
More information about the Openroad-users
mailing list