Toggle field visibility

I need to disable or hide a set of checkboxes in Notes when a specific radio button is selected. Doing this in javascript is easy on a webpage - how is it done for notes?

In other words:

Radio button values: Big; Small; none

Check box values: Red; Blue; Green; Black

if the radio button “none” is selected, hide the checkboxes; if any other radio button is selected, show the checkboxes.

Thanks

Subject: Toggle field visibility

Hide-when formulas (the windowshade tab of the object properties for the object(s) to be hidden, “Hide paragraph when formula is true”) and “refresh document on keyword change” set in the controlling field’s properties, second tab.

Subject: RE: Toggle field visibility

These are on the second page of a tabbed table. Didn’t notice before, but setting it up like this causes the document to refresh - on the web it puts the user back to the first page of the tabbed table. How do I get around this?

Subject: RE: Toggle field visibility

Thanks Stan. That takes care of visibility. Now, what about something similar to the javascript property “disabled”? How would you handle that in Notes client?

Thanks in advance

Subject: RE: Toggle field visibility

No setch thang. What we do in Notes is use two fields, one editable and one computed-for-display, using the editable field’s name as its formula, and hide them alternately.

Subject: RE: Toggle field visibility

For fields OTHER than checkboxes/radiobuttons, if the style of the field is “OS”, then you can use the “event” in the programming pane labelled “Input enabled”. If the event evaluates to 0, the field is disabled. Otherwise it’s enabled. Since the value is a computation, a refresh on the page/form will recompute whether the field is enabled/disabled.

(This is new in ND6. It was not added to checkboxes/radiobuttons because Notes currently requires you define radiobuttons as an entire group and there wasn’t a way to let you enable/disable individual buttons given this mechanism.)

Bill Andreas

Senior Designer, IBM

Subject: *Cool.

Subject: But…

It doesn’t work with fields in layout region ?

Subject: RE: But…

Not much does. Consider layout regions a “deprecated feature”, retained only for backwards-compatibility.

Subject: * Neat! Ta. =B-)