5 Sep
2012
5 Sep
'12
8:03 p.m.
On Wednesday 05 September 2012 22:56:28 Darrell Anderson wrote:
Now the remaining problem is I can't get the messages
to appear at all. :(
I think this can be controlled by kdebugdialog.
Yes, but I haven't figured out the process works.
I set the following in the global kdebugrc:
# KInit debug info off [182] InfoOutput=4
That part seems to be working because the messages no longer appear. When I run kdebugdialog and enable the new 182 area, those new messages still do not appear.
I tried changing the global kdebugrc:
# KInit debug info off [182] InfoOutput=2
I restarted Trinity. Still no 182 messages.
Darrell
If i'm not wrong, kdDebug() means "0". Or you use kdDebug(182)?
--
Serghei