BUT if I call my own routine to log the message with a timestamp I loose the ability to click on on the message in the IDE and bring me to the line of code (always brings me to my routine that does the Log message)
But I too would love to be able to create my own Log function that would add date/time (to the millisecond for performance monitoring) and colors, etc.
But the "Jump to Log caller" arrow only works with the built-in Log function.
It would be great if there was some way to store a pointer to the previous location in the stack, so this can be provided to the log "arrow".
Well maybe this is a wish - it is more of a request for the source code to log to make the changes myself if that is possible.
Because B4A is now open source would the log routine be part of that?
LucaMs interesting routine - is this still being supported? What is the cost? Says a few dollars but how few?
I think a little harsh. Some have no need, Some do not know (I didn't until today), or in most of my cases it would be something I would be using for just fun (no income created)
The biggest draw back to it I see is that it is generating code into my code. When does this happen? Every time I do an edit? At compile time.
Seems like modifying Log command is a better solution (but I checked it is not part a library that is released).