New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

log messages #367

Closed
luc35 opened this Issue Feb 7, 2018 · 3 comments

Comments

Projects
None yet
2 participants
@luc35

luc35 commented Feb 7, 2018

Thanks for appJar!My project uses the logging module. Unfortunately appJar injects its own messages between mine.

For example, it injects: [Line 400->3422/SET_WIDGET_BG]: Config Label BG to #eee [Line 400->3330/SET_WIDGET_FG]: SET_WIDGET_FG: Button - #000000 [Line 400->3422/SET_WIDGET_BG]: Config Button BG to #eee [Line 400->2636/configureWidget]: Configuring: Reset of 3 with: width [Line 400->2636/configureWidget]: Configuring: Reset of 3 with: background [Line 400->3422/SET_WIDGET_BG]: Config Button BG to #ccc .... (long text)

I'm assuming this behavior is useful for appJar development, but not for appJar users. Can this behavior be turned off?

@jarvisteach jarvisteach added this to the 1.0 milestone Feb 11, 2018

@jarvisteach

This comment has been minimized.

Owner

jarvisteach commented Feb 11, 2018

This is definitely an issue that needs fixing.

appJar logs a bunch of messages at the debug level, so if you switch up a level, you can hide most of those.

However, I understand that other users might want to log their own debug messages, and not have appJar messages.

There's no way to achieve this right now, however, I would like to include this feature.

I guess their are two way to achieve this:

  • add a flag, to turn off appJar debugging
  • introduce a custom debug level, at a lower priority than debug - is this possible?

I like the idea of the second, but have no idea if it's possible - I'll add it to the future list!

@jarvisteach

This comment has been minimized.

Owner

jarvisteach commented Feb 11, 2018

OK - found a way to create a new log level: https://stackoverflow.com/questions/2183233/how-to-add-a-custom-loglevel-to-pythons-logging-facility

So, will introduce a TRACE level below DEBUG, and log all appJar debug messages at that level

jarvisteach added a commit that referenced this issue Feb 11, 2018

New log level, stop property, error checking on autoEntries, grid opt…
…ions

#367 - new TRACE log level, for appjar messages
#340 - stop function & parameter to constructor
#266 ability to select row/column - not finished, and has issues if new
rows/columns added
#366 - error messages when calling autoEntry functions on
non-autoEntries
@jarvisteach

This comment has been minimized.

Owner

jarvisteach commented Feb 11, 2018

New log level added - TRACE, 5 below DEBUG.

All appJar messages now logged at this level.

Should resolve this issue.

jarvisteach added a commit that referenced this issue Feb 11, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment