pb sdk 0.9.77 ?

[f.maillet]

Do you mean that the litle above code with a simple frame and a JLabel following user gaze is ok with both libraries ?
May I have a "fresh" copy of the library ? could it be that my jar file be corrupted in a way that allow compilation, but not execution ?

[Anders]

Do you mean that the litle above code with a simple frame and a JLabel following user gaze is ok with both libraries ?

No. I mean that I have no trouble establishing connection when following the standard rules of controlling a Java program life-cycle. See the code of the project I posted.

could it be that my jar file be corrupted in a way that allow compilation, but not execution ?

Hard to say without knowing where you got the library from in the first place.

May I have a "fresh" copy of the library ?

As mentioned in my previous post, I have verified that the latest release of the github repo works as intended. Use that.

[f.maillet]

Hello Anders,
I get the 0.9.77 jar file on gitHub.
I have tried the HeatMap gitHub program, which is quite a good piece of code and have the same problem : works fine with 0.9.66 but not with 0.9.77. Checking with his author, Aksel, he told me that he had previously the same problem with 0.9.77 sdk that lead him to switch back to 0.9.66. (we're together on the same windows 10 platform, netbeans 8.2 and jdk 1.8).

We checked together the code below (which is good standard threaded as you asked) and have the same problem : the 0.9.77 sdk doesn't succeed in activating the GazeManager while the 0.9.66 works nicely.

Code: Select all

package testeyetribe;

import com.theeyetribe.clientsdk.GazeManager;
import com.theeyetribe.clientsdk.IGazeListener;
import com.theeyetribe.clientsdk.data.GazeData;

public class TestMain {
    public static void main(String[] args) {
        final GazeManager gm = GazeManager.getInstance();
        gm.activate();
        gm.addGazeListener(new GazeListener());

        //Endlessly looping thread.
        new Thread(new Runnable() {
            public void run() {
                while (gm.isActivated()) {
                    try {
                        //sleep for 1 second
                        Thread.sleep(1000);
                    } catch (InterruptedException e) {
                        e.printStackTrace();
                    }
                }
            }
        }).start();
    }

    static class GazeListener implements IGazeListener {
        public void onGazeUpdate(GazeData gazeData) {
            System.out.println(gazeData.toString());
        }
    }
}

[Anders]

Code: Select all

//Endlessly looping thread.
        new Thread(new Runnable() {
            public void run() {
                while (gm.isActivated()) {
                    try {
                        //sleep for 1 second
                        Thread.sleep(1000);
                    } catch (InterruptedException e) {
                        e.printStackTrace();
                    }
                }
            }
        }).start();

This code is not 'endless looping'. It only loops if gm.isActivated() is true.

Try running the exact code of the project I created for you and check the console output.

Also, what happens if you export your project to a JAR and run it from the cmd line instead of from NetBeans? Netbeans seems to be the common denominator for several devs who've had issues.

[aksel]

Hi Anders

I am the guy f.maillet mentioned in his previous post.

While working on this project, I too had issues with 0.9.77. I used IntelliJ, but never tested with an exported jar.

Specifically, the GazeManager refused to activate. I am fairly certain there was an error output to the console, but I can't be sure. Any word on this, f.maillet?

Note that both mine and f.maillet's applications use Swing for GUI.
Maybe that has something to do with it? I noticed the demo you offer comes with a JavaFX example.

I sadly do not have access to an eye tracker any longer. I borrowed the one I had from my teacher.
I will get my hands one later this month, when I will start work on a more advanced heatmap application.
I will make sure to retry with 0.9.77, also with exported jars.

And to f.maillet, please try running this project by Anders.

[f.maillet]

Hello Aksel and Anders,
I made the checks you asked both of you.
-) I have the same behaviour in command line jar or from the netbeans ide.
-) the Anders project works fine with 0.9.77 sources

Given this last result, I came back to all our tries and checked with 0.9.77 sources instead of jar file (and gson-2.3.1 + annotations-13.0 jar libraries) : ALL of them run nicely when build like this...
I then checked back again with the 0.9.77 jar file and it fails : this jar file always fails to activate gazemanager. But when the project is build from sources it works.

