[Psi-devel] Re: AutoResize also should resize from top to bottom

[MRAY]

Yves Goergen wrote:

>On 23.03.2005 09:03 (+0100), Remko Troncon wrote:
>  
>
>>Strange, i was hoping that the list would never grow upwards. This is 
>>something that may not happen, since growing up would mean the moving 
>>(and potentiallly moving out of sight) of your window titlebar.
>>    
>>
>
>I'm absolutely for growing it upwards, otherwise this feature will be of
>no use for me. I have my roster aligned at the bottom of my screen, with
>a little space to the taskbar. I know/can imagine it would grow upwards
>(which is effectively grow downwards and move upwards) if it already
>grew to the bottom of the screen, but when it shrinks again, it's
>somewhere at the top of my screen where I really don't want it to be.
>
>But I guess it's not much work to make it grow upwards as an option. If
>noone should want to code this, I'll make a patch for it, along with
>minimum and maximum limits for the window height.
>
>Another idea: would it take too much system resources if the window
>resizing could be done more - ehm - don't know the word - kinda fading.
>Not resize(+20) but 20x resize(+1) with a little delay. Animated, kind
>of. This would probably lead to less clicks to some place where the
>window has been 10 milliseconds before only because the window resized
>just in that moment. Now I don't like my previous idea so much anymore,
>to not resize the window while the mouse is over it.
>
>  
>
I asked Michail about this, and he said he has his roster top-aligned!?!
(would be a nice poll for the website btw).
I have my roster botom aligned, and michails patch does not work for me
either.
The problem of a disappearing titlebar is absolutely a danger, but we
have to face it. This thing needs to be able to grow upwards!
(if memory serves right Michail coded some kind of barrier that makes it
IMPOSSIBLE to grow out of the screen by itself - but creating a
scrollbar instead)

concerning the roster-resize double click issue i have another option:
if a doubleclick was made whithin the second the roster was resized just
discard the click.
(you would have to cope with a small delay though)