On 10/28/2010 11:43 AM, David Seikel wrote: > On Thu, 28 Oct 2010 11:29:32 -0500 Texstar<texs...@gmail.com> wrote: > >> On 10/27/2010 10:12 PM, Carsten Haitzler (The Rasterman) wrote: >>> On Thu, 28 Oct 2010 12:14:41 +1000 David Seikel<onef...@gmail.com> >>> said: >>> >>>> On Thu, 28 Oct 2010 09:43:18 +0900 Carsten Haitzler (The Rasterman) >>>> <ras...@rasterman.com> wrote: >>>> >>>>> On Thu, 28 Oct 2010 10:35:23 +1000 David Seikel<onef...@gmail.com> >>>>> said: >>>>> >>>>>> On Thu, 28 Oct 2010 08:01:16 +0900 Carsten Haitzler (The >>>>>> Rasterman)<ras...@rasterman.com> wrote: >>>>>> >>>>>>> such bugs should get fixed. aqpps return 0 when they exited >>>>>>> cleanly with no error. anything else is an error. enlightenment, >>>>>>> unlike everyone else, doesn;t ignore it. it bothers you. this >>>>>>> solves the "why the hell did that window just vanish?" question. >>>>>>> mind you - e could do a much better ui than pop up a dialog. e >>>>>>> should really have a proper notification queue/log/stack thing >>>>>>> at some point. will worry about that for e18. >>>>>> >>>>>> Now you tell me. :-P >>>>> >>>>> the dialog is ok for now. better than not knowing what happened to >>>>> the app. apps that dont exit with a 0 exit code are saying "i had >>>>> an error". i'd bet there are quite a few that dont do this right. >>>>> this is a good opportunity to file bug reports with those apps so >>>>> they clean up their act. they are just like functions that do >>>>> this: >>>>> >>>>> int dothing(int blah) { >>>>> // do thing here >>>>> return; >>>>> } >>>>> >>>>> it's a bug. we shouldnt be hiding bugs. we should be bringing them >>>>> out and passing them to the right place to be fixed - in this case >>>>> the apps in question. :) >>>>> >>>>> just saying that we could have a less intrusive way of >>>>> logging/notifying the user than a dialog they have to dismiss in >>>>> the middle of their screen. :) >>>> >>>> I meant "now you tell me after I wrote that dialog years ago >>>> according to your desires at the time". lol >>> >>> thats what i said - dialog is fine. we have no alternative >>> mechanism right now. we'd need a nice log + notification thing. we >>> probably want one in the end anyway. but what you did was just fine. >>> >> >> Since there is no configuration option to suppress the output how >> difficult would it be for me to simply patch it out of E for now? Any >> tips on where to look in the code base? > > e_exec.c, search for a call to _e_exec_error_dialog around line 382 and > comment it out. >
Thank you kind sir. That works perfect for now and I won't get bombarded with user questions as to why such and such app is throwing a an error. Tex E17 rawks! :) ------------------------------------------------------------------------------ Nokia and AT&T present the 2010 Calling All Innovators-North America contest Create new apps & games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users