[SOLVED]Keyboard Input Lag

[duce]

Thanks for the help, everyone! I managed to find the problem. I needed to use createCompatibleImage() to convert my images to the required format.

Here is my new Texture class:
http://pastebin.com/9S8QMXby

[sproingie]

@theagentd

That’s generally slower since this creates an Iterator instance every frame. Since when did accessing array elements become slow?

This is like telling someone driving a fully loaded 18-wheeler to take the bumper stickers off to shed weight. The point is to get familiar with programming idioms that are actually clear.

[theagentd]

@sproingie

@theagentd

That’s generally slower since this creates an Iterator instance every frame. Since when did accessing array elements become slow?

This is like telling someone driving a fully loaded 18-wheeler to take the bumper stickers off to shed weight. The point is to get familiar with programming idioms that are actually clear.

That depends on how much you use it. Tell someone that it’s okay to do use those for-loops and he/she is going to use them for nested for-loops. I’ve saved milliseconds by changing it to a normal for-loop, and I don’t have many of those you know.

[pitbuller]

@theagentd

@sproingie

@theagentd

That’s generally slower since this creates an Iterator instance every frame. Since when did accessing array elements become slow?

This is like telling someone driving a fully loaded 18-wheeler to take the bumper stickers off to shed weight. The point is to get familiar with programming idioms that are actually clear.

That depends on how much you use it. Tell someone that it’s okay to do use those for-loops and he/she is going to use them for nested for-loops. I’ve saved milliseconds by changing it to a normal for-loop, and I don’t have many of those you know.

Just for additional notes that on android for:each loop is faster that indexed loop and do not produce iterator but only for normal array. For collections that cannot be indexed in constant time they are faster and create garbage but ArrayList they are slower. I used lot of time with timers and byte/dex code to get this conclusion.

Ps. Don’t say its does not matter much. I know it allready.

[sproingie]

“Optimizing” the iterator out of a brute-force algorithm. Bikeshedding at its finest.

[theagentd]

@sproingie

“Optimizing” the iterator out of a brute-force algorithm. Bikeshedding at its finest.

-_-

Let’s just say I’m not using iterators in my particle engine that runs 1 million particles, or in the ray-casting method I have to check visibility between two points on a tile-map.