@galou_breizh I think point_size is too small and the ellipse generated is "pixelated" because of that. This gives a nice circle filled with blue # -*- coding: utf-8 -*- """Show an incomprehension in setScale for QGraphicsItemGroup.""" from PySide2 import QtCore from PySide2 import QtGui from PySide2 import QtWidgets point_size = 10.0 # In real-world units. # Get entrypoint through which we control underlying Qt framework app = QtWidgets.QApplication([]) scene = QtWidgets.QGraphicsScene() group = QtWidgets.QGraphicsItemGroup() scale = 50.0 # 1 real-world units = 500 px. !! Has no apparent effect. pen = QtGui.QPen(QtCore.Qt.red) brush = QtGui.QBrush(QtCore.Qt.blue) x = 1.0 # Real-world units. y = 2.0 # Real-world units. top_left = (x - point_size / 2.0, y - point_size / 2.0) ellipse = QtWidgets.QGraphicsEllipseItem( QtCore.QRectF(*top_left, point_size, point_size)) ellipse.setPen(pen) ellipse.setBrush(brush) ellipse.setScale(scale) group.addToGroup(ellipse) # group.setScale(scale) scene.addItem(group) view = QtWidgets.QGraphicsView(scene) view.show() # Start Qt/PySide2 application. If we don't show any windows, the # app would just loop at this point without the means to exit app.exec_()

@galou_breizh I answered in the other post. But it's not a good way to duplicate post for the same issue. Please try to avoid it in the future, thanks

@SGaist said in alignment for QCheckBox in QTableWidget: Why not use the Qt.ItemIsUserCheckable flag to get the checkboxes you want rather than widgets San you are doing ? Widgets set like that will not respond to any role because they are not part of the rendering of the model. I originally went with this and had issues with how I coded it, so I went with the checkbox route. But a clear head does wonders, and I did it this way. Thank you guys.

Wait wait wait .... I am not sure how far this discussion has got but this seems woefully wrong way to do this The process flow should be --- Start Program Call Record_Audio Main Window Switch to Processing Window Call Recognizer Call SpeechConvert Call OtherProcessingFunctionsIfNeeded Switch to DisplayResults Main Window As such you never destroy the Main Event Thread as there is no need to -- you just switch between the various Windows you are using -- and if you sub-classed these various windows you can encapsulate what they do such that should you need a change to a single piece it you can easily do that without affecting any of the other pieces Create a Main Event Thread -- running a Window -- running some computational functions -- destroying the Main Event Thread and creating a new one to run another Window --- is far more complexity that is required and simply bad methodology

@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

I figured it out. It was something I definitely should have realized. Since I changed the top widget mouse press events in the init function of the ClickEdit class, it was assigning new mouse press events to the same top level widget again and again for every instance of ClickEdit in the window. I'm still ignorant of the mechanics of why it runs multiple times from being reassigned more than once, but I at least fixed the issue by creating a list called top_widgets_modified shared between all ClickEdit instances that consists of any top widgets already assigned a new mousePressEvent. If a top level widget has already been assigned a new mouse press event, it skips it in the next ClickEdit init. Alternatively, It might work to have it iterate through the top widgets once per window instead of for every ClickEdit init, though I'll have to make sure it won't miss anything by doing this. class ClickEdit(QWidget): top_widgets_modified = [] def __init__(self, type_of_edit_field, parent=None): super(ClickEdit, self).__init__(parent) self.QWidgettype = type_of_edit_field self.layout = QHBoxLayout() self.setLayout(self.layout) top_widgets = QApplication.topLevelWidgets() self.layout.addWidget(self.QWidgettype()) for tw in top_widgets: if tw in self.top_widgets_modified: continue self.top_widgets_modified.append(tw) original_MPE = tw.mousePressEvent MPE = partial(self.newMousePressEvent, tw, original_MPE) tw.mousePressEvent = MPE

oops! See: https://forum.qt.io/post/570687

