Hi,
I'm using Beyond compare for a long time and I think the following behavior is newer.
When I'm adding new lines of code in a C file I get the following comparison result:
if(MyOldFunction())
{
return FALSE;
}
if(MyNewFunction())
{
return TRUE;
}
I checked white spaces but the closing bracket line of the new code are really equal to the closing bracket line of old code.
I think the comparison doesn't show the closing bracket of old code as equal because the search order for comparison is in inverse order. These would explain the result I have.
Is there any way to invert the order (switch off invert order) to make the comparison result more near to the real changes ?
This is the only ugly problem I have with beyond compare and I hope there is a way to fix it.
I'm using Beyond compare for a long time and I think the following behavior is newer.
When I'm adding new lines of code in a C file I get the following comparison result:
if(MyOldFunction())
{
return FALSE;
}
if(MyNewFunction())
{
return TRUE;
}
I checked white spaces but the closing bracket line of the new code are really equal to the closing bracket line of old code.
I think the comparison doesn't show the closing bracket of old code as equal because the search order for comparison is in inverse order. These would explain the result I have.
Is there any way to invert the order (switch off invert order) to make the comparison result more near to the real changes ?
This is the only ugly problem I have with beyond compare and I hope there is a way to fix it.
Comment