Anyone run into this?
Activity creates a WebView and sets cache mode = LOAD_NO_CACHE, then calls
WebView.postUrl() with a URL and some POST data.
The resulting webpage has a hyperlink, which the user tap to access a
second page.
He then taps the device back button, which I intercept and turn i
Disregard. Problem was on my end.
On Monday, May 19, 2014 3:44:59 PM UTC-5, Jay Howard wrote:
>
> Am I imagining things, or was support for the "manifestpackage" property
> AaptExecTask removed in 22.6.3? This used to map to the command line
> option "--rename-ma
Am I imagining things, or was support for the "manifestpackage" property
AaptExecTask removed in 22.6.3? This used to map to the command line
option "--rename-manifest-package".
If I'm not imagining things, any reason it was removed? I found it very
helpful.
Here's the functionality I'm refe
The layout of ListView items seems to have changed in SDK 18. I've created
an example project that highlights the different behavior when
targetSdkVersio = 17 vs. 18:
https://drive.google.com/file/d/0B6DvDY2BvxUTZHUxTHkzNUZvVDg
Additionally I've started a thread on StackOverflow (with screen s
27; version and is an 'unlocked' device,
> not rooted & not from a carrier, it came out of Hong Kong, I am using it in
> Australia.
>
> Perhaps the issue is specific to some subset of these devices?
>
> Regards
> ,
> On Wednesday, August 7, 2013 11:48:28 PM UT
ld make use of an
> action bar and move the most important and relevant menu options there.
>
>
> On Tuesday, August 6, 2013 11:01:17 AM UTC-5, Jay Howard wrote:
>>
>> I'm seeing the following behavior (on a Samsung S4, but potentially also
>> on other Samsung devices
xml:
http://schemas.android.com/apk/res/android"; >
On Wednesday, August 7, 2013 2:40:37 PM UTC-5, Nobu Games wrote:
>
> Could you post your Activity code?
>
> On Tuesday, August 6, 2013 11:01:17 AM UTC-5, Jay Howard wrote:
>>
>> I'm seeing the following behavio
commended practice, is to try your
> inflator code within onPrepareOptionsMenu(), remembering to call
> menu.clear() before the inflator and see if that works any better.
>
> See for details
> http://developer.android.com/reference/android/app/Activity.html#onPrepareOptionsMenu(a
within onPrepareOptionsMenu(), remembering to call
> menu.clear() before the inflator and see if that works any better.
>
> See for details
> http://developer.android.com/reference/android/app/Activity.html#onPrepareOptionsMenu(android.view.Menu)
>
> Good luck.
>
> On Wednesday,
This may be a complete red herring, but I've noticed that certain Motorola
phones don't behave well unless you use the Motorola-branded USB cable that
shipped with the phone. For whatever reason, those particular phones don't
work well with generic cables.
On Tuesday, August 6, 2013 12:59:21 P
I'm seeing the following behavior (on a Samsung S4, but potentially also on
other Samsung devices) in an app that uses a "legacy" options menu:
1. User taps hardware menu button to bring up options menu. There are more
than six items in the menu.
2. User taps the bottom-right "more" button to a
ficient to
guarantee that doSomethingWithHandlerSync(), handleMessage() and
onReceive() will never execute concurrently.
On Tue, Oct 30, 2012 at 10:09 AM, Jay Howard wrote:
> Thanks so much for the response! If you'll indulge me with a few more
> questions...
>
> So I instantiate
> if (conditionTwo)
> handler.**sendEmptyMessageDelayed(MSG_**TWO, timeoutTwo);
> }
> });
>
> Since both the 'removeMessages' and 'sendEmptyMessageDelayed' are called
> on 'handler' the Runnable needs to finish first before any other m
I'm using a timer to manage timeout events, and would like to ensure that a
particular method runs atomically without the handler issuing messages
while the method is executing. Its basic form is:
handler.removeMessages(MSG_ONE);
handler.removeMessages(MSG_TWO);
...
if (conditionOne)
handler
t; please?
>
> Bitmap.writeToParcel
> http://developer.android.com/reference/android/graphics/Bitmap.html#writeToParcel(android.os.Parcel,
>
> int)
>
> Has no change notes against it and says it writes the pixels (from API
> level 1)
>
> On Wednesday, September 26, 2012 4:22:04 PM
With the changes to how bitmap data is stored that came in with Honeycomb
affect the efficiency of parceling bitmap objects?
I'm assuming the actual bitmap data wasn't ever parceled pre-Honeycomb. Is
that accurate? If so, then my question is basically whether this behavior
(not parceling the
I'm in a similar situation, Alex. Did you ever find a solution to your
problem?
I found third-party libraries that support creating AVI and MOV (Quicktime)
files from a series of JPEG images, but the compression isn't nearly as
good as H.264.
On Saturday, June 30, 2012 5:26:41 PM UTC-5, Alex
Guessing you need to have it in the lib directory in your Android project.
Adding it as an external library in eclipse adds it to your eclipse
classpath, so the build errors disappear in eclipse, but the android build
process only packages the jars it finds in your project's lib dir.
On Friday
For simplicity's sake I like Serializable because it frees you from the
work of implementing Parcelable. It's possible Parcleable could perform
better, but if you're worried about performance when passing objects
between activities then you should probably be storing them in a global
location
My app uses the Camera to take high-res images, which are then jpeg
compressed and sent over the network. Initially I relied on the jpeg
quality setting in the Camera API:
final Camera.Parameters params = mCamera.getParameters();
params.setPictureFormat(PixelFormat.JPEG);
I'll assume you have a Vector.
1. Make sure Foo implements Serializable or Parcelable.
2. Call toArray(Foo[]) on the Vector to get a Foo[].
3. Set the Foo[] as an extra using Intent.putExtra(Serializable) or
intent.putExtra(Parcelable[]).
4. In the resulting activity, get the array back using
In
21 matches
Mail list logo
