You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RIght now, the three classes ObserverBase, ROL_ObserverBase, and SolutionObserverBase are unrelated. In my app, I want to write a single observer class that covers all needs, since there is a lot of overlap here. However, these classes often declare a method with the same name and similar (sometime same) signature, making it confusing and possibly bug prone.
Can we do away with some observers and have just one, or at the very least make them inherit from each other? Is there a reason why we have these 3 completely unrelated classes?
Enhancement
RIght now, the three classes
ObserverBase
,ROL_ObserverBase
, andSolutionObserverBase
are unrelated. In my app, I want to write a single observer class that covers all needs, since there is a lot of overlap here. However, these classes often declare a method with the same name and similar (sometime same) signature, making it confusing and possibly bug prone.Can we do away with some observers and have just one, or at the very least make them inherit from each other? Is there a reason why we have these 3 completely unrelated classes?
@mperego
The text was updated successfully, but these errors were encountered: