[maemo-developers] New theme
From: Jeffrey Barish jeff_barish at earthlink.netDate: Thu Sep 18 19:37:34 EEST 2008
- Previous message: New theme
- Next message: Diablo autobuilder failed - python is not available
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jeffrey Barish wrote: > However, there is still something strange going on. When I write text to > the progress bar, the two buttons adjacent to the progress bar move 1 > pixel to the right (while the progress bar remains stationary). As a > result, the button on the left collides with the progress bar and the gap > on the right between the progress bar and the button on the right > increases from 1 pixel to 2 pixels. When the progressbar gets text, it receives a size-allocate signal. As a consequence, its enclosing hbox reallocates. I thought that possibly the hbox moved 1 px to the right when it reallocated, but that is not the case. The button to the left of the progressbar does not get a size-allocate signal after it is first realized, at which time its abscissa is 0. Is there a way for its abscissa to change to 1 -- which I know is happening because I see the button move -- without getting a size-allocate signal? Does anyone have an idea of what could be happening to account for the movement of the button 1 px to the right when I write text in the progressbar? I was thinking that I could design around the bug in maemo by catching the signal that caused the erroneous movement and then moving the button back where it belongs, but I haven't been able to find a signal related to the movement. I tried moving the button back where it belongs everytime the hbox resizes (using size_allocate), but the button remains 1 px to the right of its correct position. -- Jeffrey Barish
- Previous message: New theme
- Next message: Diablo autobuilder failed - python is not available
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]