Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
ADS 10 rc-9
Execute below script in ADS 10.0
Then do a Script to New Window and do a Tab Compare.
You get lines changed for a lot of things which doesnt seem to be changed
When I compare with ADS 9.0 i get the correct results
See difference in pics
|
|
79 KB
|
|
78 KB
|
|
68 KB
See issue #3861.
There is only one way of making it work - making it work right. All other ways will result in people getting confused and complaining about the lack of functionality.
Comparison options should be configurable. First, there should be a way to CHANGE the options and see the result immediately. This configuration should be remembered by the GUI such that when the next comparison is done it would reuse the settings. These settings should perhaps be database- and task- specific, that is the system should allow setting one set of options in tab compare and a different set of options in text compare (or whatever).
Sending this issue back to Niels for consideration.
This doesn't work in build 8.5.0-dev12.74 - April 25
But it does work in build 8.5.0-dev12.70 - April 20.
This is before your change as indicated in issue below.
This doesn't work in build 8.5.0-dev12.74 - April 25
But it does work in build 8.5.0-dev12.70 - April 20.
This is before your change as indicated in issue below.
As one can see from replicating the issue (screenshot 3504190188.png), two scripts differ in whitespace (tabs in one case, four leading spaces in another). (There are other differences as well, but I assume those are not the meat of the issue).
Please clarify the requirements on how the tab diff should perform, whether the whitespace should be ignored, or whether the user should have control over options.
As one can see from replicating the issue (screenshot 3504190188.png), two scripts differ in whitespace (tabs in one case, four leading spaces in another). (There are other differences as well, but I assume those are not the meat of the issue).
Please clarify the requirements on how the tab diff should perform, whether the whitespace should be ignored, or whether the user should have control over options.
Ok, so the problem has to do with TABs.
Can you add a "Ignore leading/trailing whitespaces" button which persists accross Tab Compares.
Ok, so the problem has to do with TABs.
Can you add a "Ignore leading/trailing whitespaces" button which persists accross Tab Compares.
Issue #5987 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build 10.0.0-rc-11 |
| No time estimate |
See issue #3861.
There is only one way of making it work - making it work right. All other ways will result in people getting confused and complaining about the lack of functionality.
Comparison options should be configurable. First, there should be a way to CHANGE the options and see the result immediately. This configuration should be remembered by the GUI such that when the next comparison is done it would reuse the settings. These settings should perhaps be database- and task- specific, that is the system should allow setting one set of options in tab compare and a different set of options in text compare (or whatever).
Sending this issue back to Niels for consideration.