Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 311935 - [LTTng] Implement some "preference menu"
Summary: [LTTng] Implement some "preference menu"
Status: CLOSED WONTFIX
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: LinuxTools (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Francois Chouinard CLA
QA Contact: Francois Chouinard CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 290046 301629 301630
  Show dependency tree
 
Reported: 2010-05-06 13:02 EDT by William Bourque CLA
Modified: 2022-01-13 14:53 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description William Bourque CLA 2010-05-06 13:02:02 EDT 
There is a lot of ajustable preferences in the view, however there is no way to ajust them right now at run time. 
There should be a view of some kind of "menu" to allow the user to change them while executing.  

Most of the pertinent values are in HistogramConstant.java (general stuff) or in the top of HistogramView.java (related to the view utilisation of the control and UI).
Comment 1 Alvaro Sanchez-Leon CLA 2010-06-09 13:32:28 EDT 
The title of this bug is updated to remove "HIstogram View" as this Bug applies to the whole Lttng.ui plug-in, where we need to specify all user configurable parameters for the application 

Example:
	- The check points interval used in the state system e.g. 15000 events (default)
	- The initial visible time range to display in the time related views (the lower it gets the faster the views will display) e.g. 1 sec (default), this value shall be common to Histogram View, Control Flow View, Resources View.
Comment 2 Patrick Tasse CLA 2013-05-22 17:23:25 EDT 
The checkpoint interval is not user-configurable but it can be specified at the trace level with setCacheSize().

The initial visible time range is not user-configurable but it can be specified at the trace level by overriding getInitialRangeOffset().