Hi Gerald, On 11/29/2012 01:49 PM, rich...@ecos.de wrote: > My main problem with way it is done in freerdp at the moment, is that a GUI > user will never see an error message (because it goes to stdout, which you > might see on Linux if you start from a terminal, but you will never see it on > windows, because there is no stdout for GUI programms). > Freerdp just terminates silently if anything goes wrong. An average user will > just throw freerdp away as a broken bit of software, also the reason might > only be a typo on the command line, but freerdp doesn't tells about it... I see that problem too. For people integrating freerdp it's not so much of a problem, I guess. But for Users, especially when using lauchers or so, it's bad if it "just stops".
> So Marc-Andre wrote down a few words about the needs of a > logging/debugging/error handling system and I wanted to create some draft for > the API. Unfortunately I was tight up will other projects, but now I have > made a first start and it can be found below Marc-Andre's words on the wiki > at https://github.com/FreeRDP/FreeRDP/wiki/Debug-System . > > I like to ask anybody to give feedback. If we can agree on an API I will > implement at least a basic version of it. The API looks good to me. I think starting with some basic functions and improving it when required is a good approach. But all of this should go into 1.1 or later and not into the 1.0 series. Best regards, Bernhard ------------------------------------------------------------------------------ Keep yourself connected to Go Parallel: BUILD Helping you discover the best ways to construct your parallel projects. http://goparallel.sourceforge.net _______________________________________________ Freerdp-devel mailing list Freerdp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
