com.ibm.rational.common.test.editor.framework

Class LoadTestDetailsSection

    • Constructor Detail

      • LoadTestDetailsSection

        public LoadTestDetailsSection(com.ibm.rational.common.test.editor.framework.TestEditorForm editorForm,
                              Composite parent)
        Parameters:
        editorForm -
    • Method Detail

      • setDescription

        public void setDescription(String description)
        Overrides:
        setDescription in class com.ibm.rational.common.test.editor.framework.kernel.DetailsEditorSection
      • getFormWidgetFactory

        protected com.ibm.rational.common.test.editor.framework.kernel.util.LoadTestWidgetFactory getFormWidgetFactory()
      • refreshClientFor

        protected Composite refreshClientFor(Composite details)
        Deprecated. 6.1.2
        Parameters:
        details -
      • createClientFor

        protected Composite createClientFor(Composite details)
        Deprecated. 
        Unlike CommonDataSection class's implementation, this is quite different and complex. It uses Extensions and LayoutProviders to handle the details of displaying information on screen.
        See Also:
        com.ibm.rational.common.editor.framework.internal.editor.DetailsEditorSection#createClientFor(org.eclipse.swt.widgets.Composite)
      • getControlGridData

        public Object getControlGridData()
      • createClient

        public Composite createClient(Composite parent)
        The default behavior of the DetailsEditorSection is to provide switchable behavior. It means that it supports different layouts of controls for different types of objects and is capable of managing a list of Composites each of which is hoostinf different things.

        When an element is selected elsewhere, this method is eventually called to display that element's data. By this time, the element itself is stored in m_selection. If this is the first time the element of such type needs t be displayed, the createCleintFor method is called. Otherwise, the Composite with existing controls is looked up and refreshClientFor is called. Any derived class is responsible to update data displayed in the controls.

        See Also:
        org.eclipse.hyades.test.ui.internal.editor.form.base.FormSection#createClient(org.eclipse.swt.widgets.Composite, org.eclipse.hyades.test.ui.internal.editor.form.base.FormWidgetFactory)
      • isPageNew

        protected boolean isPageNew(Composite thePage)
      • getActiveLayoutProvider

        public com.ibm.rational.common.test.editor.framework.kernel.InteractiveLayoutProvider getActiveLayoutProvider()
      • reflow

        public void reflow(boolean flush_cache)
        when required to update scrollbar you should call this
IBM Rational Performance Tester SDK

© Copyright IBM Corp. 2013. All rights reserved.