@lolcocks Thank you! I also just found out about that, in the bug report @Pablo-J-Rogina posted, somebody mentioned it. I do have a couple of little problems like setting the Background of QSpinBoxes via stylesheet doesn't work anymore using a file dialog fo an open file name sometimes has issues etc. but overall it actually works way too good, I wasn't expecting that! Now I am happy. Very happy. For now this is solved I guess. If I run into huge problems, I will probably update here.

Hi and welcome to devnet, Rather than just posting code, you should also explain exactly what you want to achieve.

Awesome, thanks. I'll keep that in mind and put in some checks just to make sure.

Okay then divide and conquer this. Create your GUI initially giving it a Dictionary of hard-coded data that represents the data coming from the database get your Gui to work with that data in the manner you are wanting. I do something similar with my project as I deal with a QTreeView (the QTreeWidget was not necessary) and QStandardItemModel supplying it a Dictionary of rows and it works like a charm Basically step back and simplify your approach making it overly complicated/complex just makes it harder to work with. I have a database class template that I shared with several folks already as well as the students in my free python-qt classroom on Discord but I think I also have an example program of rendering the QTreeView as well then all you would need to do is implement that add and substract aspects which are also fairly easily done if you work with your data behind the scenes and then just repopulate the view after that data has been adjusted

Well without seeing the code you use to create the object you are passing in -- it is hard to see what you might or might not be doing wrong -- better yet supply an MRE (Minimal Reproducible Example) that shows this functioning and produces the same error you are getting when it is run --- then we can help you troubleshoot your bug so much more effectively and quicker to boot

@RemcoMusic I know this is not PySide2 but PyQt5 is really really close and here is discussion on getting QtCharts to work perhaps something they tried/did might help you as well https://github.com/ghostop14/sparrow-wifi/issues/1

This work project responde to many problems How to integrate matplotlib in Pyqt5 include : Open file to read and write (read data , save data to .txt file) by pyqt5 how to use QlistWidget how to use figureCanva to Both plot 2D ,3D

@younglegend Yes I am too confused -- what is it that you still need help with here -- please be specific in what was not covered?

Depending on what your image is, you can create a custom QAbstractSlider that will draw the image and then the cursor on top of it.

@behruz-montazeri if you want to learn how to do MVC within python-pyqt shoot me a message on Discord at DenniO#8137 and I will dive into that with you as well as share some example code as that can be a rather extensive discourse.

That depends on what you are actually trying to put into the ListView -- your List of Dictionaries is a bunch of Dictionary Objects or just the names of those Dictionary Objects?

