Jump to content


Photo

BUG 10.3.1 - Clicking and Dragging to Select Text Stops Selecting


  • Please log in to reply
5 replies to this topic

#1 Matt Fredenburg

Matt Fredenburg

    Gold

  • Active Members
  • PipPipPipPip
  • 312 posts
  • Gender:Male
  • Accordance Version:10.x

Posted 13 October 2013 - 11:28 PM

In the following screenshot, I clicked next to the 'F' in 'Forgiveness' and dragged down. After I dragged the mouse cursor down and it went below the border of the text box, the drag/selection did not continue.

Attached File  ClickDragSelectProblem.png   63.36KB   20 downloads

 

Matt


Specs:
  • Windows 7 SP1 x64
  • Accordance 10.3.4.2
  • Quad Xeon 2.83 GHz x2
  • 16 GB RAM
  • Nvidia 580 GTX 2GB VRAM

#2 Matt Fredenburg

Matt Fredenburg

    Gold

  • Active Members
  • PipPipPipPip
  • 312 posts
  • Gender:Male
  • Accordance Version:10.x

Posted 09 November 2013 - 10:49 PM

This is partially fixed in 10.3.2. In 10.3.1, it wouldn't continue the selection at all, but in 10.3.2 it does continue the selection and scroll for a few paragraphs, but then Accordance crashes. See bug http://www.accordanc...showtopic=11299.

 

Matt


Specs:
  • Windows 7 SP1 x64
  • Accordance 10.3.4.2
  • Quad Xeon 2.83 GHz x2
  • 16 GB RAM
  • Nvidia 580 GTX 2GB VRAM

#3 Daniel Semler

Daniel Semler

    Platinum

  • Active Members
  • PipPipPipPipPip
  • 1,690 posts
  • Gender:Male
  • Accordance Version:11.x

Posted 09 November 2013 - 10:56 PM

Hi Matt,

 

  I tried to repro. the crash yesterday and failed. I was able to select more than the limit of 500 verses in a bible text and cut and paste to another program. I tried a tool (ZIBBCNT) and that worked fine too. I'm not sure what's different in your case. I'm on win7 SP1 x64 also.

 

Thx

D


Accordance Configurations :
 
Mac : 2009 27" iMac                 Windows : HP 4540s laptop
      Intel Core Duo                          Intel i5 Ivy Bridge
      12GB RAM                                8GB RAM
      Accordance 11.0.1                       Accordance 11.0.1
      OSX 10.9 (Mavericks)                    Win 7 Professional x64 SP1


#4 Matt Fredenburg

Matt Fredenburg

    Gold

  • Active Members
  • PipPipPipPip
  • 312 posts
  • Gender:Male
  • Accordance Version:10.x

Posted 09 November 2013 - 11:24 PM

Hi Matt,

 

  I tried to repro. the crash yesterday and failed. I was able to select more than the limit of 500 verses in a bible text and cut and paste to another program. I tried a tool (ZIBBCNT) and that worked fine too. I'm not sure what's different in your case. I'm on win7 SP1 x64 also.

 

Thx

D

Hi Daniel, I just tried in ESVS and it succeeded. I just tried in BECNT again but in just a one-tool workspace (my original bug report is in a fairly complex workspace), and it stopped responding and then crashed, so that at least isolates one crash from a complex workspace. It could be particular to the BECNT, it could be particular to the content of the BECNT, etc., I have no idea.

 

Thanks for the feedback!

 

Matt


Specs:
  • Windows 7 SP1 x64
  • Accordance 10.3.4.2
  • Quad Xeon 2.83 GHz x2
  • 16 GB RAM
  • Nvidia 580 GTX 2GB VRAM

#5 Matt Fredenburg

Matt Fredenburg

    Gold

  • Active Members
  • PipPipPipPip
  • 312 posts
  • Gender:Male
  • Accordance Version:10.x

Posted 04 December 2013 - 07:52 PM

Behavior is yet different in 10.3.3. As in 10.3.2, I can now click and drag beyond the border for a few paragraphs, but now Accordance hangs indefinitely and must be forcibly closed as opposed to the 10.3.2 behavior of simply crashing:

Attached File  ClickDragAndHang.png   315.45KB   0 downloads

 

 

Matt


Specs:
  • Windows 7 SP1 x64
  • Accordance 10.3.4.2
  • Quad Xeon 2.83 GHz x2
  • 16 GB RAM
  • Nvidia 580 GTX 2GB VRAM

#6 Steven van der Hoeven

Steven van der Hoeven

    Bronze

  • Active Members
  • PipPip
  • 69 posts
  • Gender:Male
  • Location:The Netherlands
  • Accordance Version:10.x

Posted 05 December 2013 - 12:17 PM

Same here. Crashed already couple of times when selecting larger portions of text. Pretty frustrating to be honest. Hoped it would have been solved by now. Having said this, I must admit that it doesn't happen as often as in earlier versions. Seems we're almost there :)






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users