| Summary: | Search and replace puts original on right and proposed change on left | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | John Arthorne <john.arthorne> |
| Component: | Client | Assignee: | libing wang <libingw> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | libingw |
| Version: | 0.5 | ||
| Target Milestone: | 0.5 RC1 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
|
Description
John Arthorne
I might have been wrong at very beginning. I thought about it from a compare point of view: the older file is always on the right side and the newer on the left side(e.g. working tree VS master, newer commit VS older commit). In replace page when compare widget is initiated, I am passing proposed contents as the newer and the original contents as older file. So I think the easiest trick we can play is to reverse the order. And because it is a read only widget, it does not really matter as long as left side is not editable. |