I want the ability to break when my
2019-02-15 22:55:06.932637+01 by Dan Lyke 3 comments
I want the ability to break when my breakpoint *isn't* hit.
(Right now: Why is my transient popover being closed?)
2019-02-15 22:55:06.932637+01 by Dan Lyke 3 comments
I want the ability to break when my breakpoint *isn't* hit.
(Right now: Why is my transient popover being closed?)
comments in ascending chronological order (reverse):
#Comment Re: I want the ability to break when my made: 2019-02-16 21:01:12.195887+01 by: TheSHAD0W
That's like trying to prove a negative.
Only thing you can do is set another breakpoint at a place where your first breakpoint was expected to hit but didn't.
#Comment Re: I want the ability to break when my made: 2019-02-17 19:59:03.152946+01 by: Dan Lyke
Yep. In particular, we were trying to figure out WTF was closing a dialog box, when a breakpoint on the "close" wasn't getting fired.
#Comment Re: I want the ability to break when my made: 2019-02-18 00:32:08.046995+01 by: spc476
Couldn't you put a breakpoint in the code that does the dialog box close? I mean, when I can't figure out why my program is exiting, I put a breakpoint on exit() itself.
We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.
Flutterby™ is a trademark claimed by
Dan Lyke for the web publications at www.flutterby.com and www.flutterby.net.