Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Post History
Today I saw the following question on Software Dev (this is the beginning): (rest of post...) The title, "connect with SLOT/SIGNAL:QPushButton clicked signal not received by main window" sounds li...
#2: Post edited
- Today I saw the following question on Software Dev (this is the beginning):
- 
- The title, "connect with SLOT/SIGNAL:QPushButton clicked signal not received by main window" sounds like it could be about one of several languages. From the web context I was guessing Javascript. As I read further I eventually saw `MainWindow.cpp`, which told me it's actually C++.
- Down at the bottom I saw the tags:
- 
- On the one hand, you could argue that if I don't know enough to recognize the library (and thus know its language) then I shouldn't be answering the question. And that's true! I had no intention of answering the question. I read the question and its answers to *learn something*, and wondered if I should have better context for what I would be learning.
- Would it make more sense to display the tags under the title, something like this?
- 
- Today I saw the following question on Software Dev (this is the beginning):
- 
- (rest of post...)
- The title, "connect with SLOT/SIGNAL:QPushButton clicked signal not received by main window" sounds like it could be about one of several languages. From the web context I was guessing Javascript. As I read further I eventually saw `MainWindow.cpp`, which told me it's actually C++.
- Down at the bottom I saw the tags:
- 
- On the one hand, you could argue that if I don't know enough to recognize the library (and thus know its language) then I shouldn't be answering the question. And that's true! I had no intention of answering the question. I read the question and its answers to *learn something*, and wondered if I should have better context for what I would be learning.
- Would it make more sense to display the tags under the title, something like this?
- 
#1: Initial revision
Should we show tags before the body, to provide context for reading the question?
Today I saw the following question on Software Dev (this is the beginning):  The title, "connect with SLOT/SIGNAL:QPushButton clicked signal not received by main window" sounds like it could be about one of several languages. From the web context I was guessing Javascript. As I read further I eventually saw `MainWindow.cpp`, which told me it's actually C++. Down at the bottom I saw the tags:  On the one hand, you could argue that if I don't know enough to recognize the library (and thus know its language) then I shouldn't be answering the question. And that's true! I had no intention of answering the question. I read the question and its answers to *learn something*, and wondered if I should have better context for what I would be learning. Would it make more sense to display the tags under the title, something like this? 