Hi! Martin Ereth wrote:
> I just had a quick look at main.cpp. I saw that a QApplication object is > created after > the processing of the command line arguments. That is sensible, because QT > doesn't > need to be loaded to process cli-arguments. Besides that, there is a command line mode that doesn't create the QApplication at all. And it's triggered with -generateidx, therefore we need to process the options before we open any windows. Or a separate CLI-only application. But for the latter, a lot of code needs to be rewritten. > But the translator can only be loaded after QApplication. So the output on > the cli > can't be translated (yet). That only applies to the built-in Qt translator. Gettext should be usable from the beginning, as long as you call setlocale() and textdomain() first. > There seems to be a solution: > A separate class (here: application) is something like a wrapper for > QApplication: A > object of the class is being created at the very beginning, but QApplication > is loaded > some time later. Why not just create the QApplication a little earlier? In case we're going to use Qt's translation mechanism in the first place. -- Michael "Tired" Riepe <[EMAIL PROTECTED]> X-Tired: Each morning I get up I die a little ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ DVBCUT-devel mailing list DVBCUT-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dvbcut-devel
