Ticket #151 (closed: fixed)

Opened 12 years ago

Last modified 5 years ago

Capture and display log information in QTIPlot

Reported by: Nick Draper Owned by: Roman Tolchenov
Priority: major Milestone: Iteration 9
Component: Keywords:
Cc: Blocked By:
Blocking: Tester:

Description

This may require the writing of a new log Channel, but this can be done easily see FilterChannel in MantidKernel for Reference.

Unless you have a better suggestion I suggest we pass the messages up through publishing them as a BOOST Signal.

This can be subscribed to a QT slot within QTIPlot. The slot code should then handle displaying the message. I suggest a scolling textbox similar to the display you get when performing a curve fit in QTIPlot.

Change History

comment:1 Changed 12 years ago by Nick Draper

  • Owner set to Roman Tolchenov

comment:2 Changed 12 years ago by Roman Tolchenov

(In [1085]) re #151 New classes added: SignalChannel to Mantid and MantidLog to QtiPlot.

FrameworkManager's initialization is moved to the constructor.

comment:3 Changed 12 years ago by Roman Tolchenov

(In [1086]) re #151

comment:4 Changed 12 years ago by Nick Draper

(In [1087]) re #151 Added the missing boost dls into third party andcorrected broken tests and main

comment:5 Changed 12 years ago by Matt Clarke

(In [1090]) Refs #151. Adjusted sconstruct to link against boost signals library.

comment:6 Changed 12 years ago by Russell Taylor

(In [1096]) Downgrade a log statement from DetectorGroup that was excessive and slowed down ConvertUnits a lot. Allow the setting of L1 from the properties file (when LoadInstrumentFromRaw is used). Re #151.

comment:7 Changed 12 years ago by Nick Draper

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

comment:8 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​999

Note: See TracTickets for help on using tickets.