Mercurial > pidgin
view doc/ui-ops.dox @ 28800:139aa186e8cc
Don't call purple_xfer_start in msn_xfer_init. purple_xfer_start is called
later after the other side accepts, and this second call clobbers the file
handle. This file handle is leaked resulting in Pidgin appearing to lock
the file stopping Windows from being able to delete it.
The changes from darkrain42's branch actually fixed the real file handle
leak except for the addition of this one line.
Fixes #1643.
author | Elliott Sales de Andrade <qulogic@pidgin.im> |
---|---|
date | Mon, 14 Dec 2009 06:50:33 +0000 |
parents | e3bf822c19c8 |
children |
line wrap: on
line source
/** @page ui-ops UiOps structures When implementing a UI for libpurple, you need to fill in various UiOps structures: - #PurpleAccountUiOps - #PurpleBlistUiOps - #PurpleConnectionUiOps - #PurpleConversationUiOps - #PurpleCoreUiOps - #PurpleDebugUiOps - #PurpleDnsQueryUiOps - #PurpleEventLoopUiOps (without this, nothing will work and you will cry) - #PurpleIdleUiOps - #PurpleNotifyUiOps - #PurplePrivacyUiOps - #PurpleRequestUiOps - #PurpleRoomlistUiOps - #PurpleSoundUiOps - #PurpleWhiteboardUiOps - #PurpleXferUiOps */ // vim: ft=c.doxygen