macOS Question about theory vs practice

[mdeh]

I am starting off on Hillegass book, and he talks about the "event queue". From the apple docs, some terms then a question.

Figure 1 shows the path of a user event....... through the system to the Carbon and Cocoa application environments. The event originates when the device driver that controls an input device.......... passes it to the window server. When the window server receives the event, ........ sends the event to the event port of the run loop ............. event manager .........passes it to the event-handling mechanism specific to the application environment
of the process.

How much of this is just of interest, and how much should one know in detail? So, for example, is the window server a conceptual representation of low level code, or does it really exist as an entity one can see in Xcode, for example? The same would apply to the terms "event loop" and "event port". Is it important, for example, to know which "event port" is being used, or how to find it or which "event manager" is currently active?

Sorry about the generality of this question, but often, on starting out, it 's nice to know the depth to which one should be looking, or just accept things as is for the time being.

 

[MrFusion]

I am starting off on Hillegass book, and he talks about the "event queue". From the apple docs, some terms then a question.




How much of this is just of interest, and how much should one know in detail? So, for example, is the window server a conceptual representation of low level code, or does it really exist as an entity one can see in Xcode, for example? The same would apply to the terms "event loop" and "event port". Is it important, for example, to know which "event port" is being used, or how to find it or which "event manager" is currently active?

Sorry about the generality of this question, but often, on starting out, it 's nice to know the depth to which one should be looking, or just accept things as is for the time being.

If you are just starting out, don't worry about it. In objective-c you send messages ([entity message]), which finds its way through the chain, until it reaches something that can respond to it.
Start worrying about it when you start using menuitems, IBAction's and the first responder chain.

 

[mdeh]

If you are just starting out, don't worry about it. In objective-c you send messages ([entity message]), which finds its way through the chain, until it reaches something that can respond to it.
Start worrying about it when you start using menuitems, IBAction's and the first responder chain.

Will do...thank you...but then I will be back!!!