![]() |
Telelogic DOORS (steve huntington) | ![]() |
new topic :
profile :
search :
help :
dashboard :
calendar :
home
|
||
Latest News:
|
|
Topic Title: Error Reporting Topic Summary: Created On: 25-Aug-2004 09:18 Status: Post and Reply |
Linear : Threading : Single : Branch |
![]() |
![]()
|
![]() |
|
Hi,
I'm trying to re-direct errors from the edit DXL window to a window on my main GUI. I know you can use the noErrors() function to suppress error reporting in the DXL window, but this then involves using the lastError() function to check the last error recieved against a previous error to decide whether or not to display it. So i have some questions as follows:-
Cheers Hugh ------------------------- Hugh Johnson Westland Helicopters Ltd. myurl |
|
![]() |
|
![]() |
|
The dxl manual (V7.0SP1 page 606) says this of noErrors:
<< Switches off DXL run-time errors until lastError is called. Any function that can produce a run-time error is affected. Instead of failing and halting when they discover an error condition, they set an error message, which can be checked by the lastError function. Calling this function resets the error message to null, so you must store any potential error messages for reuse. >> ... which nearly answers your first question. But it's not too clear on how many errors it's 'active' for. I'd guess at all of them, but you'll only see the most recent one when you call lastError. So the answer to your question is (I think) that noErrors suppresses all errors, but you only get to see the last one that occurred before you call lastError. What happens about the effects of the errors in the meantime is anyone's guess... Not sure (even less sure!) about the second question. Paul. ------------------------- Paul dot Tiplady at TRW dot com TRW Automotive |
|
![]() |
Telelogic DOORS
» DXL Exchange
»
Error Reporting
|
![]() |
FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.