window resizing problem #19550

New Issue

Fred Feuerstein · 2009-10-05T10:34:28+02:00

Fred Feuerstein commented

2009-10-05 10:34:28 +02:00

%%%how to reproduce: grab upper right corner to resize, pull it all the way down to the lower left corner, dont release but pull it back to a screen-filling size.
i end up with a fully trashed blender gui.
the gui layout system seems to be involved here, because i can still open the main menu or grab the timeline border to drag it, however it can not be draged down (and it should be, it somehow moved up to the very top -> see screenshot).

this doesnt happen on 2.49b or 2.48a, and if i dont resize the window, gui is working pretty well.

intel quadcore/2.4ghz
ati 4770 using catalyst driver
ubuntu 9.04
blender svn ver. 23630

2.5 looks nice!%%%

%%%how to reproduce: grab upper right corner to resize, pull it all the way down to the lower left corner, dont release but pull it back to a screen-filling size. i end up with a fully trashed blender gui. the gui layout system seems to be involved here, because i can still open the main menu or grab the timeline border to drag it, however it can not be draged down (and it should be, it somehow moved up to the very top -> see screenshot). this doesnt happen on 2.49b or 2.48a, and if i dont resize the window, gui is working pretty well. intel quadcore/2.4ghz ati 4770 using catalyst driver ubuntu 9.04 blender svn ver. 23630 2.5 looks nice!%%%

Fred Feuerstein commented

2009-10-05 10:34:28 +02:00

Changed status to: 'Open'

Fred Feuerstein commented

2009-10-05 10:42:42 +02:00

%%%uhh... forgot to say that i am using the 64bit version.%%%

Damien Plisson commented

2009-10-18 09:33:57 +02:00

%%%There is a related issue when you resize the window by very small increments (e.g. <5 pixels)

When you reduce the size of the window, all areas reduce their size to, but it doesn't seem to be proportional though. Like the right column (the one with the properties and outliner spaces on 2.5 default view) is reduced more than the ones more on the left.

It becomes weird when you increase the size (width in this example) by small increments : the right column width continues to decrease !

This looks like a rounding issue in the spaces size computation after resize.
One solution might be to maintain spaces relative size values independent of window/resolution size, like a percentage, for easing this spaces size computation after window resize ?

Furthermore, if, by such small steps, you decrease the window size too much, you come up with complete garbage (even when you enlarge again), as shown in the bildschirmfoto.png picture.

This bug is a show stopper for the "live resize" feature, that is having window contents redrawn continuously while the user is changing its size.
(This feature is the one that makes lots of window size changes by small steps)

This bug already existed in 2.4x releases.%%%

%%%There is a related issue when you resize the window by very small increments (e.g. <5 pixels) When you reduce the size of the window, all areas reduce their size to, but it doesn't seem to be proportional though. Like the right column (the one with the properties and outliner spaces on 2.5 default view) is reduced more than the ones more on the left. It becomes weird when you increase the size (width in this example) by small increments : the right column width continues to decrease ! This looks like a rounding issue in the spaces size computation after resize. One solution might be to maintain spaces relative size values independent of window/resolution size, like a percentage, for easing this spaces size computation after window resize ? Furthermore, if, by such small steps, you decrease the window size too much, you come up with complete garbage (even when you enlarge again), as shown in the bildschirmfoto.png picture. This bug is a show stopper for the "live resize" feature, that is having window contents redrawn continuously while the user is changing its size. (This feature is the one that makes lots of window size changes by small steps) This bug already existed in 2.4x releases.%%%

Ton Roosendaal commented

2009-10-20 09:44:28 +02:00

%%%This is caused by the screen subdivision system, it stores internally integer coords for splits, which causes things to go bad on extreme small sizes.
For all platforms there should be a minimum size hint set, like 320x240. In OSX it already is. Campbell knows how.%%%

%%%This is caused by the screen subdivision system, it stores internally integer coords for splits, which causes things to go bad on extreme small sizes. For all platforms there should be a minimum size hint set, like 320x240. In OSX it already is. Campbell knows how.%%%

Campbell Barton commented

2009-10-20 09:55:10 +02:00

%%%fixed in svn.%%%

Campbell Barton commented

2009-10-20 09:55:10 +02:00

Changed status from 'Open' to: 'Resolved'

Campbell Barton closed this issue

2009-10-20 09:55:10 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

window resizing problem #19550