Hi,

You can put your QStackedLayout and buttons in a QVBoxLayout so you can re-use the buttons. Put that layout in a QWidget and set that widget as the central widget of your QMainWindow.

@raven-worx you sir saved my life! I cant believe i was stuck at this for 2 days, when it was simply just about using the right object in qml. thanks!

Hi there.

I think you can use TableViewColumn element to create a new column inside a TableView component.
If necessary, you can define your own delegate to set how the data is showed to user.

Read more:
http://doc.qt.io/qt-5/qml-qtquick-controls-tableview.html#details <- TableView Documentation
http://doc.qt.io/qt-5/qtquickcontrols-tableview-main-qml.html <- TableView Example

[This post cross-posed to https://forum.qt.io/topic/85493/unicodedecodeerror-with-output-from-windows-os-command/18 ]

For the record, I have done exhaustive investigation, and there is only one solution which "correctly" displays the £ character under Windows. I am exhausted so will keep this brief:

To create a file name with a £ in it: Go into, say, Notepad and use its Save to name a file like abc£.txt. This is in the UK, using a UK keyboard and a standard UK-configured Windows.

Note that at this point if you view the filename in either Explorer or, say, via dir you do see a £, not some other character. That's what my user will want to see in the output of the command he will run.

Run an OS command like robocopy or even dir, which will include the filename in its output.

Read the output with QProcess.readAllStandardOutput(). I'm saying the £ character will arrive as a single byte of value 0x9c.

For the required Python/PyQt decoding bytes->str (QByteArray->QString) line, the only thing which works (does not raise an exception) AND represents the character as a £ is: ba.bytes().decode("cp850").

That is the "Code Page 850", used in UK/Western Europe (so I'm told). It is the result output of you open a Command Prompt and execute just chcp.

Any other decoding either raises UnicodeDecodeError (e.g. if utf-8) or decodes but represents it with another character (e.g. if windows_1252 or cp1252).

I still haven't found a way of getting that cp850 encoding name programatically from anywhere --- if you ask Python for, say, the "system encoding" or "user's preferred encoding" you get the cp1252 --- so I've had to hard-code it. [EDIT: If you want it, it's ctypes.cdll.kernel32.GetConsoleOutputCP().]

So there you are. I don't have C++ as opposed to Python for Qt, but I have a suspicion that if anyone tries it using the straight C++ Qt way of text = QString(process.readAllStandardOutput()) they'll find they do not actually get to see the £ symbol....

@Fuel the exemples in pyqt-master do it automatically but i don't understsnd what event or property they use

I have found a solution that kind of does the job, although takes three times as much memory.
Every update I calculate the difference between the new and the old saturation matrix, this eliminates 60% of the nonzero values, which means it gets drawn that much faster.

As a second layer of optimization I call repaint with a rectangle describing the most important zone, and call update every 60ms.

@Pierone Can you put you code in GitHub instead of a rar file? Its pretty awkward to unpack your code.

@Pataruutu

Hi the video you link is QML :)
So its its the reason it looks differently.

The one you call ugly is QWidgets and it uses the default look of the platform.

It seems you can use QML with pyt
http://pyqt.sourceforge.net/Docs/PyQt5/qml.html

Thanks @jsulm!! That sorted it!

@alekssandrap
Hello,

I found your topic because I am looking for a virtual keyboard for my PUQT5 application.
So, I found the problem of your error and this is my solution to solve it (maybe that can help some other people) :

In your pyqtSignal you have to pass an object :
sigKeyButtonClicked = pyqtSignal(object) #line 9

sigInputString = pyqtSignal(object) #line 32
sigKeyButtonClicked = pyqtSignal(object) #line 33

Then you have just to pass your key and your inputString in the signal emit :
self.sigKeyButtonClicked.emit(self._key) #line 20

self.sigInputString.emit("") #line111 in function Cancel in order to avoid an other error

Don't modify line 71 with lambda as @AlfredoC suggest because you won't be able to get the key pressed.

That's all :)

Hope that can help someone else.

Have a great day

Thank you! I didnt noticed that. I did correct this mistakes, but still getting the same error:( and empty window :/

I did the test and appearantly it's the painting which is very expensive... with no slot connected, the program takes 1,5 seconds to complete the task. There is a very similar issue reported at https://bugreports.qt.io/browse/QTBUG-49655.

But generally ProgressBars are consuming especially when we update it that often (>365000 times) while there is no significant change at each iteration. So I simply update the QProgressBar less often and the results are good (~1s) and the progression still smooth. PSB :

class ParseFileAsync(QtCore.QThread): match = QtCore.pyqtSignal(str) PBupdate = QtCore.pyqtSignal(int) PBMax = QtCore.pyqtSignal(int) def run(self): with open("test_long.log", "r") as fichier: fileLines = fichier.readlines() self.lineNumber = len(fileLines) self.PBMax.emit(self.lineNumber) if (self.lineNumber < 30): self.parseFile(fileLines, False) else: self.parseFile(fileLines, True) def parseFile(self, fileLines, isBig): cpt = 0 if(isBig): for line in fileLines: cpt+=1 if(cpt % (int(self.lineNumber/30)) == 0): self.PBupdate.emit(cpt) for element in liste: if element in line: self.match.emit(line) self.PBupdate.emit(self.lineNumber) #To avoid QProgressBar stopping at 99% else: for line in fileLines: cpt+=1 self.PBupdate.emit(cpt) for element in liste: if element in line: self.match.emit(line)

super :)
also using "#MainWindow" makes sure it dont apply to childs as stylesheets does.

@Kourpetis
Hi, it sounds like your code is getting stuck in your while loop. I believe your code needs threading.

How can i create my signal for text edit with python3 ?
With as many ways i tried, but I did not succeed .. :(