How to use both Android.App.Fragment and Support V4 library -

-

I want to use a support library to add a new El Style actionbase to my app. So I changed my activity to a ActionBarActivity now I have both getFragmentManager () and getSupportFragmentManager () .

I use getFragmentManager () to work with pieces and they are provided fine but when I get backstack ( (mTransaction.addToBackStack ("blabla" ), Then there is a problem, the backstack remains empty, so if I call mTransaction.commit () and immediately after getFragmentManager (). GetBackStackEntryCount () After 0 will return no matter how much transaction I do, as a result, in my first section of the section, without first navigation, "BACK"

Why do not I use pieces from the help library? I do not care for the app 15 and new & lt; 11 and to migrate There is a lot of code besides this, if the help library is used then I will not be able to use the objectAnimator for the transition. This is not a disaster, but I just want to improve one more addendum Do not want to be a part of an app.

So the question - is it possible to fix the stack back or support me all the related code-V4?

Edit: I was posting very fast before reading my question carefully. I have looked through source code and I highly recommend using getSupportFragmentManager () if the reason for using ActionBarActivity is that the implementation of Fragment Manager mFragments Has been shrouded in fragment activity and it is used in all activity life cycle if super classes using getFragmentManager () will be implemented. And you have to rely on fragment activity to make a super call at the right time, otherwise there may be disturbance in the life cycle. With onBackpressed () you have already searched for a case where fragmentation fails to make super call to activity.

Another solution would have to migrate but you lose some of the ActionBarActivity stuff eg. Widget-tinting and childfraggument manager.

I paste only with support implementation.

This is the basic answer and does not really apply here:

One piece transaction does not immediately add / replace your piece, so your back stack You will still be able to call getFragmentManager (). ExecutePendingTransactions () If this is really necessary.

BTW: Why do you stop using the ObjectEnimeter by using the support library?


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