change size of controls in a layout
by dillipk » Thu, 22 Apr 2010 03:32:36 GMT
Sponsored Links
Hi,
How do I change the size of the controls placed in a layout? (by any
method)
I tried to change the height of an EditBox ->setHeight(10); doesn't
seem to work.
Thank you,
-DK
--
change size of controls in a layout
by social hub » Thu, 22 Apr 2010 03:46:09 GMT
did u call requestLayout()
or invalidate()
if that doesnt work try below
textView.getLayoutParams().height = x;
requestLayout();
should work
>
Sponsored Links
change size of controls in a layout
by karteek » Thu, 22 Apr 2010 12:22:01 GMT
If you declared EditText in xml file you can change by
<EditText android:layout_width="50px"
android:layout_height="50px">
</EditText>
where you can use any nuber instead of 50
>
change size of controls in a layout
by ~ TreKing » Thu, 22 Apr 2010 21:58:49 GMT
You should use "dp" to stay consistent across devices with different
resolutions, unless this is definitely what you want.
-------------------------------------------------------------------------------------------------
TreKing - Chicago transit tracking app for Android-powered devices
http://sites.google.com/site/rezmobileapps/treking
--
Other Threads
1. Android bitmap allocation weirdness
I'm having some trouble understanding why this code
public class BitmapAllocTest extends Activity {
/** Called when the activity is first created. */
@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
byte[] b = new byte[20 * 1000 * 1000];
b = null;
Bitmap.createBitmap(2500, 2000, Bitmap.Config.ARGB_8888);
}
}
throws an OutOfMemory exception on a device with a 24mb heap limit. If
I comment out either of the allocations it runs fine. I was under the
impression that the java vm would try to garbage collect before
throwing OutOfMemory exceptions.
I suspect it having to do with android allocating the bitmaps on the
native heap.
PS. This is a clone from my stackoverflow question
http://stackoverflow.com/questions/3546635/android-bitmap-allocation-weirdness
which hasn't gotten a satisfactory answer yet.
--
2. Sharing code between apps as in Eclipse
I have ten, possibly more, apps I'm developing that all share logic.
50-75% of the logic is the same - perfect for some time of library or
code sharing. However, after reading the posts here and trying to
share code in Eclipse, I'm not sure that's going to work. I tried
going to project -> properties -> build path -> link source and adding
the src and gen folders of the project with the shared code and then
importing the classes I need. That seems to work in the IDE, but gives
an error during runtime: class not found. This seems to be a common
error for people attempting this.
I am slowly deciding that shared code is not the best approach in this
scenario. Android doesn't seem to work well with this type of code
sharing. For one thing resources are not packed in libraries, but
references (R.whatever) must exist so as not to create errors. This
can be designed around, but the effort and headache is probably worse
than simply creating multiple copies.
What are you thoughts on the topic? My experience seems typical,
based on what I've read. Is it? Have you experienced success or
failure with sharing code and/or custom libraries? Am I off-base in
thinking that multiple code copies will be smoother sailing than
fighting the shared code approach?
--
3. copybit format conversion issue, for help
4. Unsuccessful install of successful built apk
5. Porting Information
6. JDOM in Android 2.1 or earlier
7. getPreviewSize() bad result on Froyo emulator