On Sun, Aug 3, 2014 at 11:25 AM, luca wrote:
> i have a class that extends DialogFragment. The .xml used to create its
> view is selected by calling a specific method of the activity (let's call
> it getData())
Your DialogFragment should not be calling into a custom Activity to
determine its be
Hi,
i have a class that extends DialogFragment. The .xml used to create its
view is selected by calling a specific method of the activity (let's call
it getData())
(there are three different xml: one showing only three buttons, one showing
a seek bar and three buttons and one showing two seekb
Hi,
i have a class that extends DialogFragment. The .xml used to create its
view is selected by calling a specific method of the activity (let's call
it getData())
(there are three different xml: one showing only three buttons, one showing
a seek bar and three buttons and one showing two seekb
Am Donnerstag, 30. Januar 2014 00:01:56 UTC+1 schrieb TreKing:
>
> You are creating a new Dialog in your onCreate method. onCreate gets
> called both the first time the app is run (with savedInstanceState set to
> null) and after an orientation (configuration) change, with
> savedInstanceState s
You are creating a new Dialog in your onCreate method. onCreate gets called
both the first time the app is run (with savedInstanceState set to null)
and after an orientation (configuration) change, with savedInstanceState
set to the last saved state Bundle.
In the latter case, the system also auto
Dear readers,
i experienced a double call to onCreateDialog also to onCreateView in my
project.
here is my activity code:
public class DialogTestActivity extends Activity {
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
I've created a DialogFragment sub-class and when done i
call dialog.dismiss() to close the dialog.
but i'd like it not to be destroyed - so that i don't have to
go thru the creation process again.
the dialog gets displayed and closed quite often.
you guessed it - how do i do it?
--
--
You rec
The code works - since i was testing i tried a simple layout with
nothing in it and the dialog was displaying transparently.
duh!
--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers
I have never used that code. Here is a sample project that just uses show():
https://github.com/commonsguy/cw-omnibus/tree/master/Dialogs/DialogFragment
On Mon, Feb 18, 2013 at 11:24 AM, dashman wrote:
>
> Re-direct - but straight to the point. appreciate it.
>
> i copied this code from android
On Monday, February 18, 2013 11:24:56 AM UTC-5, dashman wrote:
>
>
> Re-direct - but straight to the point. appreciate it.
>
>
>
--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@g
Re-direct - but straight to the point. appreciate it.
i copied this code from android docs to display a DialogFragment
FragmentTransaction transaction =
fragmentManager.beginTransaction();
transaction.setTransition(FragmentTransaction.TRANSIT_FRAGMENT_OPEN);
/
http://stackoverflow.com/questions/14803338/advantage-of-using-a-dialogfragment-over-simple-alertdialog/14803385#14803385
On Mon, Feb 18, 2013 at 10:45 AM, dashman wrote:
> What's the advantage of DialogFragment?
>
> Over just creating AlertDialog in the Activity class.
>
>
> --
> --
> You receiv
What's the advantage of DialogFragment?
Over just creating AlertDialog in the Activity class.
--
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from
Ok, all is working now.
The problem came from wanting to only enable the "ok" button once a minimum
number of characters had been entered.
I was doing this through setOnKeyListener - this blocked the soft keyboard
appearing automatically (if the user touched the edittext, the soft
keyboard showe
Do any of these attributes help? In particular I am thinking of the
stateVisible or stateAlwaysVisible options:
http://developer.android.com/guide/topics/manifest/activity-element.html#wsoft
Thanks,
Justin Anderson
MagouyaWare Developer
http://sites.google.com/site/magouyaware
On Mon, Jul 16, 2
Everything around the Android keyboard feels hacky.
Try one of the following:
1) Set in your XML in the edittext.
2) do a post such as et.post(new Runnable() { et.requestFocus() }} etc.
3) do a post again but your use own code in your original post.
Good luck.
On Monday, July 16, 2012 9:26:4
Yes, I use this as well, but forgot to include it in the code I posted here.
On Monday, 16 July 2012 18:06:41 UTC+2, Kostya Vasilyev wrote:
>
> Have you tried "et.requestFocus()" ?
>
> 2012/7/16 Simon Giddings
>
>> I have a simple dialog built with the compatibility libraries
>> DialogFragment.
Have you tried "et.requestFocus()" ?
2012/7/16 Simon Giddings
> I have a simple dialog built with the compatibility libraries
> DialogFragment.
> It holds only
>
>1. EditText
>2. 2 buttons
>
> When the dialog is shown, the edit text control has the focus.
> At this point, I want to open
I have a simple dialog built with the compatibility libraries
DialogFragment.
It holds only
1. EditText
2. 2 buttons
When the dialog is shown, the edit text control has the focus.
At this point, I want to open the soft keyboard automatically.
Here is what I am doing within the onCreateVi
Consider showDialog() / managed dialogs to be deprecated.
On Apr 25, 2011 12:30 PM, "Dave Johnston" wrote:
> Honeycomb introduced the DialogFragment class for producing dialogs.
> Pre-Honeycomb, applications were encouraged to use managed dialogs
> handled by their owning Activity via showDialog,
Honeycomb introduced the DialogFragment class for producing dialogs.
Pre-Honeycomb, applications were encouraged to use managed dialogs
handled by their owning Activity via showDialog, dismissDialog etc.
Looking forward, should DialogFragments be preferred over Activity
managed dialogs, or should
21 matches
Mail list logo
