1

Topic: std:: exception and qt

And here what nuance in qt - why in int main (int argc, char *argv []) {QApplication app (argc, argv); window wnd;//--- wnd.show (); int ret_code = 0; try {ret_code = app.exec ();} catch (...) {//- - QMessageBox:: critical (0, "Critical", "Critical message text");//-};//--- return ret_code;} thrown inside window:: showEvent normal means with ++ the exception in cath does not get?

2

Re: std:: exception and qt

Hello, _hum _, you wrote: __> and here what nuance in qt - why in __> thrown inside window:: showEvent normal means with ++ the exception in cath does not get? show it is necessary inside try to do. Well and RTFM: Non-spontaneous show events are sent to widgets immediately before they are shown. The spontaneous show events of windows are delivered afterwards. Try to pump over the inquisitiveness, very much helps. Redefine showEvent and deliver inside . Look callstack. And only then already get a subject on rsdn.

3

Re: std:: exception and qt

Hello, SaZ, you wrote: SaZ> Hello, _hum _, you wrote: __>> and here what nuance in qt - why in __>> thrown inside window:: showEvent normal means with ++ the exception in cath does not get? SaZ> show it is necessary inside try to do. Well and RTFM: SaZ> SaZ> Non-spontaneous show events are sent to widgets immediately before they are shown. The spontaneous show events of windows are delivered afterwards. SaZ> Try to pump over the inquisitiveness, very much helps. Redefine showEvent and deliver inside . Look callstack. And only then already get a subject on rsdn. And where in dock it is written, what show does not put asynchronously event in event queue, and causes at once function showEvent? Resulted by you  word-for-word not spontaneous (?) Show-events are sent  at once before they gather . Spontaneous events of a window are delivered after [everywhere speech about sending and delivery of events, instead of about direct calls of functions]

4

Re: std:: exception and qt

Hello, _hum _, you wrote: __> [everywhere speech about sending and delivery of events, instead of about direct calls of functions] Well esteem textbooks on Qt. Then, to be caught up,  qt. Then, if carries, understand that the virtual methods of type showEvent it only the helpers working on events not to fence large switch and not to fence permanently overload QObject:: event.

5

Re: std:: exception and qt

Hello, SaZ, you wrote: SaZ> Hello, _hum _, you wrote: __>> [everywhere speech about sending and delivery of events, instead of about direct calls of functions] SaZ> Well esteem textbooks on Qt. Then, to be caught up,  qt. SaZ> Then if carries, understand that the virtual methods of type showEvent it only the helpers working on events not to fence large switch and not to fence permanently overload QObject:: event." Working on events "- unless it does not mean that actuating of these  goes at arrival of events. And for this purpose it is necessary, that earned  event queues. And start exec is for this purpose necessary? The item with. Textbooks are read. And on source codes to climb... Well we already in this respect conducted conversation is the same what to climb in car interiors only to understand as it to get and control for relocation from a point and in a point - to mechanics it it is interesting, and that who uses a car as means of transportation - superfluous expenditure of time.

6

Re: std:: exception and qt

Hello, _hum _, you wrote: __> "working on events" - unless it does not mean that actuating of these  goes at arrival of events. And for this purpose it is necessary, that earned  event queues. And start exec is for this purpose necessary? Does not mean. Events separately, event queue - separately. Queue +  magnifiers it only one of mechanisms of delivery of messages. __> the item with. Textbooks are read. And on source codes to climb... Well we already in this respect conducted conversation is the same what to climb in car interiors only to understand as it to get and control for relocation from a point and in a point - to mechanics it it is interesting, and that who uses a car as means of transportation - superfluous expenditure of time. All right, it is useless. At you simply mentality such. Everything that I itself do not understand I will ask at a forum because something I do not want to do, I want ready answers to all questions.

7

Re: std:: exception and qt

Hello, SaZ, you wrote: SaZ> Hello, _hum _, you wrote: __>> "working on events" - unless it does not mean that actuating of these  goes at arrival of events. And for this purpose it is necessary, that earned  event queues. And start exec is for this purpose necessary? SaZ> does not mean. Events separately, event queue - separately. Queue +  magnifiers it only one of mechanisms of delivery of messages. Well here see, all me reproach in , and instead of more in detail explaining how such can be (as can be sent and reach the message the addressee, passing magnifiers), or to refer on  (in the end-ends, simply to specify in what a gap in my knowledge), give minimum informative answer. __>> the item with. Textbooks are read. And on source codes to climb. . Well we already in this respect conducted conversation is the same what to climb in car interiors only to understand as it to get and control for relocation from a point and in a point - to mechanics it it is interesting, and that who uses a car as means of transportation - superfluous expenditure of time. SaZ> it is fine, it is useless. At you simply mentality such. Everything that I itself do not understand I will ask at a forum because something I do not want to do, I want ready answers to all questions. To do and understand - different things. I do all, and those moments which enter into lockup, I specify.

8

Re: std:: exception and qt

__> and here what nuance in qt - why in... __> thrown inside window:: showEvent normal means with ++ the exception in cath does not get? Therefore as OUT OF the controllable unit. Standard With ++ catches only that arises in the controllable unit.

9

Re: std:: exception and qt

Hello, LaptevVV, you wrote: __>> and here what nuance in qt - why in LVV>... __>> thrown inside window:: showEvent normal means with ++ the exception in cath does not get? LVV> therefore as OUT OF the controllable unit. LVV> standard With ++ catches only that arises in the controllable unit. Here a question in other. _hum_ erraticly considered that time  it is mandatory should be postponed and to be added in the end of queue of an operation cycle of messages. Therefore expected that  takes off inside exec. But it not so about what it is written to documentation and that can be checked up elementarily.

10

Re: std:: exception and qt

Hello, SaZ, you wrote: SaZ> Hello, LaptevVV, you wrote: __>>> and here what nuance in qt - why in LVV>>... __>>> thrown inside window:: showEvent normal means with ++ the exception in cath does not get? LVV>> therefore as OUT OF the controllable unit. LVV>> standard With ++ catches only that arises in the controllable unit. SaZ> here a question in other. _hum_ erraticly considered that time  it is mandatory should be postponed and to be added in the end of queue of an operation cycle of messages. Therefore expected that  takes off inside exec. So it is exact SaZ> But it not so about what it is written to documentation and that it is possible to check up elementarily. Well SaZ, well where there to documentation it is written? Well you in the business.

11

Re: std:: exception and qt

Hello, LaptevVV, you wrote: __>> and here what nuance in qt - why in LVV>... __>> thrown inside window:: showEvent normal means with ++ the exception in cath does not get? LVV> therefore as OUT OF the controllable unit. LVV> standard With ++ catches only that arises in the controllable unit. I thought that the call show simply puts event so,  will not be in queue, does not twirl yet exec. And till now I can not understand, why everywhere in docks there is a speech about events, but these events as states SaZ, not are obliged to transit all through a cycle. You can share reasons (for SaZ considers it below the advantage) in this respect?

12

Re: std:: exception and qt

Hello, _hum _, you wrote: __> Hello, LaptevVV, you wrote: __>>> and here what nuance in qt - why in LVV>>... __>>> thrown inside window:: showEvent normal means with ++ the exception in cath does not get? LVV>> therefore as OUT OF the controllable unit. LVV>> standard With ++ catches only that arises in the controllable unit. __> I thought that the call show simply puts event so,  will not be in queue, does not twirl yet exec. And till now I can not understand, why everywhere in docks there is a speech about events, but these events as states SaZ, not are obliged to transit all through a cycle. You can share reasons (for SaZ considers it below the advantage) in this respect? Not all are obliged to transit through queue. It is the method of implementation selected by authors Qt. They do not use  magnifiers there where it is not necessary. And about the documentation - I already gave the reference and the citation.

13

Re: std:: exception and qt

Hello, SaZ, you wrote: SaZ> Hello, _hum _, you wrote: __>> Hello, LaptevVV, you wrote: __>>>> and here what nuance in qt - why in LVV>>>... __>>>> thrown inside window:: showEvent normal means with ++ the exception in cath does not get? LVV>>> therefore as OUT OF the controllable unit. LVV>>> standard With ++ catches only that arises in the controllable unit. __>> I thought that the call show simply puts event so,  will not be in queue, does not twirl yet exec. And till now I can not understand, why everywhere in docks there is a speech about events, but these events as states SaZ, not are obliged to transit all through a cycle. You can share reasons (for SaZ considers it below the advantage) in this respect? SaZ> not all are obliged to transit through queue. It is the method of implementation selected by authors Qt. They do not use  magnifiers there where it is not necessary. SaZ where about it it is possible to esteem? What keywords at least? SaZ> and about the documentation - I already gave the reference and the citation. You cited: not spontaneous show-events are sent  at once before they gather . Spontaneous events of a window are delivered after where in it is said what sending is carried out passing magnifiers?

14

Re: std:: exception and qt

Hello, _hum _, you wrote: __>... __> you cited: __> __> not spontaneous show-events are sent  at once before they gather . Spontaneous events of a window are delivered after __> where in it is said what sending is carried out passing magnifiers? Where it is said, what they are sent through magnifiers?

15

Re: std:: exception and qt

Hello, SaZ, you wrote: SaZ> Hello, _hum _, you wrote: __>>... __>> you cited: __>> __>> not spontaneous show-events are sent  at once before they gather . Spontaneous events of a window are delivered after __>> where in it is said what sending is carried out passing magnifiers? SaZ> where it is said, what they are sent through magnifiers? And where in it it is said, what are not delivered through magnifiers? Standard  deliveries of events is magnifiers. We read in dock on qt: wiki.qt.io/, Events and QObjects as Event in Qt is called the object representing something interesting from event; principal difference of events from signals is that events are intended for specific object in our application (which decides that with this event to do), and signals "walk in itself". From the point of view of the code all events are objects of any subclass QEvent, and all derivative from Object classes can redefine the virtual method QObject:: event () for operation with the events intended for given object. Events can be generated as inside, and outside of application [...] the Important point is that events come not as soon as they have been generated; instead they get to event queue and come later. The manager cyclicalally processes event queue and sends events at destination, therefore it is called as an operation cycle of events

16

Re: std:: exception and qt

Hello, SaZ, you wrote: SaZ> Well esteem textbooks on Qt. Then, to be caught up,  qt. "-1" council good, tone of bad.

17

Re: std:: exception and qt

Hello, Skorodum, you wrote: S> Hello, SaZ, you wrote: SaZ>> Well esteem textbooks on Qt. Then, to be caught up,  qt. S> "-1" council good, tone of bad. Probably. We here for a long time already  in such spirit. And ratings basically do not excite me

18

Re: std:: exception and qt

Hello, SaZ, you wrote: S>> "-1" Council good, tone of bad. SaZ> it is possible. We here for a long time already  in such spirit. I would like to see more civilized discussions on , especially in professional sections, therefore I expressed the relation. SaZ> and ratings me basically do not excite Minuses on a rating do not influence.

19

Re: std:: exception and qt

Hello, Skorodum, you wrote: S> Hello, SaZ, you wrote: S>>> "-1" Council good, tone of bad. SaZ>> it is possible. We here for a long time already  in such spirit. S> I would like to see more civilized discussions on , especially in professional sections, therefore I expressed the relation. Thanks, I will agree. I will try S> Minuses on a rating do not influence. Yes, I in course. In due time used for a basis system of a rating rsdn for one own development.

20

Re: std:: exception and qt

Hello, SaZ, you wrote: SaZ> Hello, _hum _, you wrote: __>>... __>> you cited: __>> __>> not spontaneous show-events are sent  at once before they gather . Spontaneous events of a window are delivered after __>> where in it is said what sending is carried out passing magnifiers? SaZ> where it is said, what they are sent through magnifiers? SaZ so you answer was informatively (with instructions at least books in which about such situation with  to necessity of passage through event magnifiers, it has been written) on a question?

21

Re: std:: exception and qt

Hello, _hum _, you wrote: __> SaZ so you answer was informatively (with instructions at least books in which about such situation with  to necessity of passage through event magnifiers, it has been written) on a question? No. Since it is improbable that authors Qt wrote the book about why they made so. I do not see sense to answer, for the real problem for which decision generally such reasonings could be necessary is not specified. If it is "simply interesting", it is possible to open source codes and to esteem. There anything difficult is not present.

22

Re: std:: exception and qt

Hello, SaZ, you wrote: SaZ> Hello, _hum _, you wrote: __>> SaZ so you answer was informatively (with instructions at least books in which about such situation with  to necessity of passage through event magnifiers, it has been written) on a question? SaZ> I do not see sense to answer, for the real problem for which decision generally such reasonings could be necessary is not specified. Generally, because of this misunderstanding I made a program error, and you speak "I do not see a problem" (I want to understand once and for all with it then not to bother you with foolish questions "why does not work") SaZ> Are not present. Since it is improbable that authors Qt wrote the book about why they made so. SaZ> If it is "simply interesting", it is possible to open source codes and to esteem. There anything difficult is not present. So and 1) what for then they write in docks about that all events transit through magnifiers: wiki.qt.io/, Events and QObjects as Event in Qt is called the object representing something interesting from event; principal difference of events from signals is that events are intended for specific object in our application (which decides that with this event to do), and signals "walk in itself". From the point of view of the code all events are objects of any subclass QEvent, and all derivative from Object classes can redefine the virtual method QObject:: event () for operation with the events intended for given object. Events can be generated as inside, and outside of application [...] Important point is that events come not as soon as they have been generated; instead they get to event queue and come later. The manager cyclicalally processes event queue and sends events at destination, therefore it is called as an operation cycle of events 2) what for generally to speak about event sending if there is the synchronous method call (what sense to use this term, instead of for example, simply to write "by a call show there is a method call showEvent"); 3) how further to learn, what mechanism is meant words "events" - through magnifiers or with its involvement are sent, without rummaging in source codes; 4) unless from source codes it is possible to rely on the information - after all, in upcoming version they can change these source codes easily.

