Hey there,

I've been looking at the maintainability of other people's code when they've written stuff that uses signals and slots, and have been starting to get the feeling that it's just hard to read - when the signal arrives, the code jumps to the slot function, which seems very much like a GOTO statement, and it can be tiring to find out which signal called the slot, and where the code goes to next after the slot function has completed. I'm wondering what sorts of "best practices" people use to make signal/slots code more readable and easier to follow.