On Oct 21, 10:24 pm, Streets Of Boston flyingdutc...@gmail.com
wrote:
That's why i put 'official' in quotes :-)
One should not manipulate windows/views in any other thread than the
main UI-thread (e.g. textView.setText(...) or imageView.setImageBitmap
(...), hiding/showing views, etc.). If
Yes you definitely can not inflate views from the thread they won't run in.
The reason is that views may create a handler, and when the handler is
created it is bound to the thread that is creating it. So if you try to
attach that view hierarchy to a window being run in another thread, all hell
I still would try to inflate your view inside your main gui-thread and
not in a seperate background thread.
The fact that it works on other phones does not guarantee it works on
all phones, if inflating views on non-gui threads is 'officially' not
supported.
Who knows, it may fix it (if you
--
Jayesh
On Wed, Oct 21, 2009 at 7:39 PM, Streets Of Boston
flyingdutc...@gmail.comwrote:
I still would try to inflate your view inside your main gui-thread and
not in a seperate background thread.
The fact that it works on other phones does not guarantee it works on
all phones, if
That's why i put 'official' in quotes :-)
One should not manipulate windows/views in any other thread than the
main UI-thread (e.g. textView.setText(...) or imageView.setImageBitmap
(...), hiding/showing views, etc.). If you do this in a background
thread, then you may get exceptions or other
Thanks Shane and Amir for confirming the doubts.
It's frustrating that all I can say to users is to wait until Sprint/HTC
issues firmware update, then hopefully the problem will be fixed. The users
are willing to test if I have any fix, but I can't find root cause even
after looking inside the
I saw somwhere else that one developer also has problems only with HTC
Hero (Sprint) ...
On Oct 18, 9:48 am, Shane shanemenchi...@gmail.com wrote:
We are having problems only with HTC Hero phones as well. Our issue
is different that yours but it is very disappointing to see not all
phones
We are having problems only with HTC Hero phones as well. Our issue
is different that yours but it is very disappointing to see not all
phones handle the SDK the same.
http://groups.google.com/group/android-developers/browse_thread/thread/8fc880b7540a4baf
I suspect this is just going to get
I might be mistaken,
But this part of the stack-trace worries me a bit:
android.view.LayoutInflater.inflate(LayoutInflater.java:276)
com.altcanvas.readerscope.ItemDetails.init(ItemDetails.java:
145)
com.altcanvas.readerscope.ItemDetails.getInstance(ItemDetails.java:
566)
--
Jayesh
On Mon, Oct 12, 2009 at 7:49 PM, Streets Of Boston
flyingdutc...@gmail.comwrote:
I might be mistaken,
But this part of the stack-trace worries me a bit:
android.view.LayoutInflater.inflate(LayoutInflater.java:276)
I tried to look into the android framework code
(linkhttp://www.google.com/codesearch/p?hl=ensa=Ncd=1ct=rc#uX1GffpyOZk/core/java/android/view/LayoutInflater.javaq=lang:java
android.view.InflateException Error inflating class
java.lang.reflect.Constructorl=458). The topmost frame refers to a
Jayesh Salvi wrote:
Hi,
In past couple of days, users of my app have sent crash reports
indicating errors in layout inflation.
android.view.InflateException: Binary XML file line #27: Error
inflating class java.lang.reflect.Constructor
After some investigation I found out that all
Hi,
The stack trace you showed is not useful. This is the top of the
exception chain, which means this exception was caused by something
else. Please show the application specific stack frames you removed.
On Sun, Oct 11, 2009 at 12:34 PM, Jayesh Salvi jayeshsa...@gmail.com wrote:
Hi,
In past
--
Jayesh
On Mon, Oct 12, 2009 at 1:10 AM, Mark Murphy mmur...@commonsware.comwrote:
Jayesh Salvi wrote:
Hi,
In past couple of days, users of my app have sent crash reports
indicating errors in layout inflation.
android.view.InflateException: Binary XML file line #27: Error
--
Jayesh
On Mon, Oct 12, 2009 at 1:11 AM, Romain Guy romain...@google.com wrote:
Hi,
The stack trace you showed is not useful. This is the top of the
exception chain, which means this exception was caused by something
else. Please show the application specific stack frames you removed.
15 matches
Mail list logo
