[Extensions, II] Continous Slicing and Error Messages

[EagleoutIce]

Let's suppose i mark the second x (alt+p or via the context menu) for continuous slicing within the following example:

x <- 4

print(x)

So far so good:

Now, let's suppose i start editing the file, writing something sensible as (please type this out to see the effect):

x <- 4
x xxxxxx
print(x)

Starting from the second x in the second line, the code is syntactically incorrect and will produce parsing errors. However, in this state every new keystroke triggers a new error message as produced in

vscode-flowr/src/flowr/internal-session.ts

Lines 98 to 100 in 8107516

	if(showErrorMessage){
	void vscode.window.showErrorMessage(`There was an error while extracting a slice: ${(e as Error)?.message}. See the flowR output for more information.`)
	}

Showing such an error is good and important, however it would be better to do this in batches (e.g., suppress the output of a new/equivalent error whenever the last one happened <1s ago). Similarly it is probably better to automatically hide these messages again after ~5-10 seconds at the latest.

[EagleoutIce]

• Only show errors if repeat after X seconds (maybe configurable)
• Keep previous "graying out" of the slice whenever the code becomes syntactically invalid (maybe again for X seconds)
• fade out existing error messaages/remove them (after X seconds)