@a_person Find out what it is about your environment that does make it find PyQt5 when from the terminal or wherever (e.g. maybe you have a virtual environment, I don't know), and then compare that environment to the one being used inside Qt Creator at run time which does not locate it?

@ruchitinfushion okay hopefully all you have to do is replace the reference to PyQt5 with PySide2 but not sure on that one. Regardless if you cannot get this to work straight out of the gate then at least it should point you in the right direction of how to implement what you are trying to implement -- it also gets rid of the unnecessary Designer junk that was there and extends the classification appropriately. Lastly I do not have your images so I simply commented that part out and used straight Text. So hopefully all you will have to do is implement those lines if I read the documentation correctly -- so just comment out the pure Text lines in favor of the Icon/Pixmap related stuff from sys import exit as sysExit from PyQt5.QtCore import Qt, QSize, pyqtSlot from PyQt5.QtGui import QFont, QIcon from PyQt5.QtWidgets import QApplication, QMainWindow, QWidget, QComboBox, QVBoxLayout, QLabel class CentralPanel(QWidget): def __init__(self, parent): QWidget.__init__(self) self.MyParent = parent # Best just to load these once at start self.pmHigh = QPixmap('E:/code/highStats.png') self.pmMedm = QPixmap('E:/code/mediumStats.png') self.pmLows = QPixmap('E:/code/lowStats.png') self.pmNorm = QPixmap('E:/code/normalStats.png') qgFont = QFont() qgFont.setFamily("SF Pro Display") qgFont.setPointSize(16) qgFont.setWeight(75) qgFont.setBold(True) self.lblIconHldr = QLabel('Hidden Label') self.lblIconHldr.setFont(qgFont) self.lblIconHldr.setAlignment(Qt.AlignHCenter) self.lblIconHldr.hide() self.cbxStats = QComboBox() self.cbxStats.setFont(qgFont) # self.cbxStats.setIconSize(QSize(70, 20)) self.cbxStats.addItem('High') self.cbxStats.addItem('Medium') self.cbxStats.addItem('Low') self.cbxStats.addItem('Normal') # self.cbxStats.addItem(QIcon('E:/code/highStats.png'),'High') # self.cbxStats.addItem(QIcon('E:/code/mediumStats.png'), 'Medium') # self.cbxStats.addItem(QIcon('E:/code/lowStats.png'), 'Low') # self.cbxStats.addItem(QIcon(E:/code/normalStats.png'), 'Normal') self.cbxStats.currentIndexChanged.connect(self.SetIcon) vbxLayout = QVBoxLayout() vbxLayout.addWidget(self.lblIconHldr) vbxLayout.addStretch(1) # The position of this affects how things are rendered vbxLayout.addWidget(self.cbxStats) self.setLayout(vbxLayout) @pyqtSlot(int) def SetIcon(self, Indx): if Indx == 0: self.lblIconHldr.setText('High') # pmImage = self.pmHigh elif Indx == 1: self.lblIconHldr.setText('Medium') # pmImage = self.pmMedm elif Indx == 2: self.lblIconHldr.setText('Low') # pmImage = self.pmLows else: self.lblIconHldr.setText('Normal') # pmImage = self.pmNorm # pmImage.scaled(70, 20, Qt.KeepAspectRatio) # self.lblIconHldr.setPixmap(pmImage) self.cbxStats.hide() self.lblIconHldr.show() class statsMainWindow(QMainWindow): def __init__(self): QMainWindow.__init__(self) self.setWindowTitle('Main Window') self.resize(300, 275) self.CenterPane = CentralPanel(self) self.setCentralWidget(self.CenterPane) if __name__ == '__main__': MainThred = QApplication([]) MainGUI = statsMainWindow() MainGUI.show() sysExit(MainThred.exec_())

@daljit97 that is awesome -- but to reiterate for future questions you might have - including an MRE (Minimal Reproducible Example) which means one can simply copy/paste the MRE and run it to get the same results greatly speeds up getting an answer. If you include an MRE that will not run because it has elements removed that are still referenced that is not technically an MRE because it does not reproduce what you are experiencing.

Well without seeing a minimal fully functioning example of your code it is kind of hard to guess what you might be doing wrong. However as a general answer I (unless the combo box has a large amount of data in it) just store this data in dictionary and/or list and then add to the dictionary/list -- purge the combo box -- and add the data pre-sorted back into the combo box

This is my experience with "Ravi, Robbie" and whoever is running things at goslicd. I interviewed over a skype call and in my oppinion it went very smoothly and it was a good interview. He knows I'm at least qualified if not over qualified for this job. He said over skype that he would send me the coder agreement that I could read over and then get back to him on it. He never sent the agreement. It's been 2-3 days. It was supposed to be sent right after the skype call. No email from him. I sent an email asking about it. No response was returned. I said I was open about how much I would get paid per milestone. That would be an employer's wet dream, right? There is no hourly wage, it's jut pay-by-milestone + equity (so they say). Another horror story from the dishonest, fake, unfair job market. This post has no business in the Qt forums, with such disrespect shown from the hiring party. Well, they do have about a 20% chance of success as 80% of startups fail. Good luck to them! I could have finished all of the project milestones in less than half the timeline stated. Their loss. Thinking of applying? Don't waste your time.

@nekitamtip what I would do is not rely on the call stack as @Kent-Dorfman points out its unreliable at best and not available due to threading issues (now that does not mean it cannot be just means it would take a lot of work and time to figure it out if it is even possible). So with that said and a much easier methodology for handling this in code regardless of the coding language you use here is what I do. Any place you plan to "raise" an error or handle an exception include enough information so that you can easily determine where that error occurred along with what that error was. In your example I would change the raise to read: raise Exception('MyTreadWorker.job_with_exception_raised :' + error_message) This basically (at a glance) tells you where the error occurred in detail and if the error was dynamic what that error was -- note if the error is static then simply replace [ ' + error_message ] with [ Description of Error ' ] again do this any place you raise an error and/or use a try except -- further I would actually call an error_handler routine in case I want to switch from live debugging to production debugging and want those errors posted to an error-log of some sort. Basically it is considered quality programming that when you raise an error or handle an exception that you report enough information back so that with that error message you (1) Know exactly where the error occurred (2) Know exactly what the error was (3) and include any extra information that might be available that would make fixing that error much easier If you do this as a standard within all your code you will soon find out that tracking done bugs becomes a trivial task.

First off regardless of the coding language you should follow the MVC (Model-View-Controller) methodology of coding which basically divorces the front-end (View) from the back-end (Model) by putting in a middle interpreter layer (Controller). Why do this well first it has the benefit of separating functionality and focusing each element on what it does best. The GUI (View) is best for handling the user interface and not very good with dealing with the data, while the Database (Model) is best for handling the data and is not very good with handling the user interface. The Controller is just the method for moving the data from the View to Model. This also has a secondary benefit if you ever change the back-end with a different database engine the only thing that is effected is the Model and maybe a bit of the Controller the GUI is essentially untouched and vice-versa if you wish to change the front-end the only thing that really changes is the front-end since all the API calls to the middle-tier would essentially remain the same. Further should the business logic affecting the data occur that is generally dealt with within the Controller or the Database depending on the implementation of the business logic. For instance data validation and manipulation generally takes place within the Controller layer making sure that no bad-data gets into the database which is always a nightmare and something that happens often if you directly tie the front-end into the back-end. So in short use pyqt5 to handle your front-end GUI and use python to handle your interface to your database (validating and moving the data to the database) and let the database do what its best at doing - handling the data with storage and stored-procedures, triggers, etc... I hope that helps

@badr You have one table widget (or similar, actually presumably QTableView rather than QTableWidget since you have your own model) holding rows & columns from a SQL query. You say you want another table widget to show a column "computed" (at client side) from columns in the first one. So why not create a second model whose data() method is overridden to perform the necessary computation and return the desired final string for Qt::DisplayRole using the index.row/column() (not just the index) as indexers into the SQL model's rows/columns? Or, if you want to stick with your current usage of QTableWidget (not ideal that you use Python SQL calls and copy result set into that, but up to you), you could make your second one a QTableWidget too and use setData() to populate its rows/columns with the actual corresponding strings whenever the first one changes (more work depending on how often your data changes, but in your case it might only be during loaddata() when you populate if it does not change thereafter).

@Hodenbrecher one of the quirks of c++ QQuickItem is a forward-declared class https://en.cppreference.com/w/cpp/language/class#Forward_declaration

Just an update. It looks like the QtCreatorDeployment.txt file is only taken into account by CMake Project or Generic Project. So I created a Generic Project, add the Python file(s) to the .files file, removed all the steps from the Build Settings tab, and configured the Run Settings with a Custom Executable where I set python as the remote executable, and main.py as the command line arguments while enabling Forward to local display. And it worked :-)

