Ram Watch / Search "Differences" column

[GoogleCodeExporter]

As I said here (http://code.google.com/p/bizhawk/issues/detail?id=39#c1), I 
don't feel like the previous definition "Prev value as change" for Ram Watch 
makes a lot of sense; -2 will never match a previous value for an unsigned 
watch. For that reason alone, I think we should have a separate column called 
"Difference" to store this information (I would need to move this to some data 
item anyway in order to properly store and fix Issue 39).

In addition, I thought of the implications for Ram Search. Right now, we have a 
related search option: "Different by". Perhaps the most useful time to use 
"Different by" is to find the difference between the rows' values and the 
previous value. This is fairly limited; all it does is find the values that 
differ from the previous value by the specified number exactly. Having a 
"Difference" column would allow us to use all of the operators to compare this 
difference, which would allow us to filter out ranges of differences (If I 
wanted to find values that changed but not by more than +2, I'd search if the 
difference is not equal to zero and then search if the difference is less than 
or equal to +2). If we wanted to ignore the sign (Maybe I want to find a value 
that has changed by 2 but I don't care if it increased or decreased by 2), we 
can put a checkbox for "Absolute Value" next to the "Difference" radio button. 
The "Different by" operator would still remain ("Difference" is a value, not an 
operator), but I figure this new column would allow us to compare values with 
the previous value better.

Original issue reported on code.google.com by brandman...@gmail.com on 10 Jun 2012 at 2:34

[GoogleCodeExporter]

Ram Watch has this as of r2467. I still think it should be implemented in Ram 
Search as well. Just to clarify: this option would be "Compare By", not 
"Compare To". What I mean by this is that you'd need a text box next to it, 
like we have for "Number of Changes", instead of comparing the difference to 
its address' current value, which would be ridiculous. There's a lot of ways to 
implement this, but I think it'd be very useful, even if it were just used for 
sorting.

Original comment by brandman...@gmail.com on 5 Jul 2012 at 6:43

• Changed state: Started

[GoogleCodeExporter]

Switching this to priority low.  I just don't see a good use case for a 
differences column, any case I can think of has a better alternative strategy 
when weeding through addresses.  Give me a good use case and I will bump the 
priority

Original comment by adeli...@tasvideos.org on 17 Sep 2012 at 1:32

• Added labels: Priority-Low
• Removed labels: Priority-Medium

[GoogleCodeExporter]

The difference column and ability to search by difference has been implemented

Original comment by adeli...@tasvideos.org on 7 Oct 2013 at 12:30

• Changed state: Fixed