|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Jan SchulzBlog Authors: Jan Schulz |
Notes becomes stranger every day: binding to onHelp event
Jan Schulz
|
|
Tags: 
event
lotusscript
binding
|
Comments (3)
Binding to an onHelp event via "
![]() ![]() |
A tag is a keyword that is used to categorize an entry. To view the entries with a particular tag, click a tag name or enter a tag in the box.
The tag cloud indicates the frequency of tag use. Popular tags appear darkest. The slider control adjusts how many tags are displayed in the tag cloud.
1 Chris Whisonant Permalink Thanks for the tip! Got your email re: the image cropping. I relayed that issue to IBM this past Tuesday. I'm saying it's a bug...
2 Nathan T Freeman Permalink I'll be happy to explain it.
The problem is that some events in a given form are, by a default,
part of some other event model. By default, onHelp is part of the
JAVASCRIPT event model, not Lotusscript. By putting some LS code in
on the form, you're telling Notes "consider on Help to be in the
Lotusscript events, not the Javascript events." Then you have the
opportunity to bind to it remotely.
You'll see the same thing happen with onLoad and onUnload for
forms, and onBlur, onFocus and onChange for fields. Just put
anything at all in the direct event definition to convince Notes to
add it to the Lotusscript event sequence, and you're able to attach
it remotely from anyplace where you can get to the underlying UI
object.
3 Jan Schulz Permalink That's crazy! This basicly makes "on event... " very error prone and seperating code from the Form very hard: just forget the comment (or you co-dev deletes it) and it will come apart. :-(
If it can be binded to by "on event", the it should do that. Or
throw an error when the event is not available. But not just
silently fail.