#pyqt | Logs for 2018-10-25

Back
[00:41:14] -!- mandeep has joined #pyqt
[01:03:01] -!- mandeep has quit [Quit: Leaving]
[01:14:17] -!- mandeep has joined #pyqt
[02:53:18] -!- Mrokii has quit [Ping timeout: 252 seconds]
[03:07:09] -!- kallesbar has joined #pyqt
[03:34:47] -!- anqxyr has joined #pyqt
[06:35:18] -!- mintograde has joined #pyqt
[07:16:53] -!- mintograde has quit [Ping timeout: 276 seconds]
[08:53:48] -!- Siecje has joined #pyqt
[09:18:45] -!- GrandPa-G has joined #pyqt
[09:22:30] <GrandPa-G> For a program I was given to update, they use QtCore.QMetaObject.connectSlotsByName(MainWindow). They name each widget, like saleBtn. I understand the concept of how a signal is generated. I see there a def for on_saleBtn_released. Does this the connectbyname maps all possible events for the widget?
[09:32:21] -!- mandeep has quit [Quit: Leaving]
[09:34:00] <altendky> GrandPa-G: did they specify the slots in designer?
[09:34:27] <altendky> GrandPa-G: I've never really done that myself.
[09:34:56] <GrandPa-G> From what I have been given, it looks no designer was ever used. All the widgets are hard coded
[09:36:45] <altendky> GrandPa-G: http://doc.qt.io
[09:38:46] <GrandPa-G> yes i have looked at that. it gives example of clicked event. does the "matching signals" mean any of the other possible signals for the widget, thus released is connected?
[09:39:40] <altendky> GrandPa-G: if you have a slot following the form it seems
[10:47:12] -!- GrandPa-G has quit [Ping timeout: 252 seconds]
[11:33:17] -!- kdas_ has joined #pyqt
[11:34:09] -!- kushal has quit [Ping timeout: 256 seconds]
[12:12:05] kdas_ is now known as kushal
[12:58:48] -!- kallesbar has quit [Quit: Konversation terminated!]
[16:42:53] -!- Siecje has quit [Quit: Leaving.]
[17:04:40] -!- mintograde has joined #pyqt
[17:45:02] -!- BPL has joined #pyqt
[18:21:38] -!- anqxyr has quit [Read error: Connection reset by peer]
[18:35:12] -!- BPL has quit [Quit: Leaving]
[22:36:47] -!- mintograde has quit [Ping timeout: 240 seconds]