ios - Who's responsible for calling viewWillLayoutSubviews()/viewDidLayoutSubviews() in a custom UIViewController container? -

-

एक कस्टम UIViewController कंटेनर (एक UIViewController UIViewControllers और उनके विचार) जो कॉल करने के लिए जिम्मेदार है और? मेरे कंटेनर वर्ग के पास दो उप-नियंत्रक हैं, जिनमें से न तो इन विधियों को माता-पिता के दृश्य नियंत्रक में ले जाने पर बुलाया जाता है।

UIViewController के दस्तावेज को ट्रिगर करने के तरीके के रूप में प्रलेखित किया गया है viewWillAppear () , देखेंविलिसआप () , viewDidAppear () , और viewDidDisappear () लेकिन मुझे viewWillLayoutSubviews () / viewDidLayoutSubviews () ।

सबसे अच्छा के रूप में मैं मूल उपयोक्ता नियंत्रक (जो इस मामले में प्रस्तुत किया जा रहा है) को पहचान सकता है इसके उप-नियंत्रक कॉल करने के लिए जिम्मेदार है देखेंविल्लेआउटस्यूव्यूज () / देखेंडिडलेआउटसमूह दृश्य () उन तरीकों के अपने स्वयं के कार्यान्वयन में कुछ परिस्थितियों में ढांचे के इन तरीकों को कॉल करने के लिए लगता है (जैसा कि आप rootViewController UIWindow की संपत्ति सेट करते हैं) परन्तु अन्य नहीं (जैसे जब आप addChildViewController () कॉल करते हैं) / Code> में UIViewController )।

क्या यह चीजों के बारे में जाने के लिए सही, मुहावरेदार तरीका है?

दृश्य देखने के लिए कौन जिम्मेदार है? दृश्य और दृश्यडिडलाउज़स्यूब दृश्य?

रनटाइम आपको इन तरीकों से स्वयं कभी कॉल नहीं करना चाहिए।


Comments

Post a Comment

Popular posts from this blog

apache - 504 Gateway Time-out The server didn't respond in time. How to fix it? -

-
Using a form submission on an embedded iframe , the customer downloads a compressed log file Requested. The request was sent to the server, which is the compressed log files, perform some database operations and returns a compressed file. After just 2 minutes, 504 gateway time-out server did not respond timely message on browser net panel How to fix this error? The log files were taking a long time to compress, and timeout was set to 2min The error was fixed by extending the file file: # # timeout: The number of seconds before getting the time out. # # # Timeout 120 timeout 600
Read more

c# - .net WebSocket: CloseOutputAsync vs CloseAsync -

-
We have a working ASP.NET Web API REST service, which is one of the methods of our controller, HTTPTTEX. .) Socket handler code looks something like this ... Public async task socket handler (AspNetWebSocketContext context) {_webSocket = context.WebSocket; ... while (! Cts.IsCancellationRequested) {WebSocketReceiveResult Results = _webSocket.ReceiveAsync (Input Segment, cts.Token) .Result; WebSocketsStateCollusocketState = _webSocket.State; If (result.MessageType == WebSocketMessageType.Close || currentSocketState == WebSocketState.CloseReceived) {// What should I use. CloseAysnc () or. CloseOutputAsync ()? _webSocket.CloseOutputAsync (WebSocketCloseStatus.NormalClosure, "Client Requested", cts.Token). Wait (); } If (currentSocketState == WebSocketState.Open) {...}}} .What is the difference between .CooseAsync () and CloseOutputAysnc ()? I tried both of them and they both seemed to work fine but some difference should be the same they both describe very similar to...
Read more

c++ - How to properly scale qgroupbox title with stylesheet for high resolution display? -

-
I am trying to apply a stylesheet for QGroupBox (QT4.8), which works on the normal screen ( 96 dpi) high resolution screen (Yoga 2 Pro, 3200x1800, 275 dpi, windows 8.1). The following style looks good on the 275 dpi screen, but the top margins on a regular 96 dpi screen are far too big. QGroupBox {border: 1px solid red; Range radius: 7px; Margin-top: 12x; } QGroupBox :: Title {subcontrol-origin: margin; Subcontrol-position: left above; Padding-left: 10px; Padding-right: 10px; } Changing the top-margin has an effect, but I did not get a proper setting which works on both screens. If I shorten the value, the content of the group box overlaps with the title on 275 dpi screen. I was also playing with units "East", "PX", "MX", "PT". Reading the document I would have guessed, "2 X" was the correct solution, which should be scaled with different screen resolutions. Without the stylesheet, the groupbox works well on both screens. ...
Read more