Settings and activity
5 results found
-
23 votes
An error occurred while saving the comment -
28 votes
An error occurred while saving the comment 
Daniel Chapman
commented
A pane-level lock would make this clearer without assuming the left or base file must always be protected. Show a lock icon and let users toggle it for each pane; that keeps the default safe for ordinary diffs while still allowing edits during merges or cleanup.
-
31 votes
An error occurred while saving the comment Daniel Chapman
commented
The Power Tools `UU` command already undoes unchanged adds, edits, and deletes. If the request is for that action inside Code Compare, specifically on a selected pending-changes folder after a baseless merge, that distinction would help clarify it.
-
37 votes
An error occurred while saving the comment Daniel Chapman
commented
A Pascal-aware comparison should match declarations by unit, class, and member, so moving code between sections doesn’t make the whole unit look changed.
-
56 votes
An error occurred while saving the comment Daniel Chapman
commented
It would help if manual alignment were saved with each comparison, so reopening the same file pair doesn’t require setting the match points again.
A folder-level setting should use the same comment parser as file compare, then base the file status on the remaining differences. It should be optional and show when a file differs only inside comments, so license updates aren’t mistaken for code changes and aren’t silently hidden.