Author Topic: Version-control (perforce), bad error dialogs  (Read 2025 times)

jporkkahtc

  • Senior Community Member
  • Posts: 1960
  • Hero Points: 185
  • Text
Version-control (perforce), bad error dialogs
« on: May 04, 2013, 07:21:48 pm »
In Compare project to perforce:
I checked a folder with about 15 files in it and clicked "diff".
It opened DiffZilla showing the first file differences.
Then I closed this diff window and Slick opens this error:

   "Could not compare 'compare' with most up to date version
   E:
   \src\p1\blah\trunk\ui\src\com\htc\myproject\ui\SecondFile.java
   
   
When I dismissed this error dialog slick then it opened diff on SecondFile.java

Repeat several times, then I get:
   Files match, view them anyway?
Which files match???
A filename would be really helpful here.


#1: Weird error dialog. I have no files named "compare" so clearly the strings in this dialog are wrong.
But more likely, it is attempting an invalid comparison operation altogether.

#2: Dialogs like "Files match" (much like my all time favorite "File not found error" error dialogs) should *ALWAYS* tell me what file they are complaining about.

#3: Filename formatting is screwy -- putting the drive letter on a line by itself and then the rest of the path on the next line is just wrong.

Dan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 2456
  • Hero Points: 137
Re: Version-control (perforce), bad error dialogs
« Reply #1 on: May 06, 2013, 01:54:47 pm »
The error in this case was incorrectly formatted.  Some errors take a command name, so it can match the command name for that version control system (ie submit vs commit).  This one simply got formatted wrong, the file name should be where "compare" was, and the error output where the file name was.  Thanks for the report.