One strange thing : when checking back with the 0.9.77 jar, I firstly let the gson-2.31 library in the project : and then it worked (?!). I was firstly puzzled, you can imagine, before noticing the fact that I let the gson library in the project. When I remove it, I reproduce the gm activation fail problem...
Not sure it is clear : for all the tests we have proposed so long (mines, Anders gitHub test, Aksel heatmap and threaded test, ...), and so whatever the design of the program may be , I have this constant behaviour :

+) they do work with 0.9.66 jar library alone (and this is true within or outside netbeans ide)
-) they do not work when build with 0.9.77 jar library alone (and this is true within or outside netbeans ide)
+) they do work when build from 0.9.77 sources (of course given gson and annotations libraries too)
+) they do work when build with 0.9.77 jar library AND gson-2.3.1 jar library ! ?

Hope that things get clearer for you. The last point may give you a cue that is far beyond my competencies.

[Anders]

@aksel

I am the guy f.maillet mentioned in his previous post.

While working on this project, I too had issues with 0.9.77. I used IntelliJ, but never tested with an exported jar.

Great project. I strongly encourage you to make this forum aware of you github heatmap project by posting a new thread about it. Many could benefit from it.

Note that both mine and f.maillet's applications use Swing for GUI.
Maybe that has something to do with it? I noticed the demo you offer comes with a JavaFX example.

Hard to say. But since Swing is from the mid 90'es, maybe it's safe to say that it has passed it's expiry date. I strongly encourage anyone doing GUI work to use JavaFX. Especially when all the hard work of setting up the needed Gradle routines is already done for you in the project you mention.

I sadly do not have access to an eye tracker any longer. I borrowed the one I had from my teacher.
I will get my hands one later this month, when I will start work on a more advanced heatmap application.
I will make sure to retry with 0.9.77, also with exported jars.

Looking forward to it. I encourage you to use the package available through Bintray using Gradle instead of local JARs. It is faster and easier to maintain.

[Anders]

@f.maillet

I made the checks you asked both of you.
-) I have the same behaviour in command line jar or from the netbeans ide.
-) the Anders project works fine with 0.9.77 sources

Given this last result, I came back to all our tries and checked with 0.9.77 sources instead of jar file (and gson-2.3.1 + annotations-13.0 jar libraries) : ALL of them run nicely when build like this...
I then checked back again with the 0.9.77 jar file and it fails : this jar file always fails to activate gazemanager. But when the project is build from sources it works.

The project I posted has a dependency to a JCenter package, eyetribe-java. It does _not_ contain the sourcecode. This is no different from using the Jar downloaded from the EyeTribe Java SDK github page.

One strange thing : when checking back with the 0.9.77 jar, I firstly let the gson-2.31 library in the project : and then it worked (?!). I was firstly puzzled, you can imagine, before noticing the fact that I let the gson library in the project. When I remove it, I reproduce the gm activation fail problem...

This sounds very strange and indicates that something is wrong with your JAR file or Netbeans project setup. Could you please check that the JAR file you are using has the exact same size as the one from the EyeTribe Java SDK release page? Could you also please check if your Netbeans project uses obfuscation (e.g. proguard) by default and turn that off if it is the case.

Also, could you 'open' the JAR file you use with a Zip program (7zip or winzip) and check if the folder structure 'com\google\gson\' is contained within?

[f.maillet]

You're right Anders, the 0.9.77 jar file I have is smaller than the one you linked, and the gson structure is missing.
It seems I have found an incomplete 0.9.77 jar file but I just can't help you and tell where I initially got it. Aksel may be more precise as we probably faced the same problem.

If I replace the jar file you linked in your last post, all is working perfectly.
Seems we have finally found the origin of the problem. My programs design wasn't so bad as they run nicely by now but you're right, I have to check how to link through Bintray. I will cope with Gradle for my Attention Aware System university project. I'm on it by now.

[Anders]

I am glad to hear we've solved your problem.

On the other hand I'm sad to learn that corrupt Jars are being redistributed from somewhere and that this was the cause of the problems you've been facing.

Other developers reading this should make sure to ONLY use releases from the official repository. Also, I STRONGLY advice any developers wanting to use the EyeTribe Java SDK to use Gradle and JCenter to handle the library dependency. That is the modern and build system friendly approach to handling dependency complexities in Java projects.