Re: Retrieving Mouse Clicks

[guilhelm savin <guilhelm.savin AT gmail.com>]

I think it's a really normal behavior if you want to turn your laptop into a heater.

But well .... we agree : this is not the aim of GraphStream.

I think there is a real problem in this case. We have to discuss it with other dev but I made a draft hack of ViewerPipe with a blocking pump method.

You can find it here : http://pastebin.com/a6kcA6xQ

To use it, just change this line :

ViewerPipe fromViewer = viewer.newViewerPipe();

into : 

ViewerPipe fromViewer = new BlockingViewerPipe(viewer);

Your CPU load should fall to a more acceptable rate.

Thanks for reporting this behavior.

Hope this helps.

Regards.

Guilhelm

2013/5/28 Sebastian Bock <sebastian.bock AT bluewin.ch>

Hi there

Just a question to the example from the graphstream site. In the following example a while(true)-loop is used and AFAIK the pump() method is non blocking. This results in a loop which causes a 100% CPU usage.

Is this a normal behavior? Are there any other ways to retrieve mouse clicks without 100% CPU usage?

Thank you in advance

Sebastian

Example:

public class Clicks implements ViewerListener {

    protected boolean loop = true;

 

    public static void main(String args[]) {

        new Clicks();

    }

    public Clicks() {

        // We do as usual to display a graph. This

        // connect the graph outputs to the viewer.

        // The viewer is a sink of the graph.

        Graph graph = new SingleGraph("Clicks");

        Viewer viewer = graph.display();

 

        // The default action when closing the view is to quit

        // the program.

        viewer.setCloseFramePolicy(Viewer.CloseFramePolicy.HIDE_ONLY);

 

        // We connect back the viewer to the graph,

        // the graph becomes a sink for the viewer.

        // We also install us as a viewer listener to

        // intercept the graphic events.

        ViewerPipe fromViewer = viewer.newViewerPipe();

        fromViewer.addViewerListener(this);

        fromViewer.addSink(graph);

 

        // Then we need a loop to wait for events.

        // In this loop we will need to call the

        // pump() method to copy back events that have

        // already occurred in the viewer thread inside

        // our thread.

 

        while(loop) {

            fromViewer.pump();

        }

    }

 

    public void viewClosed(String id) {

        loop = false;

    }

 

    public void buttonPushed(String id) {

        System.out.println("Button pushed on node "+id);

    }

 

    public void buttonReleased(String id) {

        System.out.println("Button released on node "+id);

    }

}

--
Guilhelm Savin
PhD Student of Computer Science

LITIS, University of Le Havre
\/\/\/\/\/\/

http://gsavin.lewub.org

http://d3-project.org
http://iscn.univ-lehavre.fr
http://graphstream-project.org
/\/\/\/\/\/\

Attachment: BlockingViewerPipe.java
Description: Binary data