What steps will reproduce the problem?
1. Manually edit XDS.INP to reduce the resolution (by modifying
INCLUDE_RESOLUTION_RANGE).
What is the expected output? What do you see instead?
I would expect to see the lower resolution cut updated according to the user's
input. What I see instead is that runxdspy just keeps the previous highest
resolution.
What version of the product are you using? On what operating system?
XDSme 0.5.0.2
MacOSX 10.9
Please provide any additional information below.
Original issue reported on code.google.com by francisc...@strubicib.org on 23 Dec 2013 at 11:50
Original issue reported on code.google.com by
francisc...@strubicib.orgon 23 Dec 2013 at 11:50