[ 
https://issues.apache.org/jira/browse/OPENMEETINGS-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13604460#comment-13604460
 ] 

SebastianWagner commented on OPENMEETINGS-571:
----------------------------------------------

No there is no "redraw" like in Java.
It would mean to implement in the UI:
 - a listener that waits for the resize option
 - a timer that waits until the resizing is finished (otherwise you would 
restart the cacluation multiple times while resizing is not yet finished, 
remember: THe user can press down the mouse and resize endlessly theoretically, 
so the calculation should really only happen one time and after the resize is 
finished)
 - send a method call to the chat text box to clear and re-initialize. 
Re-initializing the chat box will load only the last 10 (or so) chat items. So 
you will loose some of your history, if you have been in the chat box writing 
for a while. But that is still a lot less effort then recalculating the entire 
chat history. The history can potentially grow endless and re-calculating is a 
bit CPU intensive, so re-calcing everything might be also not a good option.
                
> Chat area does not resize when resizing browser window
> ------------------------------------------------------
>
>                 Key: OPENMEETINGS-571
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-571
>             Project: Openmeetings
>          Issue Type: Bug
>          Components: UI
>    Affects Versions: 2.0 Apache Incubator Release, 2.1 Apache Release
>            Reporter: Marius van Voorden
>            Assignee: SebastianWagner
>            Priority: Minor
>              Labels: chat, resize
>
> Go into a conference
> Resize the browser window
> Expected result:
> All contents are resized to fit the new browser window
> Actual result:
> Chat area remains the same size as before, regardless if it should be larger 
> or smaller

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to