[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Kicker Applet Issue
From:       Randy Carnahan <rcarn () chartermi ! net>
Date:       2005-06-10 16:20:19
Message-ID: 200506101220.19982.rcarn () chartermi ! net
[Download RAW message or body]


Okay, after adding in some cout debugging statements and using 
appletproxy, this is what I get:

rcarn@cerebus [12:13] ~ $ appletproxy kclip.desktop
QLayout "fontLayout" added to kclipconfig "confDialog", which already 
has a layout
QLayout "colorLayout" added to kclipconfig "confDialog", which already 
has a layout
QLayout "buttonLayout" added to kclipconfig "confDialog", which already 
has a layout
Initial Color: #ffffff
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  20
  Minor opcode:  0
  Resource id:  0x2600086
Config Chosen Color: #748293
deskFontColor after label change: #748293
Actual Widget Foreground color  : #748293


...and it works perfectly.  The layout issues I'll fix later, since they 
have not been changed and I doubt they are the cause of the buggy font 
colors, and the X Error happens when I close the color dialog from the 
kcolorbutton, though the widget is still having the color set 
correctly.

Anyone have any idea how I can get some debug output once the applet is 
in the kicker, without resorting to using kmessagebox's?  Is the output 
redirected to some log file someplace?

Randy
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]