Okay first I am not quite sure what was wrong with your code but I have re-implemented it using PyQt and this slight re-implementation of your code works just fine for me -- all you should have to do is change the PyQt5. reference to a PySide2. reference and it should work for you as well and if it does not then we would need a link to one of those images to help you troubleshoot what is occurring. Oh and if you have absolutely any questions about what I did and/or why please do ask. I am all about teaching folks the hows and whys of coding. from PyQt5.QtCore import Qt, pyqtSlot from PyQt5.QtGui import QPixmap from PyQt5.QtWidgets import QApplication, QMainWindow, QDockWidget from PyQt5.QtWidgets import QFileDialog, QLabel, QAction class MenuToolBar(QDockWidget): def __init__(self, parent): QDockWidget.__init__(self) self.Parent = parent self.MainMenu = self.Parent.menuBar() self.MenuActRef = {'OpenFileAct':0} # ******* Create the File Menu ******* self.FileMenu = self.MainMenu.addMenu('File') # ******* Create File Menu Items ******* # self.OpnFileAct = QAction(QIcon('Images/open.ico'), 'Open File', self) self.OpnFileAct = QAction('Open File', self) self.OpnFileAct.setShortcut('Ctrl+O') self.OpnFileAct.setStatusTip('Open File') self.OpnFileAct.triggered.connect(self.OpenFile) self.MenuActRef['OpenFileAct'] = self.OpnFileAct self.FileMenu.addAction(self.OpnFileAct) # self.InitToolBar() # In case you ever wanted to add something to a Tool Bar def InitToolBar(self): # Add Items to the Toolbar # This needs to be dynamically based on user adjustments if any self.mainToolBar = self.MainWin.addToolBar('Quick Access') # This is would be a call to a Database or Config File # ToolBarLayout = self.MainWin.GetToolBarLayout() for item in ToolBarLayout: if item == 'Spacer': self.mainToolBar.addSeparator() else: self.mainToolBar.addAction(self.MenuActRef[item]) # These are the Menu/Tool Bar Actions @pyqtSlot() def OpenFile(self): self.Parent.OpenNewFile() class CentralPanel(QLabel): def __init__(self, parent): QLabel.__init__(self) self.Parent = parent # In case you ever need to expand this functionality class MainWindow(QMainWindow): def __init__(self): QMainWindow.__init__(self) # Set QMainWindow settings self.setGeometry(100, 100, 500, 300) self.setWindowTitle("PyQT Show Image") # Setup the CentralWidget self.CntrPane = CentralPanel(self) self.setCentralWidget(self.CntrPane) # Setup the Menu and Tool Bar self.MenuToolBar = MenuToolBar(self) # Setup the Status Bar self.SetStatusBar(self) def SetStatusBar(self, parent): # Using Parent in case it ever becomes a stand-alone Class StatusMsg = '' parent.StatBar = parent.statusBar() if len(StatusMsg) < 1: StatusMsg = 'Ready' parent.StatBar.showMessage(StatusMsg) def OpenNewFile(self): name = QFileDialog.getOpenFileName(self, 'Open File') #print(name) pixmap = QPixmap(name[0]) self.CntrPane.setPixmap(pixmap.scaled(self.CntrPane.size() , Qt.KeepAspectRatio , Qt.SmoothTransformation)) if __name__ == '__main__': MainEventThread = QApplication([]) MainApp = MainWindow() MainApp.show() MainEventThread.exec()

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

@yumo said in qt.qpa.fonts: Unable to open default EUDC font: "C:\\WINDOWS\\FONTS\\EUDC.TTE": It doesn't work Well, I don't know what that exactly means and how you tried.

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.

try to add this to main.py import os os.environ["QT_IM_MODULE"] = "qtvirtualkeyboard"

