annotate doc/core-signals.dox @ 17148:9a649a04fd74
When the /pidgin/debug/enabled pref is toggled, wait until the next
iteration through the event loop before drawing or hiding the window.
This fixes the bug where we lost the width and height prefs for the
debug window because of the following sequence of event
1. Init gtkdebug window, set default width and height
2. Read in pref for /pidgin/debug/enabled and show debug window using
default width and height
3. Read in pref for /pidgin/debug/width and height, but it's too
late! The window has already been drawn using the default
width and height!
This is a pretty minor thing, but it was bugging me. I don't like
having to always make the debug window bigger when I start Pidgin.
The downside of this change is that we won't see as much debug output
in the window when starting Pidgin.
| author |
Mark Doliner <mark@kingant.net> |
| date |
Tue, 22 May 2007 07:08:57 +0000 |
| parents |
1414e0e01dc5 |
| children |
e0613cf8c493 |
| rev |
line source |
|
12053
|
1 /** @page core-signals Core Signals
|
|
|
2
|
|
|
3 @signals
|
|
|
4 @signal quitting
|
|
|
5 @endsignals
|
|
|
6
|
|
|
7 <hr>
|
|
|
8
|
|
|
9 @signaldef quitting
|
|
|
10 @signalproto
|
|
|
11 void (*quitting)();
|
|
|
12 @endsignalproto
|
|
|
13 @signaldesc
|
|
16196
|
14 Emitted when libpurple is quitting.
|
|
12053
|
15 @endsignaldef
|
|
|
16
|
|
|
17 */
|
|
|
18 // vim: syntax=c tw=75 et
|
