Changes between Initial Version and Version 3 of Ticket #88
- Timestamp:
- Apr 7, 2008, 6:07:56 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #88
- Property Status changed from new to assigned
- Property Component changed from ARSF to az* programs
- Property Summary changed from Possible azspec bug. to Restricting level 1 processing by scan line causes error
- Property Priority changed from immediate to medium
- Property Milestone changed from to The Glorious Future
- Property Type changed from task to bug
-
Ticket #88 – Description
initial v3 1 1 The use of -l in azspec produces a blank image if anything than a start line of 0 is used. The end line number does seem to produce the correct effect however. 2 3 Same problem also occurs in azatm (causes errors saying "scan jump from: 0 to 191119 scan : 191119 rejected"). Same option in azcas2 seems to work correctly.