-
I am working on a validator, so I open the “script editor” to get things started, and be sure the XPage doesn’t silently hose compilation because it’s a flaky beast that demands CDATA in weird places and suchlike. In this validator I do the seriously click-intensive dog and pony show to add an expression validator and open the “script editor”, then I enter a comment block start and end using /* … */ with a blank line in between. Then I paste code from another place into that comment block.
-
At this point, though the “script editor” has focus, the paste operation goes where I copied code from, duplicating all the lines that I copied. Reselect the “script editor” … does exactly the same thing, so now I have three copies of the code in the wrong place, and no copies in the “script editor”.
-
I finally give up and put “kiss off” in the “script editor”, then go find that in the Source tab and paste in my code fine as you please. It’s nice that I have the option to do this. It’s not nice that the “script editor” is such a heinous debacle that I have to do this.
-
Pasting plain text is such ridiculously basic functionality that it would never occur to me that anything, not even alpha-ware, would fail at it. Yet the “script edtior” not only fails to work, but borks other code in the process. This is using R8.5.1FP3!
-
Things like this, especially in a “Gold” product, just make Lotus appear incompetent. I know they aren’t, but that means diddly squat. If I knew nothing of Lotus and saw simplistic stuff routinely failing during evaluation, I’d buy Sharepoint. If they can’t even get the editor right, why would I trust them for anything else?
Subject: trying to reproduce
and it behaved well. Now this could be because I’m running a newer build (8.5.2 codestream) or it might be that I am missing a step in what you were doing.
A couple questions to be sure - when you say script editor, I think you mean the dialog version? Launched from validators in all properties or from one of the “pretty panels?” And when you copied the code, was it from somewhere in the xpage source editor?
I’m hopeful we’ve already fixed this, but want to be sure. Sorry for the very detailed questions, but if this bug is not fixed yet, I’d really like to squish it!
Subject: we reproduced
one trick seemed to be selecting a control along the way. We’re narrowing and looking for a fix.
Sorry you ran into this, but thank you for finding it and reporting.
It’s tracked as spr # GGRD87STEG
Subject: It was the dialog “script editor”…
-
Launched from validators in All Properties, and the code was LotusScript that I wanted to vet to JS, which is why I was pasting it into a comment block, as there were about twenty lines to port. I wanted to ultimately use the Source tab to edit this code because I detest the “script editor” utterly, and only use to to ensure the automagic XPage bits are established. As such this probably doesn’t really affect me.
-
Maybe I had too many carbs for lunch. (wry grin)
-
When you say a control had to be selected to reproduce, what does that mean? I had clicked on the xp:whatever tag in the Source tab because that’s the only way to get All Properties to allow me to access the validators. I presume that qualifies as “selecting a control”, so your results and mine are identical.
-
Sorry for not getting back sooner. I was on the VPN and can’t access the forum there.
Thanks for your time…
Subject: Sounds like (shock) a focus issue…