Files
qt-creator/src/plugins/qmlprofiler/qmlprofilerconfigwidget.ui
Tobias Hunger 4ef01c961e app_version.h: Make IDE name configurable
Change-Id: I993f452c8d09cf89e9a2958fc8e36b7d2c17ee6f
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
2017-09-05 10:19:48 +00:00

72 lines
2.2 KiB
XML

<?xml version="1.0" encoding="UTF-8"?>
<ui version="4.0">
<class>QmlProfiler::Internal::QmlProfilerConfigWidget</class>
<widget class="QWidget" name="QmlProfiler::Internal::QmlProfilerConfigWidget">
<property name="geometry">
<rect>
<x>0</x>
<y>0</y>
<width>320</width>
<height>100</height>
</rect>
</property>
<layout class="QFormLayout" name="formLayout">
<item row="0" column="0">
<widget class="QLabel" name="flushEnabledLabel">
<property name="text">
<string>Flush data while profiling:</string>
</property>
</widget>
</item>
<item row="0" column="1">
<widget class="QCheckBox" name="flushEnabled">
<property name="toolTip">
<string>Periodically flush pending data to the profiler. This reduces the delay when loading the
data and the memory usage in the application. It distorts the profile as the flushing
itself takes time.</string>
</property>
</widget>
</item>
<item row="1" column="0">
<widget class="QLabel" name="flushIntervalLabel">
<property name="text">
<string>Flush interval (ms):</string>
</property>
</widget>
</item>
<item row="1" column="1">
<widget class="QSpinBox" name="flushInterval">
<property name="minimum">
<number>1</number>
</property>
<property name="maximum">
<number>10000000</number>
</property>
<property name="value">
<number>1000</number>
</property>
</widget>
</item>
<item row="2" column="0">
<widget class="QLabel" name="aggregateTracesLabel">
<property name="text">
<string>Process data only when process ends:</string>
</property>
</widget>
</item>
<item row="2" column="1">
<widget class="QCheckBox" name="aggregateTraces">
<property name="toolTip">
<string>Only process data when the process being profiled ends, not when the current recording
session ends. This way multiple recording sessions can be aggregated in a single trace,
for example if multiple QML engines start and stop sequentially during a single run of
the program.</string>
</property>
</widget>
</item>
</layout>
</widget>
<resources/>
<connections/>
</ui>