There is no straightforward API for this. I see several possibilities:

custom painting in QQuickPaintedItem custom painting in QQuickItem custom painting via GL shaders custom painting in QML Canvas a set of 4 animated Rectangle components, simulating the line. An ugly solution, but probably the easiest to do

Perhaps BorderImage component can be forced to do an animation like that, but I doubt it.

@Guy-Gizmo said in QComboBox and QPushButton in a grid layout do not line up properly in macOS:

options

congratulations！

if i do this , i'll use custom stylesheet

QPushButton
{
padding: 0px;
margin:0px;
image:url(xxx);
image-position:center;
border-image: url(xxxxxx) 2 2 2 2;
}

maybe fix it.
i suggest that if you use qt, use stylesheet to redraw all the controls.
because qt draw every control itself, maybe undefined behavior happened.

but at last, congratulations for u!

Thanks, I tried the OpacityMask again as you suggested and it works now. It took me a bit to get it right, because i) I had a warning about the recursive property in ShaderEffectSource needing to be set to "true" and ii) the mask size needs to be the same as the source size for it to work properly. After a while I noticed that i) originated from some code in the contentItem of the button using the ColorOverlay (in fact it was the same problem there i.e. I tried to apply it to the parent). To fix ii) I used a transparent frame so that the code now looks something like:

background: Item{ width: control.width height: control.height Rectangle{ id: progressFrame anchors.fill: parent color: "transparent" visible: false Rectangle{ id: progressRect width: 0.7*parent.width height: parent.height anchors.verticalCenter: parent.verticalCenter anchors.left: parent.left color: "green" } } Rectangle { id: backgroundRect anchors.fill: parent radius: height / 2 color: "red" visible: true } OpacityMask{ anchors.fill: progressFrame source: progressFrame maskSource: backgroundRect } }

Resulting in:

Thanks again!

@Lasith
Oh, thats a classic :)

f3 = new QFrame();

???

How can I have a fixed size for the buttons for both the situations?

c->setSizePolicy(QSizePolicy::Fixed,QSizePolicy::Fixed);

@jsulm thanx bro :)

What was the problem ?

Hi,

More likely that not all your database data are loaded in memory. You would have to call fetchMore however beware that if you have big tables it's going to cost you more in RAM.

@VRonin I got it corrected!
searchProxy->setSourceModel(modal);
ui->tableView->setModel(searchProxy);

should be put inside the search button method!

@J.Hilk Thanx mate :) I had been too complex

just use the filePath without further modification, its already the complete path.
This code

QDir d = QFileInfo(filePath).absoluteDir(); QString absolute=d.absolutePath();

will lead you to the dir above the selected path...

Hi
Yes calling the function directly is actually a better solution in this case.
Its worth mentioning that the so called slots are 100% normal c++ member functions
and can be called without any Qt involvement/use of.

void MainWindow::on_pushButton_clicked() { int value=ui->lineEdit->text().toInt(); // get value Dialog dialog1; dialog1.sendIntData(value); dialog1.exec(); }

@Wieland thanks !!! for the answer.

@tansgumus said in Button backgound non-existent property!:

Component.onCompleted: { // WORKS! // button.background.color = "red" // WRONG background = Rectangle { color: "red" } }

Because Component.onCompleted is a javascript function and you can use only js syntax inside it. Rectangle { color: "red" } is QML specific syntax, js doesn't understand it. You can create a component dynamically (see the QML docs) by giving the component as a string to Qt.createQmlObject().

If you use button.background.color = "red" in Component.onCompleted it retains all other properties of the backround; I have found it to be a convenient way to change only one or two properties without messing others. Using other approaches, i.e. defining the whole component either dynamically or declaratively, overwrites everything which may or may not be desirable.

yeah I used the stylesheets and it solved my problem

Yep, it works.
Thanks :)

@ars1614
ok. never seen it then :)
I would not rule out you can override it closing on menu selection by subclassing
or using event filter.

you should use a Flat Button to do this

here's an example how you can do this.

import QtQuick 2.6 import QtQuick.Layouts 1.3 import QtQuick.Controls 2.0 import QtQuick.Controls.Material 2.0 // Flat Button Button { id: button property alias textColor: buttonText.color focusPolicy: Qt.NoFocus Layout.fillWidth: true Layout.preferredWidth : 1 leftPadding: 6 rightPadding: 6 contentItem: Text { id: buttonText text: button.text opacity: enabled ? 1.0 : 0.3 color: Material.primaryColor horizontalAlignment: Text.AlignHCenter verticalAlignment: Text.AlignVCenter elide: Text.ElideRight font.capitalization: Font.AllUppercase font.weight: Font.Medium } background: Rectangle { id: buttonBackground implicitHeight: 48 Layout.minimumWidth: 88 color: button.pressed ? buttonText.color : "transparent" radius: 2 opacity: button.pressed ? 0.12 : 1.0 } // background } // button

