f16d0a13ef
This nasty bug was more evident with dialog reuse on configuration Basic/Advanced toggle, on some resolutions like 1280x1024 it was always reprodutible. The problem spotted by Manio is that the dialog contents is resized but the window is not. The bug follow is: * window is at some given size (640x512) * user toggles contents, calls e_dialog_show() * bg_object (window contents) is resized to MIN (!!!) * e_win_resize is called with MIN (so far, so good) * something calls e_util_win_auto_resize_fill(), size is back to 640x512 * _e_border_eval() resizes to the last value 640x512, it's unchanged so _ecore_evas_x_resize() checks for size being the same and ignore, not even callking back fn_resize (user callback, _e_dialog_cb_resize). * window is at 640x512, while bg_object is at MIN, BUG! One solution is to never change bg_object from outside _e_dialog_cb_resize, like it's after this patch. The other is to always call fn_resize even if it did not changed, which could lead to lots of useless work. By: manio Confirmed: barbieri SVN revision: 41515 |
||
|---|---|---|
| config | ||
| data | ||
| debian | ||
| doc | ||
| intl | ||
| lib | ||
| m4 | ||
| po | ||
| src | ||
| .cvsignore | ||
| AUTHORS | ||
| BUGS | ||
| COPYING | ||
| COPYING-PLAIN | ||
| ChangeLog | ||
| INSTALL | ||
| Makefile.am | ||
| NEWS | ||
| README | ||
| autogen.sh | ||
| configure.ac | ||
| enlightenment.pc.in | ||
| enlightenment.spec.in | ||
| netwm.txt | ||
| x-ui.sh | ||
| xnest.sh | ||
README
Enlightenment 0.17.0 - IN DEVELOPMENT... not a RELEASE. Requirements: ------------- Must: libc libm libX11 libXext evas ecore ecore-evas ecore-file ecore-ipc ecore-con ecore-job ecore-imf ecore-img-evas edje eet embryo efreet efreet-mime edbus ecore-txt [png loader in evas, jpeg loader in evas, eet loader in evas, software_x11 engine in evas, buffer engine in evas] Recommended: libpam [xrender engine in evas] NOTE: Users of DR16 will need to rename the $prefix/bin/enlightenment file prior to installing DR17 or it will be overwritten. You can also use the configure --prefix option to put e17 in a separate tree of its own (recommended) like: ./configure --prefix=/usr/local/e17 You will, as usual need to add the subsequent bin dir to your $PATH etc. NOTES: * do NOT use -mfpmath=sse in CFLAGS - we are not sure, but it may have bugds and screws up things in edje, evas and e17. if your gcc uses this by default (which apparently gcc4.x does on amd64), turn it off with a -fpmath=387 in your CFLAGS. * your freetype2 version must be > 2.1.7 * i remember hearing of bugs with later versions of freetype on some distributions (2.1.9 and 2.1.10) with certain patches or missing certain patches. be aware of this as a possible font problem.