Hi,
I isolated the problem into a small snippet:
https://gitlab.com/snippets/1744780
This still crashes for me.
I do get the result I’m after by only setting one resize mode, i.e.:
|header.setSectionResizeMode(5, QtWidgets.QHeaderView.Fixed) |
However, what I’m really after is the behaviour o
On Tuesday, 14 August 2018 07:43:36 PDT Christopher Probst wrote:
> Good Morning Fellow Qters,
>
> This is basic question. I have always had the reflex of not emitting
> signals that belong to a separate class, even if signals are public. I,
> however don't know why I adopted this rule of thumb. W
Typically the semantics of signals are "something changed about *this*
object". With those semantics it should generally be the object doing
the emitting.
There are of course other ways to use signals, e.g. as a makeshift
message-bus-ish system or to call a method in another slot (though
QMetaObje
Good Morning Fellow Qters,
This is basic question. I have always had the reflex of not emitting
signals that belong to a separate class, even if signals are public. I,
however don't know why I adopted this rule of thumb. Why do we very rarely
emit signals from a different QObject?
Thanks,
Christo
