Mercurial > pidgin
view README.CVS @ 9843:19fd43d52d18
[gaim-migrate @ 10721]
" I didn't notice this bug had been closed until I went
looking for it again. :) I have been able to crash
Gaim 0.82cvs using the method described in the bug. It
looks like there was a patch to the gestures plugin to
catch a case where it catches the release of a
non-gestures button and the gesture is active. It seems
as though there is a way to confuse GDK (or the
gestures plugin) into missing the button release event
for the gestures button by sending it a bunch of events
at the same time (chord-clicking all 3 buttons of the
mouse at once).
This patch traps when other buttons are clicked after a
gesture is active and cancels the gesture. I don't know
if it's the Right Fix(tm), but it does keep it from
crashing on my system. I also trapped a place or two
where it would actually segfault in Gaim; the button
trap is more of a fix to keep the gesture from
"sticking". If the gesture sticks and we trap the null
data pointers, Gaim still crashes with a badDrawable X
error.
The error was 'BadDrawable (invalid Pixmap or Window
parameter)'.
(Details: serial 5520 error_code 9 request_code 66
minor_code 0) " --Dave (kat) West
committer: Tailor Script <tailor@pidgin.im>
author | Luke Schierer <lschiere@pidgin.im> |
---|---|
date | Mon, 23 Aug 2004 23:56:23 +0000 |
parents | 17a446f5e99b |
children | e4a27c9aec4c |
line wrap: on
line source
If you plan to use gaim CVS, PLEASE read this message in its entirety! Gaim is a fast-moving project with a somewhat regular release schedule. Due to the rate of gaim development, CVS undergoes frequent bursts of massive changes, often leaving behind brokenness and partial functionality while the responsible developers rewrite some portion of code or seek to add new features. What this all boils down to is that CVS _WILL_ sometimes be broken. Because of this, we ask that users who are not interested in personally tracking down bugs and fixing them (without a lot of assistance from the developers!) avoid CVS and use releases. Since releases will be made often, this should not prevent anyone from using the newest, shiniest features -- but it will prevent users from having to deal with ugly development bugs that we already know about but haven't gotten around to fixing. If you are interested in hacking on gaim, please read README and HACKING, and take note of the issues in PROGRAMMING_NOTES. (Note that they may be somewhat out of date at times.) Win32 developers, please read README.mingw. By far the best documentation, however, is the documented code. Not all parts of gaim have yet been documented, but the major subsystems are falling fast. If you have doxygen, you can use the Doxyfile in the toplevel directory to generate pretty documentation. Otherwise (or even if you do!), the header files for each subsystem contain documentation for the functions they contain. For instance, conversation.h contains documentation for the entire gaim_conversation_* API, and account.h contains documentation for the gaim_account_* API. If you have questions, please feel free to contact the gaim developers by email at gaim-devel@lists.sourceforge.net, on IRC at irc.freenode.net in #gaim, or via the sourceforge forums at http://www.sourceforge.net/projects/gaim. Please do as much homework as you can before contacting us; the more you know about your question, the faster and more effectively we can help you! Send patches to gaim-devel@lists.sourceforge.net or post them in the Sourceforge forums at http://www.sourceforge.net/projects/gaim.