feel free to modify the Button to fit into your UI
in my blog series about Qt 5.7 QtQuickControls2 you'll find more infos: http://j.mp/qt-x

Both ApplicationWindow and Page provide header and footer properties that are convenient for placing anything at the top or bottom of the window or a page.

I think i got it... sometimes you don't see the tree in the wood...

Is just change inside the Grid....

ButtonMenu { width: columnbutton.w; height: columnbutton.h; operation: buttonUserTEXTA; onClicked: {menuuser.state = "STATE A" } }

so easy, and I can remove the if-else stuff inside the ButtonMenu.qml...

I think its SOLVED!!

@mrjj
Thanks so Much Bro :)

https://bugreports.qt.io/browse/QTCREATORBUG-16172

I was thinking about reimplementing nextId so that when you click on the "Back" button you reroute to the page you want then call next()

@mandruk1331

Hi,

yourButton->setStyleSheet("QPushButton:pressed { background-color: red }");

@aney
Yeah when meta compiler doesn't run, it all get a bit strange. :)

In first post , under it. to the right. is Topic Tools button. It can mark as solved.

@errolflynn You should write self.button1.clicked.connect(ft_handler) - this will register the function ft_handler as a slot for the clicked signal. On http://doc.qt.io/qt-5/qabstractbutton.html you see that the signature of that signal is void clicked(bool checked). In other words, when the signal is activated, your handler is called as ft_handler(checked) where checked is either True or False. Per the signature of the clicked signal, this is the only information you will get out of the signal.

If you want to pass additional parameters, you indeed will need to create a separate function that encodes those extra parameters and passes them to the handler. In Python it makes a lot of sense to use a lambda for it, for instance:
self.button1.clicked.connect(lambda checked: fct_handler(par1, par2, par3, checked))

Hope this helps

@p3c0 Thank you! Works fine.

i think the only things you need to do is open or shutdown bluetooth, find bluetooth devices and connect if needed. all the other things must have been done by the hardware vendor

Hi and welcome to devnet,

To add to @mrjj What version of Qt and OS are you running ?

@marlenet15 See the docs : http://doc.qt.io/qt-5/qabstractbutton.html#iconSize-prop

I would try on this snippet , Hope it works well.

I have found a solution myself in the QT-Sourcecode of ButtonStyle.qml. I have to :

import QtQuick.Controls.Private 1.0

in myButtonStyle.qml and in the LabelSection I use The StyleHelpers.stylizeMnemonics, so my ButtonStyle.qml looks like:

import QtQuick 2.4 import QtQuick.Controls 1.3 import QtQuick.Controls.Styles 1.3 import QtQuick.Controls.Private 1.0 ButtonStyle { id: myButtonStyle background: Rectangle { implicitWidth: 100 implicitHeight: 25 border.width: control.activeFocus ? 2 : 1 border.color: "#888" radius: 4 gradient: Gradient { GradientStop { position: 0 ; color: control.pressed ? appPalette.button_clicked_gradient_start : appPalette.button_gradient_start } GradientStop { position: 1 ; color: control.pressed ? appPalette.button_clicked_gradient_stop : appPalette.button_gradient_stop } } } label: Component{ id:labelCompoent Row{ anchors.left: parent.left anchors.leftMargin: (parent.width - (text.width + image.width))/2 anchors.top: parent.top anchors.topMargin: 2 spacing: 0 Image{ id:image ;source: control.iconSource} Label{ id: text height: image.height width:100 horizontalAlignment:Text.AlignHCenter verticalAlignment: Text.AlignVCenter color: control.enabled ? appPalette.text_color : appPalette.text_color_disabled text: StyleHelpers.stylizeMnemonics(control.text) } } } }

Glad you found out and thanks for sharing the solution.

Since you have it working now, please update the thread title prepending [solved] so other forum users may know a solution has been found :)

Yes, that is the way it should work.

You can hide also anything based on QWidget Sometimes you have more than one possibility. So there is also some redundancy.

I have the same problem ...
... there is a bug-report (https://bugreports.qt.io/browse/QTIFW-711)
... but no solution.

Hi and welcome to devnet,

Add a slot in the widget containing the toolbar and connect QStackedWidget::currentChanged to it. In the slot check the index value and enable/disable the button.

Hope it helps