wrap around with textview in a tablelayout broken

by Fabian Sturm » Tue, 22 Sep 2009 04:21:03 GMT

Sponsored Links

I have a very simple layout, a table with a single row containing two
textviews. The first textview has a short text and the second a long
text which needs to be wrapped around.

Unfortunately the wrap around does not work. In the first line of the
wrapped text the last word is missing a letter and in the second line
another letter is missing and even the word "3" is missing. 
So I get the text:

"Ein ganz langer Text der umgebrochen werde
 muss, der so lange ist, dass er auf mindesten
 zeilen verteilt werden muss"

instead of this text:

"Ein ganz langer Text der umgebrochen 
 werden muss, der so lange ist, dass 
 er auf mindestens 3 zeilen verteilt 
 werden muss"

Any ideas what I need to activate for the correct wrap around?
I tried many layout parameters but none helped.

I know I could get the same layout easier, but this is just a broken
down example. I want to use a table with maybe 5 rows and 2 columns
later on.

Thanks a lot, Fabian

<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android=" http://schemas.android.com/apk/res/android" ;
                android:text="Ein ganz langer Text der umgebrochen
werden muss, der so lange ist, dass er auf mindestens 3 zeilen verteilt
werden muss"


Other Threads

1. Kernel Panic - booting


Our embedded platform has pxa255. We downloaded linux_2_6_31_1,
compiled with EABI (downloaded the toolchain from Codesourcery),
modified the kernel to add our hardware based support. We also
compiled the user space applications with latest tool chain and able
to boot the system perfectly.

I downloaded the Android SDK, extracted the root file system.

As our system has 128MB of sdram, we extracted the contents of system
and userdata image and put it in root fs system folder. Also I
commented out mount yaffs2 section in init.rc file.

I copied the /dev contents to android root fs and etc -> /system/etc.

While booting it shows,

kernel panic - not syncing: attempted to kill init.

can anyone help me out in to fix this issue.


unsubscribe: android-porting+unsubscr...@googlegroups.com

2. Web App Support

The Android platform does a good job of supporting applications. There
are many tools for application developers to get their apps on
people's phones, make the applications easy to find, and manage the
running applications. The market is a great way for users to find new
applications; users have the application dock where they can launch
the application; the platform will allow users to run multiple apps at
the same time with the user being able to switch between the apps.

Why doesn't Android have the same support for web apps?

Google has many times stated that they prefer people to develop web
applications. Google spends a lot of their development time on mobile
web apps. So why does the Android support applications better than web
applications. Why as a developer can't I put my web app into the
market? Why can't the users launch web apps "downloaded" from the
market in their application dock? The app could open the browser and
the user would be directed to the entry of the application.

With more support for web apps on a Google platform, the gap between
an Android application and a web app would be narrowed a great deal.
It seems that many developers are creating a shell app that hosts
their mobile site. This works, but if there needs to be changes in the
shell app (i.e. new authentication) then they have to have users
update the shell app instead of doing all development on the web side.
It seems with all of Google's push for web apps, they could have
better support on Android to support web apps.

Google could also add better support by having the Google search
engine index mobile web apps. Web app developers could add a meta tag
indicating the support for mobile web. Google could then index this
content and provide a search for mobile apps within the regular Google
search. This would allow web developers to write an app on the web and
not have to submit their app to each different phone marketplace.
Users would be able to search and find web apps that were not easy to
find before. It could be the market place for all phones.


3. WiFi Regulatory Domain Channels

4. Is forcing users to enter their order number too much to ask?

5. Modem Link

6. A2DP / Headset Sink (Client)?

7. Best way for run emulator on headless machnie.