OK I tried that - no luck - it's not getting to the constructor
*BUT* - while testing it I got a new clue. It launches the SECOND
time I try it, consistently, Here's the extracted Logcat - you can see
that the first time it never gets past Starting Intent, the second time it
goes all
I think the discovery of the bizarre double-launch behavior puts a
different spin on this, so I've started a new thread. Please direct all
further comments or suggestions to the new thread:
https://groups.google.com/forum/?fromgroups=#!topic/android-developers/4js6GASVZc4
Thanks.
On Thursday, April 4, 2013 1:57:36 PM UTC-4, plnelson wrote:
I think the discovery of the bizarre double-launch behavior puts a
different spin on this, so I've started a new thread. Please direct all
further comments or suggestions to the new thread:
Here's another detail:If I set DGraphActivity's launchmode to
singleInstance the logcat shows this . . .
*03-31 18:49:12.224: I/ActivityManager(119): Starting: Intent {
flg=0x400 cmp=com..remote/.DGraphActivity (has extras) } from pid
19024
03-31 18:49:12.298:
Maybe you could add one more log statement:
Add a default constructor and print a log statement. This would check if
the DGraphActivity instance is created or not:
public DGraphActivity () {
// Print out a log statement that this code here is reached properly.
}
If this constructor is
On Friday, March 29, 2013 7:06:59 PM UTC-4, Streets Of Boston wrote:
Log.*e*(Commands, failed to start DGraphActivity*, e*);
OK, I've added that although, since it's not hitting that (or any)
exceptions it's not really telling me anything.
So we're still kinda back on the original
Technically it needs a . here:
activity android:name=.DGraphActivity
^
or the full package name.
On Friday, March 29, 2013 8:02:04 PM UTC, plnelson wrote:
This question has (so far) stumped them on Stack Overflow. . . .
I'm trying to launch an Activity which
Look at your logcat and see why your activity can't be started. Could be as
simple as a typo in your manifest.
On Friday, March 29, 2013 4:02:04 PM UTC-4, plnelson wrote:
This question has (so far) stumped them on Stack Overflow. . . .
I'm trying to launch an Activity which launches
On Friday, March 29, 2013 5:57:46 PM UTC-4, Streets Of Boston wrote:
Look at your logcat and see why your activity can't be started. Could be
as simple as a typo in your manifest.
I only see things in LogCat about DGraphActivity when it *does* start
(ie., when its launchMode is
On Friday, March 29, 2013 10:40:44 PM UTC, plnelson wrote:
RichardC wrote
Technically it needs a . here:
activity android:name=.DGraphActivity
I'm skeptical. My program has about 20 Activities and none of them have
.'s in front of the name and I've written a lot of other
I've never seen this. If it fails to start, i get a logcat message and an
exception is thrown (and you are catching that).
Have you tried to set the Intent.FLAG_ACTIVITY_NEW_TASK flag when starting
the activity?
On Friday, March 29, 2013 6:40:44 PM UTC-4, plnelson wrote:
On Friday, March
Also, change the catching of your try - catch block, so that you see more
of the exception being thrown when the activity fails to start:
Log.*e*(Commands, failed to start DGraphActivity*, e*);
This would allow you to see more info of what may go wrong.
On Friday, March 29, 2013 7:04:39 PM
On Friday, March 29, 2013 7:04:39 PM UTC-4, Streets Of Boston wrote:
I've never seen this. If it fails to start, i get a logcat message and an
exception is thrown (and you are catching that).
*My bad* - it turned out it did have a filter on. (thanks for saying you
never saw that - it
13 matches
Mail list logo
