Hello Anton,
> Title: "Iterated Rotarys"
> File: %iterated-rotarys.r
Nice idea nevertheless, thank you! This way also changing (state, face
text stc.) iterated items are easily implementable!
Although the iterated list seems to be more than a bit awkward than
any others found in streamlin
e button)
- depends on face/state
}
History: [
1.0.0 [6-May-2002 {First version inspired by a post by Geza Lakner
MD [[EMAIL PROTECTED]]
entitled "[REBOL] Re: Iterated check box anomaly (resend) - now, the
ROTARY!" on 6/5/2002} "Anton&quo
Hello Anton,
> Don't listen to that negative stuff.
> Here seems to be a solution. Tell me if it works.
Thank you, it really works! But ... :-)) Now I am stuck with a more
complex structure, namely the rotary.
I tried several initialization strategies, some of them even did not
let to "rotate"
Yes, but this will take some time for preparation... :)
I actually wanted to try that next. I am getting my
head into lists, iterated or not.
Anton.
> Hi Anton,
>
> > Don't listen to that negative stuff.
> > Here seems to be a solution. Tell me if it works.
> > Thanks for asking, by the way. M
Hi Anton,
> Don't listen to that negative stuff.
> Here seems to be a solution. Tell me if it works.
> Thanks for asking, by the way. Months could have
> gone by and I would never have figured it out.
Well done. But for your next trick can you make the multiple
highlighting disappear off the in
Don't listen to that negative stuff.
Here seems to be a solution. Tell me if it works.
Thanks for asking, by the way. Months could have
gone by and I would never have figured it out.
Anton.
a: copy []
q: [
["1" "Setup"]
["2" "Install"]
["3" "Post-install"]
["4" "
Hi,
> This is strange: the checkboxes appear to behave as if they were ONE,
> if they were the SAME face visually but the branching upon their
> individual logical state executes normally and fills the answer block
> appropriately.
Yes, they are one.
Visually they appear to be many, technically
Hello Romano,
>> First I tried toggles instead of check boxes, but selecting one of
>> them caused to redraw all toggles below the selected one in selected
> Should be the same, never tryed, but you must think that, when supply is
> called, all the changed field are in an unknown state: you must
Hi, Geza
> BTW What is the exact timing of the 'supply function, i.e. on what
> occasion (event) will it be launched? As far as I can see, it is
> called not only at initialization time (filling the list with items)
> but even when I click in the list?
There is not an exact timing. It is called
Hi Geza,
List & supply is just a VID interface to face iteration in View. ("supply"
is akin to a "pane func" with a little less effort needed)
If you would like to dig further in iterated faces, the following Zine
article may help.
"Look ma, just one face"
http://www.rebolforces.com/zine/rzine-1
Hello Romano,
> you must re-initialize the check data field:
> if index = 1 [face/data: find a face/text]
Hmmm, tricky ;-) Thank you very much, it is a great idea!
BTW What is the exact timing of the 'supply function, i.e. on what
occasion (event) will it be launched? As far as I
Hi, Geza
you must re-initialize the check data field:
a: copy []
q: [
["1" "Setup"]
["2" "Install"]
["3" "Post-install"]
["4" "Run"]
]
view layout [
below
list 550x180 [
across origin 2x2
answer: check [
12 matches
Mail list logo
