Author Topic: Win7x64 B1: VSDiff path bug  (Read 2494 times)

TKasparek

  • Senior Community Member
  • Posts: 246
  • Hero Points: 29
Win7x64 B1: VSDiff path bug
« on: August 25, 2014, 02:53:33 PM »
I often use a test directory to pull out older version files for diff. Some of our older projects use TLib source control and this is just easier to do. Anyway do a diff on a files with the following:
Setup a directory c:\some path\project\ with file.c and file2.c and c:\some path\project\test\ with file.c
  • Open diff
    • path 1: c:\some path\project\file.c
    • path 2: c:\some path\project\test\file.c
  • hit ok
  • close it
  • reopen the diff window
    • path 1 is already selected
  • press end to move to the end of line
  • ctrl-shift left x2 to select the file name
  • type file2.c
    • path 2 removed file.c from the path. Awesome, that's helpful!
  • tab x3 to get to path 2
  • press end to move to the end of line
  • ctrl-shift left to select the test\ portion of the path to overwrite
    • I want to select a file not in the test folder
  • press any alphanumeric key
    • The previously selected test\ is not overwritten as it should be but requires you to re-select the test folder to overwrite

This happens in version 18 also.

~Tom

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2897
  • Hero Points: 153
Re: Win7x64 B1: VSDiff path bug
« Reply #1 on: August 25, 2014, 03:00:54 PM »
I'm looking into this.

TKasparek

  • Senior Community Member
  • Posts: 246
  • Hero Points: 29
Re: Win7x64 B1: VSDiff path bug
« Reply #2 on: September 03, 2014, 04:10:33 AM »
B2 still exhibits this problem.

Clark

  • Moderator
  • Senior Community Member
  • *
  • Posts: 6864
  • Hero Points: 528
Re: Win7x64 B1: VSDiff path bug
« Reply #3 on: September 03, 2014, 01:36:57 PM »
We are still working on this one. Thanks for the reminder.

Clark

  • Moderator
  • Senior Community Member
  • *
  • Posts: 6864
  • Hero Points: 528
Re: Win7x64 B1: VSDiff path bug
« Reply #4 on: September 03, 2014, 02:34:29 PM »
Fixed. Also fixed another case. Thanks for reporting this.