Ticket #156 (closed enhancement: fixed)

Opened 12 years ago

Last modified 11 years ago

Worflow of new Controller version

Reported by: michelpons Owned by: Michael Halloran
Priority: minor Milestone: 2.2
Component: COLoggingController Version: Development
Keywords: Reference counting errors Cc: michaelhalloran

Description

Build 263 is used: when opening up Controller and selecting a given component, the \"Enable Logging\" box is appearing as non-ticked. The \"Call CAPE-OPEN error interfaces if errors are raised\" box and \"Log Reference counts\" box are ticked and greyed out. Then I tick the \"Enable Logging\" box. The \"Call CAPE-OPEN error interfaces if errors are raised\" box and \"Log Reference counts\" box remain ticked and are now ungreyed. Next I untick the \"Enable Logging\" box. The \"Call CAPE-OPEN error interfaces if errors are raised\" box and \"Log Reference counts\" box have then greyed out and unticked. I close the COLTT controller and then enters it again. When going to the same component as before, the \"Enable Logging\" box is unticked while The \"Call CAPE-OPEN error interfaces if errors are raised\" box and \"Log Reference counts\" box are ticked and greyed out.

I would think that ticking or unticking the \"Enable Logging\" box should not alter the two other boxes. Since by default these two boxes are ticked but greyed out, it means that they are partially independent from the \"Enable Logging\" box. Anyway they will be \"active\" only when a component is logged. Now I wonder if really the selection for these boxes is per component or rather is it for the entire set of components to be logged. I don't exactly how the implementation is done. If reference counting and error interface calls are not component dependent, the corresponding boxes should appear elsewhere than within a component detail.

Change History

comment:1 Changed 11 years ago by michaelhalloran

  • Status changed from new to closed
  • Resolution set to fixed

Fixed by fix to #158, Error and Reference logging options are now initialised correctly.

Note: See TracTickets for help on using tickets.