I got it working, somehow it was crashing because I wasn't assigning
the ID I created for a button to any handler, strange.
On Aug 1, 8:11 am, DB12 wrote:
> mAddCoInfo = (EditText) findViewById(R.id.addCoInfo);
> mAddPltInfo = (EditText) findViewById(R.id.addPltInfo);
> mA
On Mon, Aug 1, 2011 at 7:11 AM, DB12 wrote:
>mAddData = (Button) findViewById(R.id.addData);
>mPickDate = (Button) findViewById(R.id.pickDate);
>
I don't know which of these is line 60, but what I would do is replace this
with:
View temp1 = findViewById(R.id.addData);
View temp2
mAddCoInfo = (EditText) findViewById(R.id.addCoInfo);
mAddPltInfo = (EditText) findViewById(R.id.addPltInfo);
mAddSquadInfo = (EditText) findViewById(R.id.addSquadInfo);
mPickWeapon = (EditText) findViewById(R.id.pickWeapon);
mPickDist = (EditText) findViewBy
On Friday, July 29, 2011 12:58:04 PM UTC-4, DB12 wrote:
>
> Adam, that makes some sense, I'll investigate it.
>
> I took my app home from work and for some reason it did not crash when
> I added that 3rd id (my home comp runs windows 7). Then I took it
> back to work (where we have xp) and it w
On Fri, Jul 29, 2011 at 12:01 PM, DB12 wrote:
> E/AndroidRuntime( 351): Caused by:
> java.lang.ClassCastException: android.widget.Button
> E/AndroidRuntime( 351):
> at com.alion.android.rangecard.MainActivity.onCreate(MainActivity.java:60)
>
OK. And now the code at and around your onCreate me
heres the log
D/AndroidRuntime( 344):
D/AndroidRuntime( 344): >> AndroidRuntime START
<<
D/AndroidRuntime( 344): CheckJNI is ON
D/AndroidRuntime( 344): --- registering native functions ---
D/ddm-heap( 344): Got feature list request
I/ActivityManager( 52): Starting ac
Adam, that makes some sense, I'll investigate it.
I took my app home from work and for some reason it did not crash when
I added that 3rd id (my home comp runs windows 7). Then I took it
back to work (where we have xp) and it works fine with the extra id.
But then I added another custom dialog wi
On Wednesday, July 27, 2011 9:11:08 AM UTC-4, DB12 wrote:
>
> the app crashes when you try to load it, i don't even get to press the
> button that opens my custom dialog
>
> On Jul 22, 11:41 am, DB12 wrote:
> > Howdy, I searched for about 30 minutes to see if anyone had the same
> > issue but
I tried several different id names and none of them worked, but I just
tried my app on a different computer and it worked fine with three
button id's in the dialog (which is what crashed the emulator on my
other one ). I will try to recreate the problem on the original
computer and post the full l
On Wed, Jul 27, 2011 at 9:34 AM, DB12 wrote:
> if im reading it correctly it says
> "java.lang.ClassCastException: android.widget.button"
>
You want to just post the full stack trace you get? Particularly the part
including and after the "Caused by" line.
is there a limit to the amount of butto
if im reading it correctly it says "java.lang.ClassCastException:
android.widget.button"
is there a limit to the amount of buttons you can have in a custom
dialog?
On Jul 27, 9:11 am, Raghav Sood wrote:
> I think TreKing meant what is the logcat or stacktrace?
>
>
>
>
>
>
>
>
>
> On Wed, Jul 27,
I think TreKing meant what is the logcat or stacktrace?
On Wed, Jul 27, 2011 at 6:37 PM, DB12 wrote:
> it crashes as soon as the app loads, before I even push the button to
> display my custom dialog
>
> On Jul 26, 11:40 am, TreKing wrote:
> > On Fri, Jul 22, 2011 at 10:41 AM, DB12 wrote:
> >
the app crashes when you try to load it, i don't even get to press the
button that opens my custom dialog
On Jul 22, 11:41 am, DB12 wrote:
> Howdy, I searched for about 30 minutes to see if anyone had the same
> issue but couldn't find anything.
>
> I have a custom dialog I created with a relativ
it crashes as soon as the app loads, before I even push the button to
display my custom dialog
On Jul 26, 11:40 am, TreKing wrote:
> On Fri, Jul 22, 2011 at 10:41 AM, DB12 wrote:
> > and this one gives me a force close runtime exception when my app starts
>
> And the exception would be ... ?
>
>
14 matches
Mail list logo
