Files
RedBear-OS/local/recipes/qt/qtdeclarative/source/src/quicktemplates/qquickbutton.cpp
T
vasilito f31522130f fix: comprehensive boot warnings and exceptions — fixable silenced, unfixable diagnosed
Build system (5 gaps hardened):
- COOKBOOK_OFFLINE defaults to true (fork-mode)
- normalize_patch handles diff -ruN format
- New 'repo validate-patches' command (25/25 relibc patches)
- 14 patched Qt/Wayland/display recipes added to protected list
- relibc archive regenerated with current patch chain

Boot fixes (fixable):
- Full ISO EFI partition: 16 MiB → 1 MiB (matches mini, BIOS hardcoded 2 MiB offset)
- D-Bus system bus: absolute /usr/bin/dbus-daemon path (was skipped)
- redbear-sessiond: absolute /usr/bin/redbear-sessiond path (was skipped)
- daemon framework: silenced spurious INIT_NOTIFY warnings for oneshot_async services (P0-daemon-silence-init-notify.patch)
- udev-shim: demoted INIT_NOTIFY warning to INFO (expected for oneshot_async)
- relibc: comprehensive named semaphores (sem_open/close/unlink) replacing upstream todo!() stubs
- greeterd: Wayland socket timeout 15s → 30s (compositor DRM wait)
- greeter-ui: built and linked (header guard unification, sem_compat stubs removed)
- mc: un-ignored in both configs, fixed glib/libiconv/pcre2 transitive deps
- greeter config: removed stale keymapd dependency from display/greeter services
- prefix toolchain: relibc headers synced, _RELIBC_STDLIB_H guard unified

Unfixable (diagnosed, upstream):
- i2c-hidd: abort on no-I2C-hardware (QEMU) — process::exit → relibc abort
- kded6/greeter-ui: page fault 0x8 — Qt library null deref
- Thread panics fd != -1 — Rust std library on Redox
- DHCP timeout / eth0 MAC — QEMU user-mode networking
- hwrngd/thermald — no hardware RNG/thermal in VM
- live preload allocation — BIOS memory fragmentation, continues on demand
2026-05-05 20:20:37 +01:00

136 lines
3.6 KiB
C++

// Copyright (C) 2017 The Qt Company Ltd.
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR LGPL-3.0-only OR GPL-2.0-only OR GPL-3.0-only
// Qt-Security score:significant reason:default
#include "qquickbutton_p.h"
#include "qquickbutton_p_p.h"
#include <QtGui/qpa/qplatformtheme.h>
QT_BEGIN_NAMESPACE
/*!
\qmltype Button
\inherits AbstractButton
//! \nativetype QQuickButton
\inqmlmodule QtQuick.Controls
\since 5.7
\ingroup qtquickcontrols-buttons
\brief Push-button that can be clicked to perform a command or answer a question.
\image qtquickcontrols-button.gif
{Button control in various interaction states}
Button presents a push-button control that can be pushed or clicked by
the user. Buttons are normally used to perform an action, or to answer
a question. Typical buttons are \e OK, \e Apply, \e Cancel, \e Close,
\e Yes, \e No, and \e Help.
Button inherits its API from AbstractButton. For instance, you can set
\l {AbstractButton::text}{text}, display an \l {Icons in Qt Quick Controls}{icon},
and react to \l {AbstractButton::clicked}{clicks} using the AbstractButton API.
A button emits the signal \l {AbstractButton::}{clicked()} when it is activated by the user.
Connect to this signal to perform the button's action. Buttons also
provide the signals \l {AbstractButton::}{canceled()}, \l {AbstractButton::}{doubleClicked()}, \l {AbstractButton::}{pressed()},
\l {AbstractButton::}{released()} and \l {AbstractButton::}{pressAndHold()} for long presses.
See the snippet below on how to connect to the button's signals.
\code
RowLayout {
Button {
text: "Ok"
onClicked: model.submit()
}
Button {
text: "Cancel"
onClicked: model.revert()
}
}
\endcode
\sa {Customizing Button}, {Button Controls}
*/
QQuickButton::QQuickButton(QQuickItem *parent)
: QQuickAbstractButton(*(new QQuickButtonPrivate), parent)
{
}
QQuickButton::QQuickButton(QQuickButtonPrivate &dd, QQuickItem *parent)
: QQuickAbstractButton(dd, parent)
{
}
QFont QQuickButton::defaultFont() const
{
return QQuickTheme::font(QQuickTheme::Button);
}
/*!
\qmlproperty bool QtQuick.Controls::Button::highlighted
This property holds whether the button is highlighted.
\image qtquickcontrols-button-highlighted.gif
{Highlighted button showing visual emphasis}
A button can be highlighted in order to draw the user's attention towards
it. It has no effect on keyboard interaction.
The default value is \c false.
*/
bool QQuickButton::isHighlighted() const
{
Q_D(const QQuickButton);
return d->highlighted;
}
void QQuickButton::setHighlighted(bool highlighted)
{
Q_D(QQuickButton);
if (highlighted == d->highlighted)
return;
d->highlighted = highlighted;
emit highlightedChanged();
}
/*!
\qmlproperty bool QtQuick.Controls::Button::flat
This property holds whether the button is flat.
\image qtquickcontrols-button-flat.gif
{Button labeled "Button" in flat style with no background}
A flat button typically does not draw a background unless it is pressed or checked.
The default value is \c false.
*/
bool QQuickButton::isFlat() const
{
Q_D(const QQuickButton);
return d->flat;
}
void QQuickButton::setFlat(bool flat)
{
Q_D(QQuickButton);
if (flat == d->flat)
return;
d->flat = flat;
emit flatChanged();
}
QPalette QQuickButtonPrivate::defaultPalette() const
{
return QQuickTheme::palette(QQuickTheme::Button);
}
QT_END_NAMESPACE
#include "moc_qquickbutton_p.cpp"