MonitorModel QML Type

A model that can fetch data from various sources and keep a history of their values. More...

• List of all members, including inherited members

Properties

• count : int
• dataSources : list<object>
• interval : int
• maximumCount : int
• running : bool

Methods

• clear()
• object get(int index)

Detailed Description

MonitorModel can fetch data from various sources at regular intervals and keep a history of their values. Its main use is having it as a model to plot historical data in a graph for monitoring purposes, such as a CPU usage graph.

The snippet below shows how to use it for plotting a system's CPU load in a simple bar graph:

import QtQuick
import QtApplicationManager

ListView {
    id: listView
    width: 400
    height: 100
    orientation: ListView.Horizontal
    spacing: (width / model.count) * 0.2
    clip: true
    interactive: false

    model: MonitorModel {
        id: monitorModel
        running: listView.visible
        CpuStatus {}
    }

    delegate: Rectangle {
        width: (listView.width / monitorModel.count) * 0.8
        height: model.cpuLoad * listView.height
        y: listView.height - height
        color: "blue"
    }
}

To add a data source to MonitorModel just declare it inside the model, as done in the example above with the CpuStatus component. Alternatively (such as from imperative javscript code) you can add data sources by assigning them to MonitorModel's dataSources property.

A data source can be any QtObject with the following characteristics:

• A roleNames property: it's a list of strings naming the roles that this data source provides. Those role names will be available on each row created by MonitorModel.
• Properties matching the names provided in the roleNames property: MonitorModel will query their values when building each new model row.
• An update() function: MonitorModel will call it before creating each new model row, so that the data source can update the values of its properties.

The following snippet shows MonitorModel using a custom data source written in QML:

MonitorModel {
    running: true
    QtObject {
        property var roleNames: ["foo", "bar"]

        function update() {
            // foo will have ever increasing values
            foo += 1;

            // bar will keep oscillating between 0 and 10
            if (up) {
                bar += 1;
                if (bar == 10)
                    up = false;
            } else {
                bar -= 1;
                if (bar == 0)
                    up = true;
            }
        }

        property int foo: 0
        property int bar: 10
        property bool up: false
    }
}

Thus, in the MonitorModel above, every row will have two roles: foo and bar. If plotted, you would see an ever incresing foo and an oscillating bar.

QtApplicationManager comes with a number of components that are readily usable as data sources, namely:

• CpuStatus
• FrameTimer
• GpuStatus
• IoStatus
• MemoryStatus
• ProcessStatus

While running is true, MonitorModel will probe its data sources every interval milliseconds, creating a new row every time up to maximumCount. Once that value is reached the oldest row (the first one) is discarded whenever a new row comes in, so that count doesn't exceed maximumCount. New rows are always appended to the model, so rows are ordered chronologically from oldest (index 0) to newest (index count-1).

Property Documentation

Method Documentation