Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: double-click to exit program?

  1. #1
    Join Date
    Apr 2004
    Posts
    208

    Default double-click to exit program?

    I remember this being the case in Bibleworks 7: I still (BW 8) need to click twice on the "exit program" X in the upper right-hand corner to exit out of Bibleworks. Not a big deal; just wondering if that's an isolated issue or common among other users. I was going to blame it on Vista, but may be it's the economy . . . ?

    Ingo

  2. #2
    Join Date
    Apr 2004
    Posts
    2,028

    Default

    Quote Originally Posted by ingosorke View Post
    I remember this being the case in Bibleworks 7: I still (BW 8) need to click twice on the "exit program" X in the upper right-hand corner to exit out of Bibleworks...
    No, it's not just you. The BW team kept this feature in!

  3. #3
    Join Date
    Sep 2007
    Posts
    1,181

    Default

    Maybe there's a glitch in my system, but I just need to click once and the program exits.

  4. #4
    Join Date
    Apr 2004
    Posts
    2,028

    Default

    Quote Originally Posted by ISalzman View Post
    Maybe there's a glitch in my system, but I just need to click once and the program exits.
    No, it's not a glitch in your system. I guess you just didn't receive the unlock code for this feature, which means you're not one of BW's special users.

  5. #5
    Join Date
    Apr 2004
    Posts
    498

    Default

    I didn't receive the special code, either. I think the "double-click to exit feature" has been there since BW6 or so. I haven't been able to establish a pattern to reproduce this issue. Until we can reproduce the issue on-demand, it is hard to diagnose and fix the problem.

    Maybe Amazon's control of "one-click shopping" pushed us to use "double-click exit". :-)
    Glenn Weaver

    For technical support, please contact Customer Support.

  6. #6
    Join Date
    Apr 2004
    Posts
    2,028

    Default

    I don't think this is reproducible because it doesn't happen all the time. I think it's a matter of a specific window not having the input focus when you click the x mark, thus the first click only establishes the input focus and then the second click actually sends the quit message.

  7. #7
    Join Date
    Apr 2004
    Posts
    2,028

    Default

    Quote Originally Posted by Glenn Weaver View Post
    Maybe Amazon's control of "one-click shopping" pushed us to use "double-click exit". :-)
    Actually, you may have hit upon the problem. It could be that everyone who has signed up for "one-click shopping" on Amazon has inadvertently triggered this behavior in BibleWorks. Thus, cancelling your account with Amazon may fix it.

  8. #8

    Default

    Unbelievable. It's still in 8?
    I complained about it in 6, but M. Bushell was unable to reproduce it.
    I have it in 7, too.
    I don't know the reason. If you just start BW and then close it immediately it does not happen. It only happens if you close it after some time.
    No other program behaves like this. Windows XP.
    Best wishes
    Wieland
    <><
    ------------------------------------------------
    Wieland Willker, Bremen, Germany
    http://www-user.uni-bremen.de/~wie
    Textcritical commentary:
    http://www-user.uni-bremen.de/~wie/TCG/index.html

  9. #9
    Join Date
    Apr 2004
    Posts
    2,028

    Default

    Quote Originally Posted by wie View Post
    No other program behaves like this. Windows XP.
    I'm 99% certain it's a focus issue. BW has about a gazillion windows, and multiple windows even in its main interface. For example, the two tab groupings are windows unto themselves, as well as the toolbar, etc.

    It's also possible that there are ghost windows which are created/destroyed after certain tasks, although only BW knows that for sure.

    Anyway, it only happens at certain times, and the fact that it won't close on the first click sometimes tells me that it almost certainly is a focus issue, nothing more.

  10. #10
    Join Date
    Mar 2004
    Posts
    803

    Default

    Scott's analysis is correct. It is a focus issue. I have had it happen to me maybe 6 times in 3 years and have never been able to reproduce it. I do not think it is a BibleWorks issue because it has happened a couple of times in other applications. Hopefully it appears to happen almost exclusively in BW because people use BW a lot! But if we can't reproduce it we can't fix it. If it is a huge annoyance I can spend time on it, but the benefit to users versus others things I can do with my programming time is probably minimal.
    Mike

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •