Author Topic: SlickEdit 2013 (v18.0.0.13) Screen Update / Buffer Handling Issue  (Read 2094 times)

tuchman

  • Senior Community Member
  • Posts: 144
  • Hero Points: 7
This problem has happened once on a recent beta, and once with the official release.  I would say ~5% of the time I run a perl script-driven make and watch the progress in the build tab.  In the more recent case I started the make, then switched to surfing with chrome, then returned to see the make's progress. 
1) The first screenshot shows three issues.  The file buffer had a "dead" area near the bottom of the displayed buffer.  I could scroll the buffer, but the last two lines did not change.  The debug tab looks clipped on the left.  The build tab shows only the first lines of the make, yet the make had already completed.
2) The 2nd screenshot shows changes after I changed the bottom tab from build => ? => build.  I see the complete build output now, but the other issues persist.
3) The 3rd screenshot shows changes after I changed file buffers from original => ? => original.

Thanks in advance,
-ken

SlickEdit 2013 (v18.0.0.13 64-bit)
Licensed number of users: Single user
License file: C:\ProgramData\slickedit\18\slickedit.lic
Build Date: June 18, 2013
Emulation: CUA
OS: Windows 7 x64
OS Version: 6.01.7601  Service Pack 1
Memory: 61% Load, 2300MB/3767MB Physical, 2456MB/7532MB Page File, 218MB/8388607MB Virtual
Shell Info: C:\Windows\system32\cmd.exe /q
Screen Size: 1280 x 1024
Project Type: Perl
Language: .pl (Perl)
Installation Directory: C:\bin\se2013\ (non-removable drive,NTFS,46027MB free)
Configuration Directory: c:\data\se2013\18.0.0\ (non-removable drive,NTFS,46027MB free)

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6126
  • Hero Points: 470
Re: SlickEdit 2013 (v18.0.0.13) Screen Update / Buffer Handling Issue
« Reply #1 on: June 25, 2013, 11:20:07 am »
Hmm..very odd. This looks like a very old issue that was fixed in v17 and only happens on Windows.

Do you have Visual Studio installed? If so, run spyxx and use Find Window. If the SlickEdit main MDI window has ANY child win32 windows that can be chosen with Find Window, that's the bug. The only win32 window is supposed to be the outer main MDI window itself.

To fix the problem, simply restart SlickEdit. This won't tell us how the extra win32 windows are being created though but it will let us know what to look for.

Thanks