forked from enlightenment/enlightenment
05402668aa
e_menu had this behaviour that submenus were not deleted automatically, relying on the parent menu to hook to post_deactivate and then delete them. This was good because maybe you don't want to delete these children, you might want to reuse them sometime. But it ended that nobody was using this feature, and worse: most use cases were failing to delete these children, causing memory leak. This commit changes the default behaviour and thus remove all the existing code that was replicating such work. If one want the old behavior, just call e_menu_item_submenu_set(mi, NULL) and it will be unbounded from the parent. If you experience any problems with that, try adding some printf() before _e_menu_free() and _e_menu_item_free() and print some relevant information like m->category and m->header.title or mi->label in order to figure out the problematic menu. SVN revision: 38528 |
||
|---|---|---|
| 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.