Hi Tomas,
> This way it should work as the only time when *Radio is important is
> when a form is being built.
You could store it in a property 'radio' in the form (e.g. *Top). In
this way it will be empty for a new form, and will be found and reused
when a form is reloaded during a POST event.
Hi Tomas,
now I tried some of the proposals I made.
1. We can avoid the group association list completely, if we store a
'+field' reference into components that are not the group leader.
2. We can directly use the '' function, simplifying the code a
little
Regarding that, here's a modifie
Actually, the 'set>' and 'val>' methods are also not needed.
The reduces '+Radio' to:
(class +Radio +field)
# grp val lbl
# (grp val [lbl])
(dm T (Grp Val Lbl)
(super)
(=: grp (field Grp))
(=: val Val)
(=: lbl Lbl) )
(d
Hi Alex,
> Regarding that, here's a modified version of your '+Radio' class:
that is neat:-)
> I can be called like this:
>
>(gui '(+Radio) NIL "value1a")
>(gui '(+Radio) -1 "value1b")
>(gui '(+Radio) -2 "value1c")
>...
>(gui '(+Radio) NIL "value2a")
>(gui '(+Radio) -1 "v
Hi Alex,
> Actually, the 'set>' and 'val>' methods are also not needed.
I am not sure about that, because if you use +Radio inside a chart,
the selected value will be repeated as many times as there are
radiobuttons in a group. Keeping the val NIL for all except the first
radio button avoids thi
Hi Tomas,
> > Actually, the 'set>' and 'val>' methods are also not needed.
>
> I am not sure about that, because if you use +Radio inside a chart,
> the selected value will be repeated as many times as there are
Right, this might happen.
Probably we will need those methods anyway to do some mag
Hi Alex,
> Having list cells behave like variables (by referring to their CAR
> parts) is a very useful feature. Not only for properties, but also
> for other list structures.
>
>: (setq L (1 2 3 4 5 6 7 8 9))
>-> (1 2 3 4 5 6 7 8 9)
>
>: (nth L 6)
>-> (6 7 8 9)
Hi Tomas,
> (I am worried that the second way with aliases would not work well
> with charts?)
True, but these aliases cannot be used in other cases in charts, too.
They make only sense for unique, singular fields.
Actually, I don't use aliases very often, as the numeric relative
offsets look mo
Hi Alex,
> Well, the first field will often be different anyway, because it
> typically will have a +Var or +E/R prefix.
not necessarily.
It should be possible to create it programmatically like this (as part
of a chart):
(let L '((("group1" . "value1a")
("group1" . "value1b")
Hello Howard Gordon <[EMAIL PROTECTED]> :-)
You are now subscribed
--
UNSUBSCRIBE: mailto:[EMAIL PROTECTED]
10 matches
Mail list logo
