LabWindows/CVI
CVI 2017, strange behaviour in code editor.
Solved!
I hope I'm not the only one experiencing a weird behavior in the freshly installed LabWindows/CVI 2017 editor window, on two different PCs.
When I delete a line, and move the cursor down the subsequent lines disappear, and then reappear with a very disappointing effect.
An image is better than thousand words, so here it is an animation that shows it. Here I moved only a single line the cursor down.
It get worse when you're in a hurry and move down the cursor down more than once:
...and I thought CVI2017 has few new features only 
Seriously, I just tried it and can't confirm this observation - how large is your file? I've tried it with a file of 30000 lines and everything seems fine. Somehow your description sounds as if your PC is very busy with other tasks, e.g., virus scanning... but both PCs, hm...
What are your Editor Preferences?
Wolfgang, I'm happy to hear. Both PCs are absolutely unloaded.
CPU i7 3.5 GHz, 16giga RAM, SSD, Windows 10 pro fully updated, antivirus (defender) disabled.
I will investigate further...
The file you see in animated GIFs has only 375 lines.
@Wolfgang I tried on an absolutely new PC, first program installed LabWindows/CVI 2017. All settings at their defaults, no other programs except the standard bloatware coming with Windows 10.
Same problem.
I discovered it happens only in "row selection mode" (Ctrl+Ins change it)
This may explain why you didn't notice it.
Steps to reproduce:
1) Create an empty source file
2) ensure you are in row selection mode.
3) write some text rows, ideally numbered from 1 to say ... 10
4) select a single row, let's say row number 4, moving cursor up with cursor keys and pressing once shift+ cursor down
5) Hit "Del" key
6) Row 4 disappears, as wanted, AND Row 6 too!
7) Wait a second or about, row 6 reappears.
If you don't wait and instead you move cursor down, you can have the strange effect of rows disappearing and reappearing, with a weird "scroll down" effect.
If you select TWO rows at step 4) nothing strange happens.
I have not found any workaround.
AH, now I can also see it.
The bad news: your observation seems not correct... after switching back to my standard character selection mode it also occurs in this mode 
and I have not found a way to avoid this "double update"
BUT it seems specific to the project: If I load another project (*.cws) character selection mode works fine - but switching back to my original project does not help, something has permanently changed 
So if I would have plenty of time I could get my backup copy and compare if / what line in the cws / prj file has changed...
Some assistance by NI would be welcome, this behavior is annoying...
I tried both with a brand new prj/cws and with an existing project. The bad behavior occurs as I told you previously, only with "full row selection mode". May be there is some other implication or prerequisite.
At present I have very little time to do more testing.
I just checked that 2017 beta (build 230) had already this problem and I didn't notice it.
I admit I've tested only the build process compiler and general performance of compiled programs, but I haven't spent time doing any relevant editing with that version. A lesson for next time.
I hope that a workaround will be found soon...
It is too strange... I spent quite some time hunting this bug because suddenly it was gone, then it reappeared..., renaming the cws file did something sometimes....
Also this effect seems to depend on the editing history: if I open the file and the first action is deletion it may work while if I do some other editing before it may not work.
So I have situations where all scenarios work fine, i.e., whatever the row selection mode, and I could get situations where both row selection modes showed your problem...
So now I will PM you the files but will stop further investigations...
I've noticed the same cross-effects of who-knows-what.
If this is the situation, I'll too give up.
I hope that some nice guy from NI will show up here and at least he will acknowledge the problem.
