Jump to content

  • Log In with Google      Sign In   
  • Create Account


Member Since 21 Apr 2011
Offline Last Active Today, 05:18 PM

Posts I've Made

In Topic: LibGDX Multi-touch finger index tracking

11 July 2016 - 07:17 AM

I am grateful for your lengthy response.


I will try to look into in a more detailed way later on.

By doing some quick checks, i noticed that methods like


are not available from LibGDX (or at least i did not manage to find).

On the other hand, LibGDX is a crossplatform tool, so it makes sense that native android events and methods can not be accessed.


For now i will trust, that events like


public boolean touchDown(int screenX, int screenY, int pointer, int button)  { return false; }
public boolean touchUp(int screenX, int screenY, int pointer, int button) { return false; }
Operate with PointerID and not Index.
Thank you very much! I will keep this thread bookmarked as a reference to this issue!

In Topic: Application event logging (offline mode)

06 January 2016 - 11:03 AM

Maybe you have encountered any API's or services which cover that?

From the first glance, GA was excellent choice, because its free and API is there.


Now i have to write my own solution plus buy a web hosting, and build a php webie to store info in database.

In Topic: Application event logging (offline mode)

05 January 2016 - 12:02 PM

Frankly, i fail to see the "design" in current GA for Android.

It does its job well, the only issue is that it doesn't store the data for long period. And we are talking just two or three days here.

Most of data i get is so so, but there is one specific case, where person told me he got a highscore, and i simply didn't get that report. Turns out, he didn't have wifi on for 6 days.

6 days of data is lost.

At this point, I plan to use both GA and custom IntentService to dump the data. Will find out what's better.

In Topic: Application event logging (offline mode)

03 January 2016 - 03:50 AM

Found an interesting and unsettling info:


Data must be dispatched and received by 4 a.m. of the following day, in the local timezone of each profile. Any data received later than that will not appear in reports. For example, if a hit is queued locally at 11:59pm, it must be dispatched within 4 hours, by 3:59am, to appear in reports. On the other hand, a hit queued at 12:00am must be dispatched within 28 hours, i.e. 3:59am of the following day, in order to appear in reports.


So the best solution is pretty much to create IntentService and push events from UI Thread, and dump info into server once WiFi or Mobile Data is enabled. AlarmManager can be used to "awaken" service.

In Topic: Managing different screen resolutions and Mipmaps

29 September 2015 - 11:45 AM

Thanks for clearing things up.