setContentView() replaces any existing views. If you want finer-
grained control, you can setContentView() a top-level layout manager,
which you can then add and remove views in as you desire.
Would you please provide a little more information? I loaded
R.layout.main by setContentView(), then added a view with
addContentView. I need to remove the view added by addContentView by
clicking a button.
I know it is old but I have the same problem. I want next to change the view
added by addContentView. Indeed recalling addContenView throws an Exception
05-19 22:28:31.785: ERROR/AndroidRuntime(11210):
java.lang.IllegalStateException: The specified child already has a parent.
You must call removeView() on the child's parent first.
I have been trying to send the message below since yesterday and I
have tried posting it two times. I am not able to see it getting
posted to the group. Can you please let me know why?
Posting the following e-mail:
---------- Forwarded message ----------
From: Ray <pamoned...@gmail.com>
Date: Mon, Oct 18, 2010 at 1:01 PM
Subject: App design question for multiple "data" connections
To: Android Developers <email@example.com>
I am working on developing an application that requires me to
establish multiple client-server based connections. Connection can be
of two types where the Android device can be a server or a client. I
can have up to 6 - 8 connections. Once the connections are set-up they
need to be running in the background and are not typically affected by
Since each connection can be blocking, I am wondering what is a good
way to design this app. Should I have two services for handling the
server and client connections? Each service could have a "connection
manager" that can spawn new threads when necessary. Or does creating
two services even help? I presume spawning new processes would not be
good as they will be expensive.
I would appreciate any suggestions. Also, if this use case is not
typical please let me know if you need more information to make any