linuxdcpp-team team mailing list archive

[poy <696761@xxxxxxxxxxxxxxxxxx>]

fixed in rev 2577 by taking advantage of the fact that the top-level
window of a modal dialog is disabled. this creates slightly stricter
rules than what the Win API would authorize in theory, but it's
acceptable (and even necessary) for DWT.

note that by "top-level" i of course mean the top-most parent (not top-
most owner) which could be either the main window or a modal dialog.

i reproduced several scenarios by lowering the reconnect delay to a hub
that kept asking for a password, and toying with the "confirm app exit"
/ "confirm hub close" settings. all fixed here; let me know if there is
still any similar issue.

** Changed in: dcplusplus
       Status: Confirmed => Fix Committed

-- 
You received this bug notification because you are a member of
Dcplusplus-team, which is subscribed to DC++.
https://bugs.launchpad.net/bugs/696761

Title:
  Password Dialog box crash

Status in DC++:
  Fix Committed

Bug description:
   1) make a dlg box pop up for entering passwords
   2) close the hub frame right before a reconnect (what will happen is that as the HubFrame is closing a dialogue box for password input will come up but the frame is closed already so cancelling or even hitting ok will crash DC++)

   Using te steps above will 100% crash DC++ every single time

To manage notifications about this bug go to:
https://bugs.launchpad.net/dcplusplus/+bug/696761/+subscriptions