search

hoangduit / openmeetings

Automatically exported from code.google.com/p/openmeetings
0 stars 0 forks source link

Room windows not clear when exit the conf. room #707

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
When exited the conf. room, all windows were not cleared.
So I had both a list of rooms and a room inside on my srceen. (See the 
screenshot).
Moreover, windows from the room inside were active.

I had no log messages from server concerning that.

Which version of OpenMeetings are you running?
0.8 RC2

Original issue reported on code.google.com by e.rovin...@gmail.com on 20 Apr 2009 at 7:27

Attachments:

GoogleCodeExporter commented 9 years ago 
I've carefully studied the problem - and found the possible source of the 
problem. 
The most easy way to reproduce it was to enter the conference, leave it back to 
the 
"all meetings" page, then back again etc. etc. After 7-8 times the pages were 
starting to switch much slower and cases like this would start to appear, easy 
to 
reproduce on 0.8rc2. After taking a look I have noticed that the "all meetings" 
page 
is displayed before it is fully functional, and the reason is this piece of 
code in 
allmeetings.lzx:

    <handler name="oninit">
        canvas.thishib.roomtype = "public";
        this.getRoomsPublic.doCall();
    </handler>

This handler is present in each view and it calls getRoomsPublic 
netRemoteCallHib and 
we're seeing the page displayed before getRoomsPublic has finished. Easily seen 
when 
debugging. Therefore, race condition occurs.
 So, I've made a few changes in the code - first of all, when a user presses a 
button, which is displayed before the remote calls are finished, click does 
nothing 
but stores which button was pressed, and only after the calls are finished 
click is 
processed like it was before. Secondly, to show user that his click was already 
processed we display a wait mouse cursor, so the thing looks perfect, only the 
reaction has become a bit slower, but this is required for proper work. So, 
please 
take a look at the patch and commit when done. After I applied the patch 
myself, I 
wasn't able to reproduce the bug described above, so I assume the described 
race 
condition was the reason of it.

Original comment by volkov.r...@gmail.com on 5 May 2009 at 9:54

Attachments:

GoogleCodeExporter commented 9 years ago 
Rodion, thanks for a nice patch. Groking. Where could I get 
lzwaitcursor_rsc.swf?

Original comment by alexei.f...@gmail.com on 12 May 2009 at 6:22

GoogleCodeExporter commented 9 years ago 
OMG it was supposed to be in the patch... Well, whatever, sending it now, put 
it into 
openmeetings/modules/conference/conference/resources

Original comment by volkov.r...@gmail.com on 13 May 2009 at 7:01

Attachments:

GoogleCodeExporter commented 9 years ago 
There are still small issues (two cursors appear) when I quickly click on the
different buttons while entering rooms. Yet the initial problem can be no longer
reproduced.

Committed at r2019 and verified.

Original comment by alexei.f...@gmail.com on 15 May 2009 at 5:05