This class provides a checkbox and a label. It is a compound control containing a CEikCheckBox and a CEikLabel to display a string of text. This class is not intended for user derivation.

Base class for aligned text controls. The CEikAlignedTextControl class extends the CCoeControl class in order to support extra functionality for aligned text controls. It is only intended as a simple starting point for controls.

A control which is drawn surrounded by a rectangular border. This class is used as the basis for most Uikon controls. The screen appearance of derived classes can be changed by overriding the protected method Draw() . By default, this draws a border of the appropriate type around the control.

Deprecated class.

This class holds an array of controls wrapped with related information. This related information is an ID, whether the control is of a fixed size or is stretchable and, if a set size, the controls length.

This class holds an array of controls wrapped with related information. This related information is an ID, whether the control is of a fixed size or is stretchable and, if a set size, the controls length.

Interface for aligned text controls. The MEikAlignedTextControl interface is to be implemented by aligned text controls. This interface extends the MEikAlignedControl interface with methods to handle wrapping and number of visible lines. The CEikAlignedTextControl class provides an implementation of this interface.

This is the base class from which concrete button controls (command buttons, option buttons and checkboxes) are derived. The base class implements knowledge of the buttons logical state, and can respond to user events. It cannot, however, draw itself. Derived classes should provide an appropriate implementation of CCoeControl::Draw(). It is usual to make the on-screen appearance of the button dependent on its current state. Derived classes may also implement StateChanged() to respond appropriately to changes in the draw state.

This is a container for CCoeControl-derived controls that adds horizontal and/or vertical scrollbar(s) when needed. To use this container, simply: 1. add the controls to it 2a. add a layout manager, or 2b. position them manually relative the upper left corner of the scrolling page 2b.1 call the MinimumPageSize() method to find the size needed to hold all the controls. Use the SetPageSize() method to set the size of the scrolling page. A margin is added to the size given when a scrollbar is needed (can be changed with the SetBottomRightMargin() method).

A mixin for controls that allows other classes to add and remove controls via a generic API.

A default implementation of a MQikControlProvider

This control is used as a standin for controls that are shown in a pop-out. The standin displays a text representation of the actual control value and works like a proxy for key events.

A mixin for classes creating controls. Is mainly used by CQikControlProvider.

Transfers the state of a control (that cannot be moved from one layout to another) to the control that will be used in its place. The main reason for the is not moveable is that it would get a different ContainerWindow() in the new place.

MQikControlStreamInterface is used by controls to be able to handle cancel behaviour from e.g. the QikContainerPopout. StoreUserDataL is called e.g. by the QikContainerPopout when it is launched, this to store the current value of the control. RestoreUserDataL is called e.g. by the QikContainerPopout if the user chooses to cancel the input.

The MQikControlValueObserver interface is implemented by the QikStandInControl to be able to get callback from a control when the controls value has changed. E.g. controls that implement the MQikTextRepresentationInterface interface should call HandleControlValueChanged on the observer in their SetValue() and SetText() and such methods.

A mixin for controls that have a special behaviour when a view changes layouts.

MQikTextRepresentationInterface should be implemented by controls that are normally shown in a container pop-out e.g. QikSlider or EikEdwin. The interface is used to allow the QikControlStandIn control to ask any control for its textual representation. The QikControlStandIn also adds itself as a control value observer via the SetControlValueObserver method.

A mixin that should be implemented by all controls wanting a MQikControlProvider in their ConstructFromResourceL().

An array of TQikControlInfos. Used by CQikControlProvider to know how to construct controls in a view.

An array containing controls that are released due to a relayout. The controls are removed from the view and placed in this array while they are unreleased/reused or deleted.

A single tab. Objects of this class represent a single tab in a group of tabs - see CQikTabGroup. Each tab has text and/or a picture. These can be set from code using the members provided, or loaded using information provided in a resource file. Other than the text/picture functions and the constructors, the classes functions generally need not be called directly by the user - they are used by the control framework.

Use this class to get a tab control group with one or more tabs. If you want more support, use the CQikTabScreen.

The TabScreen lets the user of it create a multi-page screen area. The TabScreen has a TabGroup consisting of one or more Tabs , and a TabPage connected to each tab. The TabScreen takes care of switching between the TabPages , so that only the page connected to the currently selected tab is shown. User controls can be added to the general TabPage object by calling the CQikTabScreenPage::AddControlL() method. The TabScreen can optionally host a extra control to be displayed at he right of the TabScreens TabGroup . This can for example be a button-bar control. To use the TabScreen you should:

• Create it on the heap and call SetContainerWindow() and ConstructL() on it.

• Set the extent of it, using e.g. the SetExtentToAllAvailableSpaceL() method.

• Optionally modify the width of the TabGroup using the SetTabGroupWidth() method.

• Create a CQikTab object and a CQikTabScreenPage object.

• Create any number of controls to appear on the TabPage, adding them to the page using the CQikTabScreenPage::AddControlL() method.

• Add the Tab and its TabPage to the tab screen using the AddTabPageL() method.

• Repeat step 5 and 6 until all tabs are created and added.

The tab screen control (CQikTabScreen ) uses objects of this type to hold pages to be displayed when one of its tabs is selected by the user. Each page is connected to a tab, and holds the user controls to be shown when the connected tab is selected.

Interface to be implemented by view tabs. The MQikTab interface is supposed to be implemented by view tab classes. The interface mainly provides methods for setting visibillity, dimmed state, tab text, tab icon and animation states of the icon.

General content class which holds some content like an icon. CQikContent can hold content like animations, themed skins or icons, application icons or bitmaps. The content objects host must be a CCoeControl, the host is used when the content object is drawn. The host and the owner of the content can be the same object, but it must not be so. The content can be created in several different ways. One way is to instantiate a CQikContent object directly by the new operator and then call a SetContentL() method to specify the content. Another more simple way is to call one of the NewL() methods. NewL() both instantiates a new CQikContent object and sets the specific content of this object. The content can also be initiated from a specific content resource. See QIK_CONTENT or QIK_CONTENT_MBM.