Hi Alv, I'm a bit suprised by what you described but I understand your point: it is due to the fact that the SetxxxOff methods are based on the SetxxxOn methods. So I can see 2 ways to remedy to that: 1- one way is to decouple these methods and have the set of SetxxxOff completly independant from the SetxxxOn 2- the second is to keep fAllOn, fFSOn or fMRSOn kTRUE (instead of the passed value) when you set off a particular detector, that's to say: for instance MTP1: void SetMTP1On(const Bool_t val = kTRUE) { fMTP1On = val; fMRSOn = kTRUE; fAllOn = kTRUE;} instead of val all the time. Does it sound reasonable? Djamel :o) ****************************************************** )o: |ME : Djamel Ouerdane EMAIL : ouerdane@nbi.dk | |OFFICE : Tb1 @ NBI PHONE : +45 353 252 69 (office) | |INST : Niels Bohr Institute, | | Blegdamsvej 17, 2100 København Ø, Danmark | |HOME : c/o Peter Christiansen | | Sdr. Fasanvej 14, ST, 2000 Frederiksberg, DK | :oD ****************************************************** \o:
This archive was generated by hypermail 2b29 : Tue Jul 25 2000 - 13:02:26 EDT