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.