samslunch / openmeetings

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

Whiteboard resizing bug #274

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
On the Demo-portal. 

When I resize the whiteboard on which a pdf document is loaded, 
Only the frame can be resized. 

The size of the whiteboard does not change at all.

Original issue reported on code.google.com by minamoto...@gmail.com on 9 Jan 2008 at 1:09

GoogleCodeExporter commented 9 years ago
where do you resize the whiteboard? you can only resize object inside the 
whiteboard.
The whiteboard itself is not resizable

Original comment by seba.wag...@gmail.com on 9 Jan 2008 at 1:20

GoogleCodeExporter commented 9 years ago
Sorry.I understand.
Actually, what I resized was the object inside the whiteboard, not the 
whiteboard
itself. 

But I would like to show you my strange situation by an attachment jpg.
As you can see, the resized or moved object in the whiteboard goes out of the 
area of
Openmeetings. What do you think of?

FYI:My monitor resolution is 1280x1024.

Original comment by minamoto...@gmail.com on 9 Jan 2008 at 2:20

Attachments:

GoogleCodeExporter commented 9 years ago
ahh yes I understand, this is due to following:
What you see is *outside* is not the document its the documents *boundingbox*
the *boundingbox* is the temp-object which gets inited once you click on any 
object
of the whiteboard. This Boundingbox is *over* .. not *clipped* by the 
whiteboard so
it can be seen outside.
I will look for a fix to limit the bound-box resizing to the (delta-) 
width/height of
the whiteboard.

Original comment by seba.wag...@gmail.com on 9 Jan 2008 at 2:36

GoogleCodeExporter commented 9 years ago
Would it be possible to also be able to resize the whiteboard? Some of us with 
larger
screens make it hard to view it clearly.

Original comment by msol...@gmail.com on 25 Feb 2008 at 9:02

GoogleCodeExporter commented 9 years ago

Original comment by cedric.c...@uperto.com on 29 Apr 2008 at 8:31

GoogleCodeExporter commented 9 years ago
this is already fixed

Original comment by seba.wag...@gmail.com on 18 Jan 2009 at 4:03

GoogleCodeExporter commented 9 years ago

Original comment by seba.wag...@gmail.com on 29 Aug 2011 at 7:57