@corruptedsyntax I can't quite grasp your explanation but maybe something like this:

import QtQuick 2.6 import QtQuick.Layouts 1.3 import QtQuick.Controls 2.1 ApplicationWindow { id: window width: 360 height: 520 visible: true Item { function onButtonClicked(num_button){ console.log(num_button) } ColumnLayout { Button { text: "1" onClicked: parent.parent.onButtonClicked(text) } Button { text: "2" onClicked: parent.parent.onButtonClicked(text) } } } }

where the Button is promoted to your custom component. 'parent' inside a component file should be automatically resolved during runtime. Or you can add the listening object as a property to your component.

@SGaist ,

Yes, I have now also confirmed on the failing line:

qrc:/CResetPasswordDialog.qml:4 module "QtWebEngine" is not installed

We have:

CResetPasswordDialog.qml:

import QtQuick 2.6 import QtQuick.Layouts 1.3 import QtQuick.Controls 1.4 import QtWebEngine 1.5

(Changing import QtWebEngine 1.2 to import QtWebEngine 1.5 as specified in documentation for QtWebEngine under Qt 5.9 (https://doc.qt.io/qt-5/qtwebengine-qmlmodule.html)

We also have QT += webengine in our .pro file.

BLE on Android and iOS ? take a look at my blog
https://appbus.wordpress.com/2017/06/29/ekkes-bt-le-example-app/
and my example app https://github.com/ekke/ekkesBTLEexample

@VRonin I maneged to fix it so that qDebug << exists() now returns true. Python is still not launching though.

@VRonin Indeed something alike, any idea why this is not part of the standard itself?
anyway i ended up implementing a c++ model which is state-aware (shows only the items of the current level)
@karlheinzreichel QSortFilterProxyModel could have worked but since my model is a tree it would be a pain to iterate over it all the time
I'm trying to build something alike the settings menu on an iPhone using Qt Quick,
and its an horrible amount more complicated than I expected it to be.

Hello,
I have found the solution. Now, instead of directly deleting the widget I use deleteLater() so the widget is scheduled to be destroyed when the control returns to the event loop. The final code can be found here and it looks like:

Custom widget:

#ifndef BUTTON_H #define BUTTON_H #include <QWidget> namespace Ui { class Button; } class Button : public QWidget { Q_OBJECT public: explicit Button(int n, QWidget *parent = 0); ~Button(); private slots: void removeRequested(); signals: void remove(Button* button); private: Ui::Button *ui; }; #endif // BUTTON_H #include "button.h" #include "ui_button.h" Button::Button(int n, QWidget *parent) : QWidget(parent), ui(new Ui::Button) { ui->setupUi(this); ui->pushButton->setText("Remove button "+QString::number(n)); addAction(ui->actionRemove); connect(ui->actionRemove,SIGNAL(triggered()),this,SLOT(removeRequested())); connect(ui->pushButton,SIGNAL(clicked()),this,SLOT(removeRequested())); } Button::~Button() { delete ui; } void Button::removeRequested() { emit remove(this); }

Main gui:

#ifndef BUTTONSTACK_H #define BUTTONSTACK_H #include <QWidget> #include "button.h" namespace Ui { class ButtonStack; } class ButtonStack : public QWidget { Q_OBJECT public: explicit ButtonStack(QWidget *parent = 0); ~ButtonStack(); private slots: void on_addButton_clicked(); void remove(Button* button); private: Ui::ButtonStack *ui; int total_buttons; }; #endif // BUTTONSTACK_H #include "buttonstack.h" #include "ui_buttonstack.h" ButtonStack::ButtonStack(QWidget *parent) : QWidget(parent),total_buttons(0), ui(new Ui::ButtonStack) { ui->setupUi(this); } ButtonStack::~ButtonStack() { delete ui; } void ButtonStack::on_addButton_clicked() { Button* button(new Button(total_buttons++)); ui->qvboxlayout->insertWidget(0,button); connect(button,SIGNAL(remove(Button*)),this,SLOT(remove(Button*))); } void ButtonStack::remove(Button* button) { ui->qvboxlayout->removeWidget(button); button->deleteLater(); }

Main:

#include <QtGui/QApplication> #include "buttonstack.h" int main(int argc, char** argv) { QApplication app (argc, argv); ButtonStack bs; bs.show(); return app.exec(); }

@mrjj

Have a look at this sample
http://www.bogotobogo.com/Qt/Qt5_Downloading_Files_QNetworkAccessManager_QNetworkRequest.php
It uses a small helper class
class Downloader : public QObject
to manage the data it downloads. It responds to the finished signal.
Here it stores to file but you can as well store in ByteArray or whatever is needed.

I already have a class doing this job - as I said in the begining I can already save my reply data to file that can be read/used from anywhere in one signal slot connection, I just want to do the same thing without using a file so it can be read/used from anywhere in a single connection. If my class data object that has been assigned (or appended to) the value of reply's byte array is always empty when called, say from outside of the class (after download), meaning I have to re-download everytime I need the same data, then the reply data is not stored to my object is it?

the difference is due to a modification of the Composition Mode of the QPaineter wich was painting the objects (QPainter::QCompositionMode_Darken on the first screenshot and QPainter::QCompositionMode_SourceOver on the second one)

So not an evolution of Qt painting behavior, but a modification of the app's code.

Credo di avere risolto.
Ho portato la struct TabIndicatori al di fuori della struct HRvbl, quindi le due strutture non sono più una dentro l'altra e nella struttura HRvbl c'è solo la definizione della matrice. Così: static TabIndicatori tabindicatori [1000] [27];
Fra le inizializzazioni c'è poi l'istruzione TabIndicatori HRvbl::tabindicatori [1000] [27] = {{}};
Ora funziona.

Hi @gabor53

you cannot call the non-const function addNewImage in the const function setModelData. So you have to remove const from setModelData or add const to addNewImage.

-Michael.

This is the code for reading it:

void MainWindow::readWAV(QString wavFile, int waveNum) { QFile m_WAVFile; m_WAVFile.setFileName(wavFile); if(m_WAVFile.exists()==false) { qDebug()<<"File doesn't exist"; return; } m_WAVFile.open(QIODevice::ReadWrite); char strm[4]; char s[1]; QByteArray wav; quint32 conv; qDebug()<<"\nstart"; qDebug()<<m_WAVFile.read(4);//RIFF // m_WAVHeader.RIFF = m_WAVFile.read(4).data(); m_WAVFile.read(strm,4);//chunk size qDebug()<<qFromLittleEndian<quint32>((uchar*)strm); m_WAVFile.read(strm,4);//format qDebug()<<strm; m_WAVFile.read(strm,4);//subchunk1 id qDebug()<<strm; m_WAVFile.read(strm,4);//subchunk1 size qDebug()<<qFromLittleEndian<quint32>((uchar*)strm); m_WAVFile.read(strm,2);//audio format qDebug()<<qFromLittleEndian<quint32>((uchar*)strm); m_WAVFile.read(strm,2);//NumChannels conv = qFromLittleEndian<quint32>((uchar*)strm); qDebug()<<conv; if(conv!=1) { QMessageBox::warning(this, "Import wav file", "Wav file must be mono",QMessageBox::Ok,QMessageBox::NoButton); return; } m_WAVFile.read(strm,4);//Sample rate conv = qFromLittleEndian<quint32>((uchar*)strm); qDebug()<<conv; if(conv!=11025) { QMessageBox::warning(this, "Import wav file", "Use file with 11025Hz sample rate for native sample rate",QMessageBox::Ok,QMessageBox::NoButton); } m_WAVFile.read(strm,4);//Byte rate qDebug()<<qFromLittleEndian<quint32>((uchar*)strm); m_WAVFile.read(strm,2);//Block Allign qDebug()<<qFromLittleEndian<quint32>((uchar*)strm); m_WAVFile.read(strm,2);//BPS conv = qFromLittleEndian<quint32>((uchar*)strm); qDebug()<<conv; if(conv!=8) { QMessageBox::warning(this, "Import wav file", "Wav file must be unsigned 8 bit",QMessageBox::Ok,QMessageBox::NoButton); return; } m_WAVFile.read(strm,4);//subchunk2 id qDebug()<<strm; m_WAVFile.read(strm,4);//subchunk2 size qDebug()<<qFromLittleEndian<quint32>((uchar*)strm); outBuffLen[waveNum] = 0; while(!m_WAVFile.atEnd()) { m_WAVFile.read(s,1); wav.append(s[0]); } m_WAVFile.close(); dsBuffer[waveNum] = QAudioBuffer(wav,fmt); outBuffLen[waveNum] = dsBuffer[waveNum].sampleCount(); qDebug()<<" Processed:"; qDebug()<<outBuffLen[waveNum]; wavePath[waveNum] = wavFile; QFileInfo fileInfo(wavFile); waveName[waveNum] = fileInfo.fileName(); }

@LeLev Thanks for the link! Unfortunately I want it the other way round: I wan't the GUI thread to stay in the main thread and a 2nd qml engine (w/o visible components) in it's own thread.

@jsulm Do you know if/how I can find the cause to why it crashes. I mean does Qt creator has some kind of crash log or something?

I though so, thank you very much @raven-worx

@Marek Looks like what I meant. One clarification to my comment: the whole binding expression is evaluated when a property used in that expression is changed; in your original code it was evaluated once, in other cases it may be evaluated more often, but the function call itself (like getSomeProperty()) can't trigger a binding re-evaluation.

@shavera said in QVariant to/from QFlag:

Q_DECLARE_METATYPE

I dont see you register your own enum anywhere?
Q_DECLARE_METATYPE (Dummy::DummyOpt);

gmake executed normally. But qt 32bit header files cannot find in the disk, instead of 64bit header files have been found(for example, qconfig-32.h did not exist in the disk, instead qconfig-64.h was found in the disk. )I don't know the reason. Can anyone help me?
Thank you. The following is my installation steps:

yum install libgcc-4.8.5-11.el7.i686 yum install libstdc++-4.8.5-11.el7.i686 yum install glibc-devel.i686 yum install openssl-devel.i686 ../qt-source/configure -prefix /opt/Qt5.6.1 -platform linux-g++-32 -no-compile-examples gmake gmake install

@J.Hilk I have used "jpg" and "jpeg" and "JPG" and "JPEG" and none of them work

As you suggested, I left out the second argument completely and it still doesn't work.

I am compiling this with MinGW using Eclipse Neon

the Compile statements are :

15:15:53 **** Build of configuration Debug for project FridgeMagnets3 ****
MinGW32-make -f mf.Debug alld

1 create obj/Debug/FridgeMagnets3d.o
D:/MinGW/64/bin/g++ -c -g -std=gnu++11 -pipe -fno-keep-inline-dllexport -O0 -frtti -Wall -Wextra -fexceptions -mthreads -I'D:/Qt64/qt-install/include' -I'D:/Qt64/qt-install/include/QtWidgets' -I'D:/Qt64/qt-install/include/QtGui' -I'D:/Qt64/qt-install/include/QtCore' -I'D:/Qt64/qt-install/qtbase/include/QtWidgets' -I'D:/Qt64/qt-install/qtbase/include/QtGui' -I'D:/Qt64/qt-install/qtbase/include/QtCore' -I'D:/Projects/FridgeMagnets3/obj/Debug' -I'D:/Projects/FridgeMagnets3/src' -I'D:/Projects/FridgeMagnets3' -o obj/Debug/FridgeMagnets3d.o src/FridgeMagnets3.cpp

2a create obj/Debug/MyLabeld.o
D:/MinGW/64/bin/g++ -c -g -std=gnu++11 -pipe -fno-keep-inline-dllexport -O0 -frtti -Wall -Wextra -fexceptions -mthreads -I'D:/Qt64/qt-install/include' -I'D:/Qt64/qt-install/include/QtWidgets' -I'D:/Qt64/qt-install/include/QtGui' -I'D:/Qt64/qt-install/include/QtCore' -I'D:/Qt64/qt-install/qtbase/include/QtWidgets' -I'D:/Qt64/qt-install/qtbase/include/QtGui' -I'D:/Qt64/qt-install/qtbase/include/QtCore' -I'D:/Projects/FridgeMagnets3/obj/Debug' -I'D:/Projects/FridgeMagnets3/src' -I'D:/Projects/FridgeMagnets3' -o obj/Debug/MyLabeld.o src/MyLabel.cpp

2b create src/moc_MyLabeld.cpp
D:/Qt64/qt-install/bin/moc.exe -DUNICODE -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DQT_NEEDS_QMAIN -D__GNUC__ -DWIN32 -I'D:/Qt64/qt-install/include' -I'D:/Qt64/qt-install/include/QtWidgets' -I'D:/Qt64/qt-install/include/QtGui' -I'D:/Qt64/qt-install/include/QtCore' -I'D:/Qt64/qt-install/qtbase/include/QtWidgets' -I'D:/Qt64/qt-install/qtbase/include/QtGui' -I'D:/Qt64/qt-install/qtbase/include/QtCore' -I'D:/Projects/FridgeMagnets3/obj/Debug' -I'D:/Projects/FridgeMagnets3/src' -I'D:/Projects/FridgeMagnets3' src/MyLabel.h -o src/moc_MyLabeld.cpp
2c create obj/Debug/moc_MyLabeld.o

D:/MinGW/64/bin/g++ -c -g -std=gnu++11 -pipe -fno-keep-inline-dllexport -O0 -frtti -Wall -Wextra -fexceptions -mthreads -DUNICODE -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DQT_NEEDS_QMAIN -I'D:/Qt64/qt-install/include' -I'D:/Qt64/qt-install/include/QtWidgets' -I'D:/Qt64/qt-install/include/QtGui' -I'D:/Qt64/qt-install/include/QtCore' -I'D:/Qt64/qt-install/qtbase/include/QtWidgets' -I'D:/Qt64/qt-install/qtbase/include/QtGui' -I'D:/Qt64/qt-install/qtbase/include/QtCore' -I'D:/Projects/FridgeMagnets3/obj/Debug' -I'D:/Projects/FridgeMagnets3/src' -I'D:/Projects/FridgeMagnets3' -o obj/Debug/moc_MyLabeld.o src/moc_MyLabeld.cpp
3a create obj/Debug/DragWidgetd.o

D:/MinGW/64/bin/g++ -c -g -std=gnu++11 -pipe -fno-keep-inline-dllexport -O0 -frtti -Wall -Wextra -fexceptions -mthreads -I'D:/Qt64/qt-install/include' -I'D:/Qt64/qt-install/include/QtWidgets' -I'D:/Qt64/qt-install/include/QtGui' -I'D:/Qt64/qt-install/include/QtCore' -I'D:/Qt64/qt-install/qtbase/include/QtWidgets' -I'D:/Qt64/qt-install/qtbase/include/QtGui' -I'D:/Qt64/qt-install/qtbase/include/QtCore' -I'D:/Projects/FridgeMagnets3/obj/Debug' -I'D:/Projects/FridgeMagnets3/src' -I'D:/Projects/FridgeMagnets3' -o obj/Debug/DragWidgetd.o src/DragWidget.cpp
^
3c create obj/Debug/moc_MyLabeld.o
D:/MinGW/64/bin/g++ -c -g -std=gnu++11 -pipe -fno-keep-inline-dllexport -O0 -frtti -Wall -Wextra -fexceptions -mthreads -DUNICODE -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -DQT_NEEDS_QMAIN -I'D:/Qt64/qt-install/include' -I'D:/Qt64/qt-install/include/QtWidgets' -I'D:/Qt64/qt-install/include/QtGui' -I'D:/Qt64/qt-install/include/QtCore' -I'D:/Qt64/qt-install/qtbase/include/QtWidgets' -I'D:/Qt64/qt-install/qtbase/include/QtGui' -I'D:/Qt64/qt-install/qtbase/include/QtCore' -I'D:/Projects/FridgeMagnets3/obj/Debug' -I'D:/Projects/FridgeMagnets3/src' -I'D:/Projects/FridgeMagnets3' -o obj/Debug/moc_DragWidgetd.o src/moc_DragWidgetd.cpp

Link objects obj/Debug/FridgeMagnets3d.o obj/Debug/MyLabeld.o obj/Debug/moc_MyLabeld.o obj/Debug/DragWidgetd.o obj/Debug/moc_DragWidgetd.o
D:/MinGW/64/bin/g++ -Wl,-subsystem,windows -mthreads -o D:/Projects/FridgeMagnets3/bin/Debug/FridgeMagnets32d.exe obj/Debug/FridgeMagnets3d.o obj/Debug/MyLabeld.o obj/Debug/moc_MyLabeld.o obj/Debug/DragWidgetd.o obj/Debug/moc_DragWidgetd.o -LD:/Qt64/qt-install/lib -lglu32 -lopengl32 -lgdi32 -luser32 -lmingw32 -lqtmain -lQt5Widgets -lQt5Core -lQt5Gui

any libraries missing?

@jsulm

Hey sorry about the misconception of the topic and my post.

i should have rephrased saying definition variables can be across all the classes.
and not as mentioned in the topic as declared and defined.

Thanks,

@SGaist YES. but after some time thinking, i think i find the answer. The work will be done sequentially because they are in the event queue, so they will be handled one by one? is this correct?

@Pradeep-Kumar said in How to fetch the current file name and line number to be written into a file for logging purpose:

u can use the below mentioned way for all the debug, based on critical , fatal also.

Hi @Pradeep-Kumar ,

I am using :

class FileIO : public QObject
{
Q_OBJECT
public slots:
bool write(const QString& source, const QString& data)
{
if (source.isEmpty())
return false;

QFile file(source); if (!file.open(QFile::Append | QFile::Truncate)) return false; QTextStream out(&file); out << data; file.close(); return true; }

for write function.
And in qml:
fileio.write("/tmp/test.log", Qt.formatDateTime(new Date(), "MMM dd hh:mm:ss.zzzzzz") + "|" + "|" + "|" + "Back button clicked" + "|" + "fileName:Menu.qml" + "|" + "lineNumber:30" + "\n");
So is there some property like QT.formatDateTime property, which I can use directly to get the line number and filename?

@sierdzio That shouldn't be a problem, I've certainly not used QtWebEngine before. 4 hours on a RPi3 is pretty good; I've only got a RPi2 at the moment, so hopefully I can leave it to compile overnight.

@Mechan
on windows 8 doesn't work
for comipling replace:
#include <wbemidl.h>

to

Wbemcli.h

CLSID_WbemAdministrativeLocator to CLSID_WbemLocator
if (pLoc->ConnectServer(L"root\cimv2", NULL, NULL, NULL, 0, NULL, NULL, &pSvc) != S_OK)

to

if (pLoc->ConnectServer(BSTR (L"root\cimv2"), NULL, NULL, NULL, 0, NULL, NULL, &pSvc) != S_OK)

HRESULT hr = pSvc->ExecQuery(L"WQL", L"SELECT * FROM Win32_NetworkAdapterConfiguration WHERE IPEnabled = 'TRUE'", WBEM_FLAG_FORWARD_ONLY | WBEM_FLAG_RETURN_IMMEDIATELY, NULL, &pEnumerator);

to

HRESULT hr = pSvc->ExecQuery(BSTR (L"WQL"),BSTR ( L"SELECT * FROM Win32_NetworkAdapterConfiguration WHERE IPEnabled = 'TRUE'"), WBEM_FLAG_FORWARD_ONLY | WBEM_FLAG_RETURN_IMMEDIATELY, NULL, &pEnumerator);

after launching:
CoInitializeSecurity(NULL, -1, NULL, NULL, RPC_C_AUTHN_LEVEL_PKT, RPC_C_IMP_LEVEL_IMPERSONATE, NULL, EOAC_NONE, 0) never OK

if delete this check then uReturn is bad

Yes it requires root on Android (look here) probably it's the same problem, and yes you don't have to be root on Linux, if you have access rights to serial device as normal user.

@Sinbad Please report it anyway. being a regression it will probably be treated with high importance and fixed.

@LeLev That's a good answer, but I thought that AbstractButton and those inheriting it already have exclusivity implemented. The looks is fully customizable, so why not use that and avoid duplicating existing functionality, avoid bugs, being able to focus on what you actually need? This is not criticism, just a question to make clear if the original poster is aware of the easier possibilities and capabilities of the Quick Controls. After all, my code implements a whole skeleton application in the amount of code which EatonCode uses to implement changing the exclusive state of the buttons...

BTW, I had an error in the previous post, it was LeLev's code, not EatonCode's which I was referring to as "EatonCode's example". LeLev's code is OK if EatonCode wants to implement buttons with states.

@SGaist
Thank you very much.
I have seen the page before, but I don't know what it describe.
Finally I use the following setting to specify the device input.
QT_QPA_GENERIC_PLUGINS=evdevtouch:/dev/input/eventX
QT_QPA_EVDEV_TOUCHSCREEN_PARAMETERS=/dev/input/eventX:rotate=0
Now, the ts_uinput work normally in my system.

@Sunfluxgames said in QT load .dll but not calling resolve returns false:

So getting the lib or header for that is out of the question. I did hack a lib/header together with those functions and faked the .dll call and put the main .dll inside that folder and it seem to work but this was based off a C++ console project not a QT project.

Qt is C++ library, as @jsulm said, so there's nothing different to do.

why (crypto->*SetKey) around this? * is a call pointer to method?

Yes, ->* is pointer-to-member call. Because the you get a method address (as it's a __thiscall) and you need to bind an object to actually call the function.

CCrypto * crypto; //< From wherever that object comes // mine comes from Qobject wouldnt you need to create a new on heap

Heap or stack doesn't matter here. The thing is you need to have an initialized object from the type Crypto, which from your description I don't see how you will obtain. The problem is you need to know how big the object is, so to allocate enough memory, then manually call the constructor (resolved as in the above example) and finally call the destructor (again manually) and free your memory whenever you've finished with the object. It's a tad more complicated than calling a simple C-style function and without a header you have to do a some digging through the library's assembly to determine how large is each class's instance so to know what to put in the fake-header.