-
Thanks to both of you for reporting and resolving the issue. I will definitely put it in.
Cheers
Martin.
2009-11-15 07:28:32 UTC in Log4Qt - Logging for C++/Qt
-
The change proposed in the details is not complete. The following change would fix the problem
NSString *expandedFileName = [fileName stringByExpandingTildeInPath];
if (![fileManager fileExistsAtPath: expandedfileName]) {
// if the we cannot create the file, raise a FileNotFoundException
// if (![fileManager createFileAtPath: fileName...
2009-11-05 04:18:53 UTC in Log4Cocoa
-
The L4FileAppender class does not support the usage of ~ in the path name. This makes it very complicated to place files into the standard directory ~/Library/Logs.
This could be fixed by changing line 86 from
if (![fileManager createFileAtPath: fileName contents: nil attributes: nil]) {
to
if (![fileManager createFileAtPath: [fileName stringByExpandingTildeInPath] contents: nil attributes:
2009-11-05 03:34:24 UTC in Log4Cocoa
-
The L4FileAppender converts a file name specified via a L4Property object to lowercase. As the folder and file names are case sensitive this alters the path.
Line 22:
NSString *buf = [[initProperties stringForKey: @"File"] lowercaseString];
should be
NSString *buf = [initProperties stringForKey: @"File"];.
2009-11-05 03:30:09 UTC in Log4Cocoa
-
Hi Manfred,
The implementation of Log4t does not support to log the file name and line.
When implementing Log4Qt I was looking into how to to support file name and line number. The only way I found was that the various logging functions on the Logger class would take another two parameters to pass in the file name and line number. A call to the logger would have then looked like...
2009-09-26 05:33:48 UTC in Log4Qt - Logging for C++/Qt
-
Hi Manfred,
The implementation of Log4t does not support to log the file name and line.
When implementing Log4Qt I was looking into how to to support file name and line number. The only way I found was that the various logging functions on the Logger class would take another two parameters to pass in the file name and line number. A call to the logger would have then looked like...
2009-09-05 01:05:08 UTC in Log4Qt - Logging for C++/Qt
-
Hi Manfred,
This is indeed a bug in Log4Qt. The problem is caused by the constructors of the class FileAppender. All constructor initialize the member mAppendFile with false. The constructors should initialize the member to true.
For example the first constructor should be
FileAppender::FileAppender(QObject *pParent) :
WriterAppender(pParent),
mAppendFile(true)...
2009-09-04 23:24:59 UTC in Log4Qt - Logging for C++/Qt
-
Possible use cases:
- SIGNAL to specific logger to log message. The level is given by the SLOT
- SIGNAL to specific logger to log message. The level is given by a parameter
Not sure, if it is possible in a SLOT function to figure out what object the sender is. If this is possible on could think of something where a central object (e.g. LogManager) determines the logger and then logs the event.
2009-08-27 07:32:51 UTC in Log4Qt - Logging for C++/Qt
-
Raised enhancement requests:
- To turn the log4Qt to a real library (*.so in Linux, *.dll in Windows)
- To access the the library log routines via SIGNAL/SLOT Qt facility.
2009-08-27 07:11:24 UTC in Log4Qt - Logging for C++/Qt
-
Raised enhancement requests:
- To turn the log4Qt to a real library (*.so in Linux, *.dll in Windows)
- To access the the library log routines via SIGNAL/SLOT Qt facility.
2009-08-27 07:09:12 UTC in Log4Qt - Logging for C++/Qt
