From: Nick H. <nic...@ho...> - 2013-03-19 18:34:03
|
Why don't we divert warning message to the NTEventLogHandler in Windows? http://docs.python.org/2/library/logging.handlers.html#nteventloghandler Nick. On 19/03/13 18:19, Enno Borgsteede wrote: > Hi Tim, > First, about the console window disappearing. That's a logical thing, > because it's a Python window, so if Gramps quits, so will the window, > leaving no time to grab any error message whatsoever. Because of that, > its use is limited to expert users who may want to see warnings while > Gramps is running, nothing else. > Knowing that the average user does not make his/her own batch files, > like Helge does, I think we can better concentrate on the Gramps Env, > which like I wrote earlier is a genuine cmd window, with everything in > place to run gramps in a terminal. You type gramps, just like you do > that in Linux, and add command line options where needed, as > instructed by our help crew or the Wiki. No need to add pause or > anything, because that cmd window will still be there when anything > goes wrong, unless someone is smart enough to crash cmd itself. > Since I already uninstalled 3.4.2 AIO, assuming that 3.4.3 AIO would > be available, I can't give you all menu options, but I will give them > once 3.4.3 AIO is there. > cheers, > Enno > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_mar > > > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel |