Yes, I assume so. My buffer.compact() fix makes it useful until
the fix is pushed out I guess. Do you think it's worth posting it to
the bug report?
Thanks,
Anton
On Mar 30, 4:48 pm, fadden wrote:
> On Mar 30, 1:51 pm, Anton wrote:
>
> > I also ran into this problem. Aft
On Mar 30, 1:51 pm, Anton wrote:
> I also ran into this problem. After looking through the source to
> the NIO buffers I noticed that when you use a wrapped direct buffer
> the wrapping code doesn't clear the underlying buffers position when
> you call buffer.clear().
Is this the same as ht
I also ran into this problem. After looking through the source to
the NIO buffers I noticed that when you use a wrapped direct buffer
the wrapping code doesn't clear the underlying buffers position when
you call buffer.clear(). I found a way around this that doesn't
require the for loop. If
Good to know. At least it's good to know that i was not going crazy :-
D
I used the for-loop solution to get around this issue.
On Mar 30, 7:04 am, Daniel Johansson wrote:
> I'm experiencing the same behavior, and I'm pretty sure it's a bug.
>
> I have been testing this thoroughly and it simply
On Mar 30, 4:04 am, Daniel Johansson wrote:
> I'm experiencing the same behavior, and I'm pretty sure it's a bug.
A handful of bugs in the nio buffer implementation have been found and
fixed. If you have some code that demonstrates the problem, please
file a bug on b.android.com, and we'll make
I'm experiencing the same behavior, and I'm pretty sure it's a bug.
I have been testing this thoroughly and it simply does not work to put
an array och another IntBuffer into a "direct" IntBuffer.
intBuffer.clear();
intBuffer.put(otherIntBuffer);
This does not work if "intBuffer" is a direct In
6 matches
Mail list logo
