[backend] Logging should be done through libunity-2d logging facilities
Bug #711724 reported by
Aurélien Gâteau
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity-2d |
Fix Released
|
Medium
|
Richard Dale | ||
unity-2d (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
libunity-2d provide some logging facilities which features a few advantages over standard q(Debug|Warning):
- Print the class and method name of their caller.
- Get colored output (conditional in a branch I have not yet published)
- Handy way to debug a variable: UQ_VAR(foo) will output the following:
foo=<
- Handy glib-like RETURN_IF_FAIL and RETURN_
- Handy (not yet published) way to print the time since startup (togglable with an environment variable)
This should be cleaned up and we should start using it instead of q(Debug|Warning)
Changed in unity-2d: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in unity-2d: | |
status: | Confirmed → In Progress |
Changed in unity-2d: | |
milestone: | none → 3.10 |
Changed in unity-2d (Ubuntu): | |
status: | New → Fix Committed |
tags: | added: patch |
Changed in unity-2d: | |
milestone: | 3.10 → 3.8.6 |
Changed in unity-2d: | |
status: | Fix Committed → Fix Released |
Changed in unity-2d (Ubuntu): | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
The attached patch changes all instances of qDebug() to UQ_DEBUG, and all instances of qWarning() to UQ_WARNING