World: r3wp

@Henrik, the error had to do with the view. I am putting that on 
hold for now.

Is it possible to update a series outside of the button that triggers 
it? I run into the problem whereby my series is being prematurely 
updated.

it sounds like there might be an organizational problem with the 
action code.

@Henrik, I'm clueless as to why it is behaving like this.

With VID, each action should not be run, unless you are passing some 
kind of event to a face. you are probably describing your actions 
in blocks in VID, like this:

button "hello" [do stuff here]


it should not do anything outside it, unless you have set up a timer 
(which I doubt) or a FEEL (which I'm not sure you have learned yet), 
so there is probably something wrong in the action code that is run 
as you click your button.

you could also be running into a copy trap, which makes it look like 
your blocks are changed by some unknown source.

@Henrik, all these look likely. I just noticed all these new errors 
today when I revisited the code. I actually thought it was working.

http://www.rebol.net/wiki/Forgoing_faux_pas#The_COPY_Trap

@Henrik, I've been debugging for hours and I think I just don't know 
enough about REBOL because the logic of the code seems ok..or that's 
my conclusion anyways.

can you pastebin the code?

sure.

http://pastebin.com/YabkWa8p

I get an unknown paste ID

@Henrik..let me post it again

http://pastebin.com/eixcKrTQ

sorry about that. I don't know why it keeps doing that sometimes.

maybe there is a timeout on pastes

@Henrik, ok.

@Henrik, does it work now?

yes, I can see it.

ok

which button press shows the error? and which series?

@Henrik, it is not so much an error as that it doesn't do what it 
should do by design

so when I press SOON, it should advance the question 5 places ahead. 
The temp file shows it does.

the display shows a  series that didn't change

the same behavior happens for all of them.

I tried move/to ; move/skip and even tried backtracking with back 
at every button press, without luck

is one expected to click "Show Question" after clicking "Soon"?

@Henrik, yes. to get to see the other questions.

result-answer/text: " "
show result-answer


This will assign a new string to the TEXT facet of the RESULT-ANSWER 
face. What to be careful of here is that every time you pass that 
bit in the code, it is the exact same string (same memory location) 
and not a new string that gets assigned. That means that if something 
is put in there from another location, that memory location will 
no longer be empty, and the content will be shown in RESULT-ANSWER.

I'm not sure that's the problem here, though.

@Henrik, I see.  Is this normal coding or just rebol?

it is normal rebol :-)

you might use one trick - result-answer/text: copy " "

Try this in the console:

repeat i 5 [append [] i]

and see what happens.


You will see that it literally is that block at that memory location 
that is reused for APPEND.

which is a clever way for not needing to assign a word to a block 
to use it, even just temporarily.

so, if you type:




in the console, a string is really made. you don't need to assign 
it. you just have no way to reach it by reference, so it's now left 
in "oblivion" until the garbage collector picks it up.

therefore in this bit of code:

button-press?: layout [
        ; displays output for user interaction
        result-question: info " "
        result-answer: info " "


two separate strings are also made prior to the LAYOUT function even 
getting the block passed. Depending on how the code that manages 
the INFO faces initializes the face, those two strings can possibly 
be referenced.

@Henrik, wow!

@Henrik, so what is REBOL if  not call-by-reference?

@Pekr, will this work in light of Henrik's remarks?

@Pekr, what I mean to say is that will  the code be useful in the 
situation where all of my code seems to be relying on different programming 
paradigms?

todun -  I am not a good programmer, so difficult to say :-) But 
- many ppl get into some gotchas, when using REBOL. Btw - do you 
know, that subobjects (objects inside objects) are shared?

@Pekr, uhm. do you mean like the scope or something similar?

@Pekr, I'm actually a new programmer myself. But I didn't start with 
REBOL thus my confusion.

>> person: context [name: copy "" address: context [street: copy 
""]]
>> a: make person [name: "petr"]
>> probe a
make object! [
    name: "petr"
    address: make object! [
        street: ""
    ]
]
>> b: make person [name: "henrik"]
>> a/address/street: "petr's street"
== "petr's street"
>> probe a
make object! [
    name: "petr"
    address: make object! [
        street: "petr's street"
    ]
]
>> probe b
make object! [
    name: "henrik"
    address: make object! [
        street: "petr's street"
    ]
]

I mean - when you have a prototype object, which uses subobjects, 
those are shared between the clones ...

@Pekr, in this context, what is a prototype object?

todun, "call-by-reference" I will defer that question to someone 
who better knows programming terminology, than me.

@Henrik. ok