Received: by 10.52.73.100 with SMTP id k4mr13315655vdv.5.1318843723354;
        Mon, 17 Oct 2011 02:28:43 -0700 (PDT)
X-BeenThere: android-developers@googlegroups.com
Received: by 10.220.149.17 with SMTP id r17ls636052vcv.0.gmail; Mon, 17 Oct
 2011 02:27:39 -0700 (PDT)
Received: by 10.220.141.200 with SMTP id n8mr1368583vcu.22.1318843659114;
        Mon, 17 Oct 2011 02:27:39 -0700 (PDT)
Date: Mon, 17 Oct 2011 02:27:38 -0700 (PDT)
From: kaciula <catalin.moro...@gmail.com>
Reply-To: android-developers@googlegroups.com
To: android-developers@googlegroups.com
Message-ID: <21297068.721.1318843658653.JavaMail.geo-discussion-forums@vbza28>
In-Reply-To: <CALLdnhPofj4EuooYgHAEbsAjFbt_FucVCzJQJ2RXwKedD_EFKw@mail.gmail.com>
References: <7619709.586.1317994154884.JavaMail.geo-discussion-forums@yqmn40>
 <7667531.600.1318334026769.JavaMail.geo-discussion-forums@vbbek10>
 <CALLdnhNXzq5qvytGh5x9Yo9o7XUjhB9S_2aS7xDo_EE4K93UuA@mail.gmail.com> <13773489.2564.1318347269764.JavaMail.geo-discussion-forums@yqai1>
 <CALLdnhPofj4EuooYgHAEbsAjFbt_FucVCzJQJ2RXwKedD_EFKw@mail.gmail.com>
Subject: Re: [android-developers] Re: Scenario where initLoader() does not
 call onLoadFinished()
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_719_3257046.1318843658651"

------=_Part_719_3257046.1318843658651
Content-Type: multipart/alternative; 
	boundary="----=_Part_720_13904585.1318843658652"

------=_Part_720_13904585.1318843658652
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

However, if I compile it using API Level 7 but run it on a tablet emulator I 
still can reproduce the problem. I thought that if you used the acl, when 
running on a honeycomb device, the built-in fragment implementation would be 
used. But I see that this is not the case here.

Regarding the configChanges workaround, what exactly are the problems that 
appear? Except for 
adding android:configChanges="keyboardHidden|orientation|keyboard|screenLayout", 
is there something else I should modify?

------=_Part_720_13904585.1318843658652
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

However, if I compile it using API Level 7 but run it on a tablet emulator I still can reproduce the problem. I thought that if you used the acl, when running on a honeycomb device, the built-in fragment implementation would be used. But I see that this is not the case here.<div><br></div><div>Regarding the configChanges workaround, what exactly are the problems that appear? Except for adding&nbsp;android:configChanges="keyboardHidden|orientation|keyboard|screenLayout", is there something else I should modify?</div>
------=_Part_720_13904585.1318843658652--

------=_Part_719_3257046.1318843658651--