23

Re: std:: exception and qt

SaZ, it you do not note my questions, or do not consider it necessary to note them (me simply that the nobility on the future, what you the person as the interlocutor)?

24

Re: std:: exception and qt

Hello, _hum _, you wrote: __> SaZ, it you do not note my questions, or do not consider it necessary to note them (me simply that the nobility on the future, what you the person as the interlocutor)? For forums normally to give answers when the person considers it necessary and can really answer. So knowledge to what I the interlocutor to you are not necessary. I think that on operation we  appear in one command for I am very rigid  on Qt.> generally, because of this misunderstanding I made a program error, and you speak "I do not see a problem" (I want to understand once and for all with it then not to bother you with foolish questions "why does not work") Well so tell that for an error. It is interesting to all. Can something is valid standing and costs  to a bug  on not expected behavior or on documentation finishing. Though to me, for some reason it seems that you had a normal working moment which is not necessary special attention.  and it is excellent, the employer is happy, you too. Simply it turns out that I set leading questions, and instead of definite answers there is a sensation that the answer is necessary to you not, and to someone something to prove.

25

Re: std:: exception and qt

Hello, SaZ, you wrote: SaZ> Hello, _hum _, you wrote: __>> SaZ, it you do not note my questions, or do not consider it necessary to note them (me simply that the nobility on the future, what you the person as the interlocutor)? SaZ> For forums normally to give answers when the person considers it necessary and can really answer. So knowledge to what I the interlocutor to you are not necessary. I think that on operation we  appear in one command for I am very rigid  on Qt. If reversal goes to this person to keep silent is at least to leave the interlocutor in ignorance that the such happened that dialogue so sharply broke.>> generally, because of this misunderstanding I made a program error, and you speak "I do not see a problem" (I want to understand once and for all with it then not to bother you with foolish questions "why does not work") SaZ> Well so tell that for an error. It is interesting to all. Can something is valid standing and costs  to a bug  on not expected behavior or on documentation finishing. Though to me, for some reason it seems that you had a normal working moment which is not necessary special attention.  and it is excellent, the employer is happy, you too. SaZ> Simply it turns out that I set leading questions, and instead of definite answers there is a sensation that the answer is necessary to you not, and to someone something to prove. SaZ, the error fasted in the very first my message. Also there was it because of ignorance of nuance with show (). If you the expert why so it is difficult to you to answer the elementary questions, which that you not to trouble with subject review,  anew: 1) what for then they write in docks about that all events transit through magnifiers: wiki.qt.io/, Events and QObjects as Event in Qt is called the object representing something interesting from event; Principal difference of events from signals is that events are intended for specific object in our application (which decides that with this event to do), and signals "walk in itself". From the point of view of the code all events are objects of any subclass QEvent, and all derivative from Object classes can redefine the virtual method QObject:: event () for operation with the events intended for given object. Events can be generated as inside, and outside of application [...] Important point is that events come not as soon as they have been generated; instead they get to event queue and come later. The manager cyclicalally processes event queue and sends events at destination, therefore it is called as an operation cycle of events 2) what for generally to speak about event sending if there is the synchronous method call (what sense to use this term, instead of for example, simply to write "by a call show there is a method call showEvent"); 3) how further to learn, what mechanism is meant words "events" - through magnifiers or with its involvement are sent, without rummaging in source codes; 4) unless from source codes it is possible to rely on the information - after all, in upcoming version they can change these source codes easily.