Author Topic: Linux Whiteboard - New SVN version - Right click waiting time now configurable  (Read 19236 times)

Offline fnf

  • *
  • Posts: 70
  • Karma: +2/-0
    • View Profile
The latest SVN version supports user-configuration values. At the time of writing, only right-click time is available.

Suggestions on what should be made configurable are welcome. Configurations saving will be functional in a short while.

Download Linux Whiteboard from Linux Whiteboard homepage


Offline ischnura

  • *
  • Posts: 13
  • Karma: +0/-0
    • View Profile
@fnf
The Gutsy Version was not working perfectly, I had some problems connecting to the Wiimote. After many tries I managed to make it work.

Once the Wiimote is connected the Calibration and the Resolution work very well.

Now I just did a fresh Hardy installation to test the Hardy whiteboard package. The package also installed another three extra packages.

After the installation as expected the Wii Whiteboard icon in the Application menu.

The Connection via Bluetooth worked perfectly.

The problem for me happend during the calibration:
 * Not Full Screen
 * Could not see my IR pen
 * It randomly Calibrated itself, (Invisible IR pen)
 * The CPU went crazy (100%)

FYI, the output on the Terminal was:
Code: [Select]
~$ whiteboard
Put Wiimote in discoverable mode now (press 1+2)...
Connected!!!
Put Wiimote in discoverable mode now (press 1+2)...
No wiimotes found
Unable to connect to wiimote

(whiteboard:20186): gtkmm-WARNING **: Gtk::Main::init() called twice
Mesg pipe overflow
Mesg pipe overflow

Let me know if I can do something else to test the Whiteboard.



Offline fnf

  • *
  • Posts: 70
  • Karma: +2/-0
    • View Profile
Thanks for your testing. I think all the problems that you're having are just a manifestation of the bug that I've been struggling for a few days.

Please check out the latest SVN version. The deb package in the repo doesn't incorporate fixes for the fullscreen issue and that bug above (not that it have been fixed, but I'm waiting for more testing whether the workaround is acceptable or not).

It is a compromise :s to make it completely crash-proof, Whiteboard must not output any text when connecting, which makes it a little bit uninformative.

Download Linux Whiteboard from Linux Whiteboard homepage


Offline fnf

  • *
  • Posts: 70
  • Karma: +2/-0
    • View Profile
I uploaded a DEB of the last SVN on the repo.

Download Linux Whiteboard from Linux Whiteboard homepage


Offline ischnura

  • *
  • Posts: 13
  • Karma: +0/-0
    • View Profile
Just downloaded the latest DEB.

Now the Calibration is Full Screen.

Still get the CPU to peak to 100%.

And could not Calibrate... (It was working fine with the last version in Gutsy)



Offline fnf

  • *
  • Posts: 70
  • Karma: +2/-0
    • View Profile
Just downloaded the latest DEB.

Now the Calibration is Full Screen.

Still get the CPU to peak to 100%.

And could not Calibrate... (It was working fine with the last version in Gutsy)

It ran fine in my machine though, but that doesn't negate the fact that that bug is not to be ignored.
Please try the latest SVN, I disabled the printing of messages when connecting. Less than ideal solution, but if you have suggestions to the GUI, please do.

Download Linux Whiteboard from Linux Whiteboard homepage


Offline fnf

  • *
  • Posts: 70
  • Karma: +2/-0
    • View Profile
I've fixed the bug and uploaded a new DEB to the repo. Please test it to see if the problem persists.

Download Linux Whiteboard from Linux Whiteboard homepage


Offline ischnura

  • *
  • Posts: 13
  • Karma: +0/-0
    • View Profile
Downloaded 0.2.9.1 and still get the same problem:
 * CPU gets to 100% (This slows all the Calibration Process)

When I show the IR Pen to the Wiimote during calibration, I can see the output of the "Wiiremote camera" in the square from the center of the calibration... The output in the center square has a delay of 3 secs to 20 seconds...

After spending three minutes calibrating, the end result was good: I could Activate the whiteboard and use it like before.



Offline fnf

  • *
  • Posts: 70
  • Karma: +2/-0
    • View Profile
I haven't completely updated all the code to the new method, so that bug may well still be 'functional'. Whiteboard is going through major refactoring, I will let you know when the new version comes out, perhaps before the end of today.

That said, can you run whiteboard in a terminal to check if it outputs any error messages?. Most of them (if any) should come from GTK+ and friends.

By the way, I suppose the CPU usage only went up when you tried to connect?.

Download Linux Whiteboard from Linux Whiteboard homepage


Offline fnf

  • *
  • Posts: 70
  • Karma: +2/-0
    • View Profile
All code related to this bug has been modified, please test if it runs properly on your system. Mean while, I'm gonna work on configuration saving feature.

Download Linux Whiteboard from Linux Whiteboard homepage


Offline ischnura

  • *
  • Posts: 13
  • Karma: +0/-0
    • View Profile
Testing whiteboard_0.2.9.2-0ubuntu1_i386.deb

There is no problem connecting to the Wiimote.

Same CPU issue: The CPU usage went up when trying to Calibrate.

Here you have the output from the command line:
Code: [Select]
~$ whiteboard
Put Wiimote in discoverable mode now (press 1+2)...
Connected!!!
Put Wiimote in discoverable mode now (press 1+2)...
No wiimotes found
Unable to connect to wiimote

(whiteboard:7791): gtkmm-WARNING **: Gtk::Main::init() called twice
Mesg pipe overflow
Mesg pipe overflow
Mesg pipe overflow
Mesg pipe overflow
Mesg pipe overflow
Calculating coefficients... Done!

After calibrated it worked very well.

Maybe you can produce a more verbose output in the command line so that you can track easily the bugs.



Offline fnf

  • *
  • Posts: 70
  • Karma: +2/-0
    • View Profile
I will add more debug outputs to the terminal after finishing the configuration feature, at least you can reload the configs after having calibrated once, partially alleviate the issue.

The thing is, it is not reproducible on my machine and a few other testers. These 'mesg pipe overflow' messages are from libcwiid itself (these were probably caused by the peaked CPU usage), and I believe I have done everything to fix the multi-threading issue, according to the documentation anyway.

Be patient though, the new feature will hopefully be completed before the end of tomorrow.

Download Linux Whiteboard from Linux Whiteboard homepage


Offline fnf

  • *
  • Posts: 70
  • Karma: +2/-0
    • View Profile
Oh, you said the CPU reached a peak when calibrating. Perhaps the problem lies in your video driver?.

The calibration window is drawn by Cairo: A 2D vector drawing library, but capable of using hardware accelerations. Chances are you are using an ATI card, some low-power Intel cards (although Cairo should be pretty fast) or most probably running without any 3D driver at all. How is the performance in, say, Inkscape or Scribus?. These apps use libcairo extensively.

Download Linux Whiteboard from Linux Whiteboard homepage


Offline ischnura

  • *
  • Posts: 13
  • Karma: +0/-0
    • View Profile
You are right!

The problem must be in the configuration of my 3D acceleration... I still need to tweak the Hardy installation.

I will keep you posted.



Offline ischnura

  • *
  • Posts: 13
  • Karma: +0/-0
    • View Profile
I chose the correct driver for my graphics card (i810) and now everything works great.

Sorry for the misleading information.