Mouse events are blocked - A way to escape from this state

[athanassios]

Hi I have been experimenting with the latest version of Wandora, and I will try to describe how to reproduce the bug I am referring to in the subject of this post. This type of bug, has also happened in previous versions of Wandora during other kind of actions, but here I am describing a specific action related to the new features of the program.

O.K start the program then create a new instance topic of Wandora class e.g. 'This is a test',
Double click on this new topic, by default the traditional topic panel displays the topic
Right click on the Variant names and select "Add variant name"

The window 'Add variant name' appears, then enter a name and click Add scope topic. You may try with the already defined 'Scope Display' topic and finally press OK and that is exactly where the bug appears.

Let me be more specific, at this program state, the mouse pointer can change from an arrow style to the hand style or bracket style when you move it on top of various widgets but you cannot select anything, you cannot do any action, when you press the mouse buttons. You cannot select menus, you cannot type on the text boxes, you cannot do anything with the mouse at this program state. What about the console messages ? There are no console messages displaying anything !!!

But there is a way to escape that condition by using the keyboard and a shortcut. You press for example Ctrl+L and the "Open Wandora project" pop-up window appears. You click cancel and you continue normally as before, the mouse events are now fully working as before. The console displays the message setRootTopic, reuse....

Important : I noticed that the traditional topic panel has been set by me to view all scopes (Righ click Variant names - View - View All scopes). If you set that back to View - View schema scopes the bug can be reproduced as above by selecting "Add variant name". You can also reproduce the bug by selecting Menu View-View topic as - Variant name....

O.K hope that bug is documented sufficiently, if not let me know....

[akivela]

Hi Athanassios

Thank you very much for the bug report! Your description is very detailed and informative but somehow I am not able to reproduce the error condition. Wandora stays responsive even if I click OK button in the Add variant name window. To hunt the cause, could you please tell

* Does the block-state appear always? I am after a question, does the block-state need some preceding actions or does the block-state appear in a fresh i.e. just started application. Does the block-state appear even if you have not opened any topic map or project in Wandora (addition to default Base topic map)?
* What Java version and what operating system are you using?

Kind Regards,
Aki / Wandora Team

[athanassios]

The block state need some preceding actions, such as those I described above to reproduce the bug, but I think I have experienced the same bug before under different conditions alhtough I have not recorded them.

Yes, the block-state appear even if you have not opened any topic map or project in Wandora (addition to default Base topic map) the way I am describing it in the post above.

sudo update-alternatives --config java
/usr/lib/jvm/java-7-openjdk-amd64/jre/bin/java

sudo lsb_release -a
Ubuntu 11.10 oneiric

Hope that helps

Athanassios

[akivela]

Hi Athanassios

Looks like I am not able to reproduce the error condition in a similar environment (Linux, Ubuntu 11.10, java-7-openjdk-amd64). This suggests that your system is still somehow different. You might try to update your Java version to newest, or try Wandora on a different environment. I wonder, if installing Oracle's Java version might help?

Also, we would like to know, if other Wandora users have experienced a similar problem. Please, do report if Athanassio's description above sounds familiar.

Kind Regards,
Aki / Wandora Team

[athanassios]

Hi Aki,
I confirm that it is a Java version problem, I used

sudo update-alternatives --config java
and changed my configuration to

/usr/lib/jvm/java-6-openjdk/jre/bin/java

The bug has disappeared......

[akivela]

Hi Athanassios

Great news! And thank you for bringing the issue to public.

I have to look at the OpenJDK Java version 7 very closely and hope the problem disappears in future releases.

Kind Regards,
Aki / Wandora Team