Assuming you are looking at the Enlightenment internal menu code, that is. If you are looking at the async efreet code, this has never successfully been used and is not currently used anywhere that I am aware of.
On Tue, Oct 31, 2017 at 9:20 PM Mike Blumenkrantz < michael.blumenkra...@gmail.com> wrote: > There are no threads in the menu code that you are looking at, only > functions with names from a time when there was an attempt to make efreet > menu parsing asynchronous. > > On Tue, Oct 31, 2017 at 8:56 PM Carsten Haitzler <ras...@rasterman.com> > wrote: > >> On Tue, 31 Oct 2017 15:31:08 +0000 Mike Blumenkrantz >> <michael.blumenkra...@gmail.com> said: >> >> > After reviewing the currently reported issues I'm now planning to do the >> > final release on Thursday. If anyone is working on any last minute bug >> > fixes, please have them tested and committed by then. >> >> can you hold off on this until i look at the apps menu stuff? i juast am >> spotting it's using threads... and threads + efreet == bad. netstar just >> pointed this out to me (as throwing in locks into efreet seems to fix >> things >> for him). >> >> i suspect i need to review this and undo the threading if it's also doing >> efreet calls from there. >> >> -- >> ------------- Codito, ergo sum - "I code, therefore I am" -------------- >> Carsten Haitzler - ras...@rasterman.com >> >> ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
