Topic: Crash on scrolling (1 of 2), Read 58 times Conf: Error messages, Crashes From: Manuel Diaz Date: Friday, July 23, 2004 05:59 PM Hello, I've come across a fairly consistent way to crash Vedit 6.12.1 (05/24/04): open a binary file, select Binary-64, scroll repeatedly by clicking on the scrollbar -> there's a popup saying "Line too long; {CONFIG, File handling, File type} now set to 64 {Binary}", CPU usage increases to around 50%, Vedit hangs and has to be killed from Task Manager. Word wrap is enabled. No problem with wheel scolling I've got this also with text files, but more clicking is required. Working on Win2k Pro, SP4 (Logitech Mouseman Optical, driver 9.41). Any confirmation? -- Best regards, M. Diaz

Topic: Re: Crash on scrolling (2 of 2), Read 60 times Conf: Error messages, Crashes From: Ted Green Date: Monday, September 06, 2004 01:35 PM At 09:14 PM 7/23/2004, you wrote: >> I've come across a fairly consistent way to crash Vedit 6.12.1 >>(05/24/04): open a binary file, select Binary-64, scroll repeatedly by >>clicking on the scrollbar -> there's a popup saying "Line too long; >>{CONFIG, File handling, File type} now set to 64 {Binary}", CPU usage >>increases to around 50%, Vedit hangs and has to be killed from Task >>Manager. Word wrap is enabled. No problem with wheel scolling This is fixed in 6.13. The problem was that it was possible to get VEDIT into both Word wrap mode and record mode, which are really mutually exclusive. Now, all word wrap modes are ignored in record mode. (The toolbar buttons are even greyed out to emphasize this.) Ted.