You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+9-1Lines changed: 9 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,8 @@
10
10
11
11
* PopUpErrorAction has been added in order to inform the user in cases where to cannot parse the source code.
12
12
13
+
* Sublime settings file has been added, from which you can turn on or off, showing the main result when it is not visible as well as the pop-ups with error information.
14
+
13
15
### Fixed
14
16
15
17
* fixed the empty brackets bug in the repair modulebugs with ":" addressed, needs more testing and a subsequent bug
@@ -28,7 +30,11 @@
28
30
29
31
* fixed a bug in the above/below argument command, which occasionally caused of by one errors.
30
32
31
-
* in the info module, fixed a bug in the get_body function where ast.IfExp was missing for some reason.
33
+
* in the info module, fixed a bug in the get_body function where ast.IfExp was missing for some reason
34
+
35
+
* Yet another forwarding bug in the argument module:(
36
+
37
+
* fix a bug in the big region of interest module which caused off by one error in the above below command, when the original selection was in an empty line.
32
38
33
39
### Changed
34
40
@@ -60,6 +66,8 @@
60
66
61
67
* In the same spirit, the query module has been modified and has a new attribute in order to store the above exception. The application module checks if this attribute HUD stored exception and displays an error through the PopUpErrorAction!
62
68
69
+
* The interface module has been modified to accept settings in its constructor.
and ndir is an interger specifying how many lines (relative to the current) up or down your roi is.
105
105
106
+
106
107
But why both "above" and "up"? The difference lies in that above only counts "interesting lines", that is(physical) lines containing function calls. The following example should clarify this:
107
108
108
109

109
110
110
-
Though if we want to be more precise, we count lines that contain the beginning of function calls! this is important because logical lines can extend over multiple "physical" lines. The last example in the gif contains such an example, physical lines still determine the line to which above/below refer and result and alternatives from that physical line will be prioritized, but alternatives will also be offered from the whole logical line!
111
+
Though if we want to be more precise, we count lines that contain the beginning of function calls! this is important because logical lines can extend over multiple "physical" lines. The last example in the gif contains such an example,but to give you a better idea:
112
+
113
+

114
+
115
+
so you can see that
116
+
* physical lines still determine the line to which above/below refer
117
+
* result and alternatives from that physical line are being prioritized, but
118
+
* The whole logical line is scanned for alternatives !
119
+
120
+
In a more complex scenario, if there are multiple functional calls in the physical line and you up for using an ordinal adjective, in order to to preserve sanity, the main result will be decided by taking into consideration the order of lexical appearance:
121
+
122
+

123
+
124
+
125
+
Finally, even though the argument query was originally designed to operate on a single logical line, make things more consistent, an exception was made for the case when the physical line that you are targeting contains more than one logical lines. In such a case, all the logical lines are processed in the monitor similar to the previous case, with important distinction that both the result and the alternatives must come from this physical line, where as in the previous case either one of them can come from other physical lines, if no suitable candidate is found.
Copy file name to clipboardExpand all lines: doc/SelectBigROI.md
+8Lines changed: 8 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -177,6 +177,14 @@ Sub indexing functionality has been expanded to include picking up parts of stri
177
177
178
178

179
179
180
+
We can pick up parts from the URL, individual words or letters, or part of a camel or snake case. this feature is still immatur and needs more work, but I am planning to improve and also expand it with the ability to select a whole range.
181
+
182
+
Also something that was kind of missing,you can now select a subset of an arithmetic expression :
183
+
184
+

185
+
186
+
Once again you need to pay attention to operator precedence and as you can see there are some edge cases that need to be fixed.
187
+
180
188
Finally, we clarify one more thing! What about relative vertical offsets when using above? We know that these abstract vertical keywords only count interesting lines, but what do we count as interesting here? To stay compatible with all of the above, we count all lines containing our desired big region of interest regardless of whether we can extract or not from them information with the sub index! As an example:
0 commit comments