@BobbyG Below is the sample code which can be used to update the Chart from C++ void PlotData::updateData(QAbstractSeries *p_series) { QVector<QPointF> pointList; pointList.reserve(numPts); for(int count = 0; count < plot_data_vector.size(); ++count) { pointList.append(x_data, y_data); // fill your plot data here } if(p_series) { QXYSeries *xySeries = static_cast<QXYSeries *>(p_series); xySeries->replace(pointList); } } void PlotData::clearSeries(QAbstractSeries *p_series) { if(p_series) { QXYSeries *xySeries = static_cast<QXYSeries *>(p_series); xySeries->clear(); } } And from the QML you need to call this function by passing the chart view series. PlotData.updateData(chartView.series(1)) Hope this helps...

@blossomsg Hi That is fine, please marked as solved then :)

May I suggest to change for Python 3 ? Python 2.7 will reached end of life next year so it's not a good idea to start a new project with it.

By writing a small demo to complete my post, I found the issue. As it might be helpful to somebody else, here it is: demo.scxml: <?xml version="1.0" encoding="UTF-8"?> <scxml xmlns="http://www.w3.org/2005/07/scxml" version="1.0" binding="early" xmlns:qt="http://www.qt.io/2015/02/scxml-ext" name="plop.scxml" qt:editorversion="4.7.1"> <state id="State_1"> <qt:editorinfo scenegeometry="144.50;162.05;84.50;112.05;120;100" geometry="144.50;162.05;-60;-50;120;100"/> </state> </scxml> demo.py: #!/usr/bin/env python import sys from PySide2.QtCore import QObject, QCoreApplication, SLOT, Slot from PySide2.QtScxml import QScxmlStateMachine class Backend_1(QObject): def __init__(self, machine): super(Backend_1, self).__init__() self.machine = machine self.machine.connectToState("State_1", self, SLOT("s1_active(bool)")) @Slot(bool) def s1_active(self, active): if active: print('Backend_1::State_1: enter') self.submachine = QScxmlStateMachine.fromFile('demo.scxml') b = Backend_2(self.submachine) self.submachine.start() else: print('Backend_1::State_1: exit') class Backend_2(QObject): def __init__(self, machine): super(Backend_2, self).__init__() self.machine = machine self.machine.connectToState("State_1", self, SLOT("s1_active(bool)")) @Slot(bool) def s1_active(self, active): if active: print('Backend_2::State_1: enter') else: print('Backend_2::State_1: exit') if __name__ == '__main__': app = QCoreApplication(sys.argv) machine = QScxmlStateMachine.fromFile('demo.scxml') b = Backend_1(machine) machine.start() sys.exit(app.exec_()) If you run this, you expect to see: Backend_1::State_1: enter Backend_2::State_1: enter But, the second statemachine does not seem to start. To fix it, you need to store the instance of Backend_2 (eg: self.b = Backend_2(self.submachine)). I guess it was garbage collected, so all the states/events connections were broken. Meanwhile, if you think my design patter is bad, I'm willing to learn :)

Hi, You are replacing the central widget in OpenVTK. You should rather add your widget to the current central widget's layout.

A quick google search with PyQt5 layout gives that nice article.

@jazzycamel said in Picamera significant delay and low FPS, but low CPU and memory usage: Thanks this worked i also changed the camera parameters so it runs even faster. self._camera=PiCamera(sensor_mode=4,resolution='640x480',framerate=40). Now the only problem is when i try to capture using the worker thread is not responding to the signal ,this is also happening with the stop function its not responding to a button click or custom emit signal to stop the camera it just keeps running @pyqtSlot() def snapshot(self): self._looping=False self._camera.capture('image.jpg') self._looping=True stopcamera = pyqtSignal() self._thread = QThread() self.stopcamera.connect(self._camera.stop) self._thread.start() self.CameraSnap.clicked.connect(self._camera.snapshot) self.CameraBack.clicked.connect(self.functionstopcamera) def functionstopcamera(self): self.stopcamera.emit()