Please translate this to English...
-
Here is my SLOT (?) function. It gets execcted when I click "close" icon on title bar window.
void SettingsDialog::closeEvent( QCloseEvent* event ) { #ifdef RETILE .... #endif event->accept(); }Here is the part in question:
void QEvent::accept()
Sets the accept flag of the event object, the equivalent of calling setAccepted(true).
Setting the accept parameter indicates that the event receiver wants the event. Unwanted events might be propagated to the parent widget.
See also ignore().Setting the accept parameter indicates that the event receiver wants the event.
Doess that implies I have to code the receiver ?
or is the closeEvent( QCloseEvent* event ) receiver ?Unwanted events might be propagated to the parent widget.
It is my understending thet "might" is synonymous to "maybe" .
Is that for real?
If so - how / where is the parent instruction / function etc? -
Here is my SLOT (?) function. It gets execcted when I click "close" icon on title bar window.
void SettingsDialog::closeEvent( QCloseEvent* event ) { #ifdef RETILE .... #endif event->accept(); }Here is the part in question:
void QEvent::accept()
Sets the accept flag of the event object, the equivalent of calling setAccepted(true).
Setting the accept parameter indicates that the event receiver wants the event. Unwanted events might be propagated to the parent widget.
See also ignore().Setting the accept parameter indicates that the event receiver wants the event.
Doess that implies I have to code the receiver ?
or is the closeEvent( QCloseEvent* event ) receiver ?Unwanted events might be propagated to the parent widget.
It is my understending thet "might" is synonymous to "maybe" .
Is that for real?
If so - how / where is the parent instruction / function etc?@AnneRanch
What languague do you think it is?
Here is my SLOT (?) function
Not every function is a Qt-slot.
void QEvent::accept()
Sets the accept flag of the event object, the equivalent of calling setAccepted(true).
Setting the accept parameter indicates that the event receiver wants the event. Unwanted events might be propagated to the parent widget.
See also ignore().
Setting the accept parameter indicates that the event receiver wants the event.Since you started reading the documentation, you should read about
QEvents- https://doc.qt.io/qt-6/eventsandfilters.html
- esp. this part here
Unwanted events might be propagated to the parent widget.
It is my understending thet "might" is synonymous to "maybe" .
This is not random.
It's a general documentation, so in some cases and for someQEvents(depending on the class, widget or even your implementation/subsclass) it might be true and for others it's not. - https://doc.qt.io/qt-6/eventsandfilters.html
-
@AnneRanch
What languague do you think it is?
Here is my SLOT (?) function
Not every function is a Qt-slot.
void QEvent::accept()
Sets the accept flag of the event object, the equivalent of calling setAccepted(true).
Setting the accept parameter indicates that the event receiver wants the event. Unwanted events might be propagated to the parent widget.
See also ignore().
Setting the accept parameter indicates that the event receiver wants the event.Since you started reading the documentation, you should read about
QEvents- https://doc.qt.io/qt-6/eventsandfilters.html
- esp. this part here
Unwanted events might be propagated to the parent widget.
It is my understending thet "might" is synonymous to "maybe" .
This is not random.
It's a general documentation, so in some cases and for someQEvents(depending on the class, widget or even your implementation/subsclass) it might be true and for others it's not.@Pl45m4 Since you cannot post without some kind of put down remark - ...since you starting to read documentation... IS a put down and no business of yours if I read documentation it or not.
I AM ASKing you TO please QUIT responding TO MY POSTS.
This kind of put-downs attitude is not welcomed .Addendum
It looks as declaring what resembles plain C function
void closeEvent( QCloseEvent* event );
in public slot
may be a source of my issues implementing simple standard window "close" act.
simply put
is it a slot or "event hander" or event receiver?
This sentence is mixing it all together.
The event handler QWidget::closeEvent() receives close events.
The default implementation of this event handler accepts the close event.
If default implementation means, to me just that - so where is it and if it is default why do I have to have
void closeEvent( QCloseEvent* event );
declared as as public slot function to close window ?
- https://doc.qt.io/qt-6/eventsandfilters.html
-
@Pl45m4 Since you cannot post without some kind of put down remark - ...since you starting to read documentation... IS a put down and no business of yours if I read documentation it or not.
I AM ASKing you TO please QUIT responding TO MY POSTS.
This kind of put-downs attitude is not welcomed .Addendum
It looks as declaring what resembles plain C function
void closeEvent( QCloseEvent* event );
in public slot
may be a source of my issues implementing simple standard window "close" act.
simply put
is it a slot or "event hander" or event receiver?
This sentence is mixing it all together.
The event handler QWidget::closeEvent() receives close events.
The default implementation of this event handler accepts the close event.
If default implementation means, to me just that - so where is it and if it is default why do I have to have
void closeEvent( QCloseEvent* event );
declared as as public slot function to close window ?
@AnneRanch said in Please translate this to English...:
since you starting to read documentation... IS a put down and no business of yours if I read documentation it or not.
But that's what the documentation is made for... To read the documentation...
just saying...
Btw: nobody is getting payed here or anything. You know that.This kind of put-downs attitude is not welcomed .
What would you reply to a topic named "Please translate this to English", when it is English and understandable for most people using the Qt Framework?
When you write a proper post using adequate, technical language and used the search function, plus at least scimmed the doc pages, then you would get replies which suit your issue best.
Most of the time one has to figure out what you are asking for.
The forum here is not a notebook, where you write down your unsorted thoughts.
You demand high-quality answers, with detailed explanations in easy and understandable (not technical) language, but your topics are quite often a mess.There is nothing to “put you down”...
just think about it....
and maybe improve your posts and your attitude towards those who are voluntarily trying to help here.You obviously have problems making things in your code work (no big deal), but then you are blaming people like how they dare to reference the documentation pages, which you refused to read for some time, while the solution to your current issue (and probably also for future ones) is litteraly written there?!
In my opinion there is nothing wrong with my reply, it answered your question.
And I provided links where to read for further info... shame on me.
Take it or leave it.If one day you no longer receive any answers at all to your questions, I won't be surprised.
(last one for me)
Good luck.
If debugging is the process of removing software bugs, then programming must be the process of putting them in.
~E. W. Dijkstra
-
@AnneRanch said in Please translate this to English...:
since you starting to read documentation... IS a put down and no business of yours if I read documentation it or not.
But that's what the documentation is made for... To read the documentation...
just saying...
Btw: nobody is getting payed here or anything. You know that.This kind of put-downs attitude is not welcomed .
What would you reply to a topic named "Please translate this to English", when it is English and understandable for most people using the Qt Framework?
When you write a proper post using adequate, technical language and used the search function, plus at least scimmed the doc pages, then you would get replies which suit your issue best.
Most of the time one has to figure out what you are asking for.
The forum here is not a notebook, where you write down your unsorted thoughts.
You demand high-quality answers, with detailed explanations in easy and understandable (not technical) language, but your topics are quite often a mess.There is nothing to “put you down”...
just think about it....
and maybe improve your posts and your attitude towards those who are voluntarily trying to help here.You obviously have problems making things in your code work (no big deal), but then you are blaming people like how they dare to reference the documentation pages, which you refused to read for some time, while the solution to your current issue (and probably also for future ones) is litteraly written there?!
In my opinion there is nothing wrong with my reply, it answered your question.
And I provided links where to read for further info... shame on me.
Take it or leave it.If one day you no longer receive any answers at all to your questions, I won't be surprised.
(last one for me)
Good luck.
@AnneRanch
Another one bites the dust.
When you point one finger at what you find a put-down attitude, three fingers are pointing back at you. “Please translate this to English” is how you started this post with a put down, insinuating that our documentation isn’t written in proper English. At the same time you mix up slots with events. It’s ok, not to understand everything. But it’s hypocrite to blame others for things you allow yourself. Don’t do that, it’s not welcome. I will follow that up internally.
