#pyqt | Logs for 2018-11-04
Back
[01:28:36] -!- kdas_ has quit [Write error: Connection reset by peer]
[01:28:54] -!- kushal has joined #pyqt
[03:52:59] -!- tijensse has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
[03:53:00] -!- crmaurei has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
[04:35:59] -!- Lauxley has joined #pyqt
[05:15:43] -!- anqxyr has joined #pyqt
[05:19:45] -!- JT-Shop has quit [Read error: Connection reset by peer]
[05:43:52] -!- heliomaster has joined #pyqt
[05:49:32] -!- heliomaster has quit [Quit: Mutter: www.mutterirc.com]
[06:22:59] <Mrokii> In a function that is called by a connected signal, is there a way to stop an event from propagating any further?
[07:11:00] -!- kallesbar has joined #pyqt
[07:44:38] -!- mintograde has joined #pyqt
[08:30:04] -!- inf has parted #pyqt
[09:14:31] -!- Lauxley has quit [Ping timeout: 268 seconds]
[09:33:39] -!- Lauxley has joined #pyqt
[09:41:10] <altendky> Mrokii: do you mean not call other slots connected to the signal? Or do you really mean an event? (Events are separate)
[10:57:42] -!- Belxjander has quit [Quit: AmigaOSv4.1.6+//PowerPC native]
[10:58:20] -!- Belxjander has joined #pyqt
[11:29:46] <Mrokii> altendky: I guess I mean the actual event. But I think I got that sorted out (reworked the functions).
[11:30:01] <Mrokii> Although I already have a new problem...
[11:31:11] <altendky> Mrokii: in the event handler you were emitting a signal?
[11:32:11] <altendky> And you wanted to pick your handler result based on things the shots connected to the signal did? Possible but not generally the intended use of signals and slots (they aren't mostly designed for getting results back)
[11:33:03] <Mrokii> altendky: As I said, I sorted that out, as I thought that manipulating the event-flow is kind of a weird thing to do.
[11:33:15] <Mrokii> In other words: I want to stay from doing that. :)
[11:37:10] <altendky> Deciding if an event propagates or not isn't weird, that's part of having an event. As in a QEvent in an event handler. But collecting results from emitting a signal isn't the most common thing
[11:38:25] <Mrokii> altendky: Anyhow, I just thought it added another complexity I didn't need at the moment.
[11:41:08] <altendky> Mrokii: I'm not sure which part you are referring to. One is complex, the other is a part of handing an event that you have no choice about, you must decide to propagate or not. You are talking about QEvents, yes?
[11:46:12] <Mrokii> altendky: Yes, I do. But as I said, I don't need that anymore.
[12:51:37] -!- Belxjander has quit [Quit: AmigaOSv4.1.6+//PowerPC native]
[12:52:01] -!- Belxjander has joined #pyqt
[14:23:30] -!- golang_dankek has joined #pyqt
[14:23:37] <golang_dankek> Hi?
[14:40:28] -!- Lauxley has quit [Remote host closed the connection]
[14:48:10] <Avaris> golang_dankek: hi
[15:02:56] -!- golang_dankek has quit [Ping timeout: 268 seconds]
[16:02:09] -!- Afrix has joined #pyqt
[16:43:21] -!- anqxyr has quit [Read error: Connection reset by peer]
[16:49:46] -!- beeman has quit []
[16:58:17] -!- beeman has joined #pyqt
[18:54:52] -!- Afrix has quit [Quit: Leaving]
[18:54:57] -!- Mrokii has quit [Quit: WeeChat 2.2]
[19:18:35] -!- Mrokii has joined #pyqt
[19:40:06] -!- Bjander has joined #pyqt
[19:41:43] -!- Belxjander has quit [Ping timeout: 245 seconds]
[19:41:44] Bjander is now known as Belxjander
[22:09:16] -!- Mrokii has quit [Ping timeout: 244 seconds]
[22:19:15] -!- Belxjander has quit [Quit: AmigaOSv4.1.6+//PowerPC native]
[22:20:20] -!- Belxjander has joined #pyqt
[22:23:39] -!- Mrokii has joined #pyqt
[23:52:18] -!- mintograde has quit [Ping timeout: 252 seconds]