As stated by several others before me, the LS compiler of all 6 versions so far, are extremely buggy.
Line of LS code disappear all the time (did not find any coherence however). It looks like it has something to do with native R6 templates, for original R5 templates behave normally so far.
Syntax error checking is pretty bad. I managed to succesfully compile a line of code containing “ReplaceItemValues”
Code that compiles and runs well on R5 produces an run-time error in R6.
Example: create a dialogbox. Create code in the postopen event. Refer to the UI document using notesUIWorkspace.CurrentDocument instead of using the more logical Source parameter. You’ll get an error in 6. R5 runs fine!
Can we have these errors fixed or can we get the good old R5 compiler back?
For your information: these ‘problems’ do cost us many hours we cannot bill to our customer(s)!!!
Syntax error checking is pretty bad. I managed to succesfully compile a line of code containing “ReplaceItemValues”
This is normal behaviour with the notesdocument class. You can specify fieldname fields to this class, so it doesnt explicity disallow stuff it doesnt recognise.
For isntance:
mydocument.myfieldName(0)
is perfectly valid. And since Lotus dont tell us which field names to use, the compiler allows “typos” through as well as fieldnames.
regarding your item: 1. Line of LS code disappear all the time (did not find any coherence however). It looks like it has something to do with native R6 templates, for original R5 templates behave normally so far.
Please see this thread in this forum:
As mentioned in my previous posting, we have thus far been unable to reproduce the problem with a specific set of steps. This is necessary in order to fix it.
If you can provide a snipet of Lotusscript code with exact steps to reproduce, we will definitely investigate.
It looks like that it has something to do with the ‘type-ahead’ kind of functionality in combination with the LS script ‘Sub-End sub’ not being entirely visible in the coding window and having changed something of the form.
How I reproduced it:
Create a new R6 database using a blank notes template
Create a new form
Go to the PostOpen event of the form and enter some lines (empty or comment) so that the ‘end sub’ line is no longer visible
Save the form using a random name (e.g. test)
Create a field on the form
Return to the PostOpen event of the form
Scroll down to just above the ‘end sub’
Enter a line of code using the ‘type-ahead’. I used “Call source.Refresh”. Press to selected the proper method.
Do not press again, which means that the cursor stays at the end of the line of code!!! (I do not know whether this is significant, but it is the way I did it).
Press - on the keyboard.
Now one of two things happen: the cursor stays where it is or the cursor jumps to the beginning of the sub. In the latter case, you’ve created the bug!!
Return to the line just below the line last entered.
Type a new line (e.g.: ‘… Test’ )
Do not press
Press -.
In my case the cursor jumps back to the beginning of the sub. If you go back to the “'… Test” line, it has disappeared.
I suspect that any line anywhere in the code will disappear after the problem has been created, but I did not check.
The problem goes away (temporarily) by closing and reopening the form.
I hope you can reproduce the problem using the steps above.
I used a Notes collaboration and designer client R6.0.2.CF2 of july 23, 2003 US language
I am able to reproduce the problem 100% of the time without turning on type-ahead. Has something to do with the order of the steps. The developer is debugging the problem.
I have type-ahead enabled in Notes 6, and it hasn’t happened to me, so I don’t think that’s the be-all and end-all. But then I don’t do the day job in 6
Does anyone else remember that bloody annoying quirk with Sametime 2.x and Notes? Whereby typing in Notes – and then getting badgered by someone via Sametime resulted in non-responsive / weird-behaving text input in Notes? I do…
Your steps to reproduce are no short of FANTASTIC. I can now reproduce the problem 100% of the time (and I don’t have Type-ahead turned on). I have forwarded the steps to the appropriate developer so he can debug the problem. Have also reopened the SPR (which was closed as “Not Reproducible”). I cannot guarantee which release this will be fixed in, but your posting has “gotten the ball rolling” again.
