How can I make use of adb logcat, DDMS, or the DDMS perspective in
Eclipse if I can't reproduce the error in the emulator? It doesn't
crash there.
Have I implemented the right aproach with the threads? I call on
yield() on the 2d thread for every
onResume() and onPause() call to the 2d activity.
Or maybe the objects in the 3d activity are not garbage collected when
I switch to the 2d activity? Maybe I should set the objects in the 3d
activity to null, when it switches to the 2d activity?
On Sep 22, 9:11 pm, Mark Murphy mmur...@commonsware.com wrote:
Use adb logcat, DDMS, or the DDMS
You said it crashes on your Samsung device, can't you get a stack trace
there?
--
Kostya Vasilyev
23.09.2011 13:01 пользователь MobileVisuals eyv...@astralvisuals.com
написал:
Or maybe the objects in the 3d activity are not garbage collected when
I switch to the 2d activity? Maybe I should set
On Fri, Sep 23, 2011 at 4:11 AM, MobileVisuals eyv...@astralvisuals.com wrote:
How can I make use of adb logcat, DDMS, or the DDMS perspective in
Eclipse if I can't reproduce the error in the emulator? It doesn't
crash there.
adb logcat, DDMS, and the DDMS perspective of Eclipse are perfectly
Thanks, it got stable when I removed the finish() calls and added this
code to the 2d view class:
@Override
public void onWindowFocusChanged(boolean hasWindowFocus) {
if (!hasWindowFocus) {
thread.setRunning(false);
I thought that it worked like it should,but I noticed that this is not
the case. This version crashes sometimes, often when onResume() is
called on any of the activities. It crashes on my Samsung Galaxy
device. I have tried to reproduce this on the emulator, but it doesn't
crashes there. The
Does anyone have an idea what I can do to improve the stability of
this 3d app, which has 2 activities? I want to avoid the crashes.
On Sep 22, 1:14 pm, MobileVisuals eyv...@astralvisuals.com wrote:
I thought that it worked like it should,but I noticed that this is not
the case. This version
Use adb logcat, DDMS, or the DDMS perspective in Eclipse to examine
LogCat and figure out what the crashes are.
On Thu, Sep 22, 2011 at 2:43 PM, MobileVisuals eyv...@astralvisuals.com wrote:
Does anyone have an idea what I can do to improve the stability of
this 3d app, which has 2 activities?
Thanks for the info. I have redesigned the app now and it worked.
On Sep 20, 6:37 pm, Mark Murphy mmur...@commonsware.com wrote:
Use startActivity(), with FLAG_ACTIVITY_REORDER_TO_FRONT, to bring an
existing activity back into the foreground (or create it if it does
not exist).
On Tue, Sep
I got the viewflipper to work, but I found that it is not possible to
use a GLSurfaceView in a viewflipper, like this thread describes:
http://groups.google.com/group/android-developers/browse_thread/thread/66e38a36c1378cfb/1b890dfece8fcb8a#1b890dfece8fcb8a
How can I then switch between 2d and
Use two activities.
On Tue, Sep 20, 2011 at 9:54 AM, MobileVisuals eyv...@astralvisuals.com wrote:
I got the viewflipper to work, but I found that it is not possible to
use a GLSurfaceView in a viewflipper, like this thread describes:
I see, then I would have to use one SurfaceView for the first activity
and a GLSurfaceView for the other activity. I searched for information
about how to switch between 2 activities on the forum and found one of
your threads:
Use startActivity(), with FLAG_ACTIVITY_REORDER_TO_FRONT, to bring an
existing activity back into the foreground (or create it if it does
not exist).
On Tue, Sep 20, 2011 at 12:32 PM, MobileVisuals
eyv...@astralvisuals.com wrote:
I see, then I would have to use one SurfaceView for the first
13 matches
Mail list logo