I had to replace this : style = """ { background-color : rgba(64,64,64,255); }; With either: style = """ *{ background-color : rgba(64,64,64,255); }; Or style = """ QWidget { background-color : rgba(64,64,64,255); }; And then it works :- )

Okay not sure if the PySide2 Designer is as bad as the PyQt Designer but I am going to guess it is. That said creating a GUI using straight Qt is just as easy and about as quick as using a Designer but when you are done you have code you can actually work with solidly and further you have template code you can copy/paste from for later project speeding up the designs of your GUI as you progress. Note using the Designer requires more knowledge and understanding than using straight Qt because you have to learn how to effectively use the Designer or you get stuff that you cannot work with or not work with easily. So just words of warning from someone who has been helping numerous folks with the pain of using the Designer and teaching them just how much easier it is to create that GUI without using the Designer

Ah, I found the problem. I was telling beginInserRows I was going to insert at the end and then not inserting at the end. Telling it the right place solved the problem.

That kind of depends on what you mean by Fix its position ?

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?

@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.

@mrjj Thank you very much! Problem solved.

@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.

It appears they are using the following version of the overloaded QImage call QtGui.QImage(uchar *data, int width, int height, int bytesPerLine, QImage::Format format, QImageCleanupFunction cleanupFunction = nullptr, void *cleanupInfo = nullptr) Thus the h*np.nbytes[np.uint8] would be the bytesPerLine That being said here is an augmented bit of documentation (https://doc.qt.io/qt-5/qimage.html#QImage-5) covering this function that I think will answer the basic question, cannot guarantee it will not raise additional questions though This constructs an image with the given width, height and format, that uses an existing memory buffer, data. The width and height must be specified in pixels. The bytesPerLine specifies the number of bytes per line (stride). For information on Stride see: (https://medium.com/@oleg.shipitko/what-does-stride-mean-in-image-processing-bba158a72bcd) The buffer must remain valid throughout the life of the QImage and all copies that have not been modified or otherwise detached from the original buffer. The image does not delete the buffer at destruction. You can provide a function pointer cleanupFunction along with an extra pointer cleanupInfo that will be called when the last copy is destroyed. If format is an indexed color format, the image color table is initially empty and must be sufficiently expanded with setColorCount() or setColorTable() before the image is used.

So I solved my problem. It turns out QImage needs the image to be a flat numpy array. Here is how it's done: qrgb_dict = {'r': lambda x: QtGui.qRgb(x, 0, 0), 'g': lambda x: QtGui.qRgb(0, x, 0), 'b': lambda x: QtGui.qRgb(0, 0, x)} colortable = [qrgb_dict[color](i) for i in range(256)] img = QtGui.QImage(arr, w, h, w, QtGui.QImage.Format_Indexed8) img.setColorTable(colortable) Where arr is an array of shape (h,w) and with uint8 values in 0-255

I was able to solve this by switching to pycharm, for some reason spyder did not want to cooperate, kept getting DLL not found errors, "application failed could not find or load qt plugin could not be initialized", and importing QCharts would not work. everything seems to be working now thorough pycharm.

OK, so the issue turned out to be something different. We are using QtPy and it needs the environment variable QT_API set to pyside2 for our Windows setup. For some reason the environment passed to QProcess isn't inheriting that variable and it was defaulting to pyside. Setting it manually to pyside2 by calling setProcessEnvironment on our QProcess before the start call gets everything working. Not sure if this is a PySide2 bug or not. The QProcess.execute documentation says: "The environment and working directory are inherited from the calling process." but it doesn't say this explicitly for start.

@krzysieklfc said in Gamma correction for display: Shouldn't Qt somehow handle the color correction when I'm 'telling it' to view the image? no! why should it? I don't quite understand why you are dividing by 256? Also whats the returning type of GetR()/GetG()/GetB()?

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

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, Looks like there's some problem with the PySide 2 implementation. You should check the bug report system to see if it's something known. If not, please consider opening a new report providing your example and as much details as possible about your current setup.

Figured out my issue. I just needed to instantiate a QQmlDebuggingEnabler object. Calling QtQml.QQmlDebuggingEnabler() before instantiating my QApplication was enough.