[Nsclspectcl-cvscommits] SpecTcl/SpecTcl EventProcessor.h,4.2,4.3 EventProcessor.cpp,4.2,4.3

[<ro...@us...>]

Update of /cvsroot/nsclspectcl/SpecTcl/SpecTcl
In directory sc8-pr-cvs1:/tmp/cvs-serv25328

Modified Files:
	EventProcessor.h EventProcessor.cpp 
Log Message:
Add interface and default implementation
to catch unrecognized buffer
types.

Index: EventProcessor.h
===================================================================
RCS file: /cvsroot/nsclspectcl/SpecTcl/SpecTcl/EventProcessor.h,v
retrieving revision 4.2
retrieving revision 4.3
diff -C2 -d -r4.2 -r4.3
*** EventProcessor.h	3 Jul 2003 21:24:05 -0000	4.2
--- EventProcessor.h	24 Oct 2003 14:47:03 -0000	4.3
***************
*** 341,344 ****
--- 341,347 ----
    virtual Bool_t OnResume(CAnalyzer& rAnalyzer,
  			  CBufferDecoder& rDecoder); // Resume Run.
+   virtual Bool_t OnOther(UInt_t nType,
+ 			 CAnalyzer& rAnalyzer,
+ 			 CBufferDecoder& rDecoder); // Unrecognized buftype.
  };
  

Index: EventProcessor.cpp
===================================================================
RCS file: /cvsroot/nsclspectcl/SpecTcl/SpecTcl/EventProcessor.cpp,v
retrieving revision 4.2
retrieving revision 4.3
diff -C2 -d -r4.2 -r4.3
*** EventProcessor.cpp	3 Jul 2003 21:24:05 -0000	4.2
--- EventProcessor.cpp	24 Oct 2003 14:47:03 -0000	4.3
***************
*** 414,415 ****
--- 414,444 ----
    return kfTRUE;
  }
+ /*!
+    Called whenever an unrecognized buffer type is encountered.
+    This is done to allow the user to take application specific 
+    action on these buffer types.
+    \param nType     (UInt_t [in]):
+       Type of buffer received.
+    \param rAnalyzer (CAnalyzer& [in]):
+       Reference to the analyzer that is calling us.
+    \param rDecoder (CBufferDecoder& [in]):
+       Reference to the  buffer decoder that understands the
+       overall buffer structure.
+ 
+    \return 
+    - kfTRUE -- If the buffer was successfully processed.
+    - kfFALSE - If the buffer was not successfully processed.
+               Note that if the processor does not understand the
+ 	      type of of the buffer, it should return kfTRUE
+ 	      since some other processor in the pipeline might.
+ 	      If it understands the buffer type but the format is
+ 	      weird/wrong etc.  Then it's appropriate to return
+ 	      kfFALSE.
+ */
+ Bool_t
+ CEventProcessor::OnOther(UInt_t nType,
+ 			 CAnalyzer& rAnalyzer,
+ 			 CBufferDecoder& rDecoder)
+ {
+   return kfTRUE;
+ }