World: r3wp

Your last example works

Your 'c function is my 'hello function.

why is it wrapped in a block?

Because I need to bind that code in open-window.

my functions already exist in the global context

It creates new copies of the functions in window-functions each time 
a new window is opened.

that's cheating!

I see.

Ok, in that case, go back to the first example I posted. I'll need 
to modify it a little bit..

the situation is that I have a lot of screens inside tabs.  now sometimes 
I want to re-use those screens outside the tabs ... so I just copy 
the code and put into a new window .. but then I want to be able 
to make the functions that operate on the original sceens work on 
my new ones.

I did actually try copying the functions but they still operated 
on the original windows and not the new ones ... :(

I got it all working using Gregg's suggestion .. but I'm open to 
others

Well, here's the modified code.

hello: does [f/text: copy "hello" show f]

bind-funcs: func [word] [

 foreach window-function [hello][bind second get window-function word]
]

open-window: does [
	view/new center-face layout vid-context [
		f: field

  button "Hello" [bind-funcs 'f hello] ;  Pass to BIND-FUNCS any one 
  of the words in this context (here 'f).
		button "Clear" [clear-face f]
	]
]

open-window
open-window
do-events

It's not brilliant; in each button action you have to call bind-funcs 
before calling any of the window functions (eg. hello).

which is what I am doing at present .. binding before calling the 
function

Yeah, so I've just made it more complex than necessary.

now if the functions could access the 'self of the object, it could 
bind automatically?

just rewrite every function ...

It's the same problem; how could the functions know which object 
to bind to?

so I would pass the context to each function as a parameter

so these would be self aware functions :)

Usually I just write functions and pass the face(s) that they need 
to work on. Passing the context could cut down the number of arguments 
passed to one. But usually I don't need to pass more than one face, 
so it doesn't seem of that much benefit.

So, rewrite the function to take a parameter word from the context 
it is to work in, and let it bind itself to that context ...

well, I have named fields ... and a bunch of data coming in which 
I need to fill the fields

either I fill by position, or by name

You can bind directly to a context now, you don't need to pass an 
example word, unless you are using a very old rebol version...

anonymous contexts ??

Alright, well, if you have a function which manipulates many faces, 
then there are arguments to be cut down, and there is a benefit.

Anonymous, yes.
ctx: context [a: 1]
bind [a] ctx

You no longer have to do:
bind [a] in ctx 'self
or
bind [a] in ctx 'a

Ok, so you can rewrite each of your window functions to take, and 
bind itself to, a context argument; or, you can add a "BIND-FUNCS" 
function, taking a context argument, which rebinds all your window 
functions to the context.
Similar to what I've done above.

So, each function binds itself:

hello: func [ctx] [do bind [f/text: copy "hello" show f] ctx]

open-window: does [
	view/new center-face layout vid-context [
		f: field

  button "Hello" [hello self] ;  Pass to HELLO this context (created 
  by VID-CONTEXT).
		button "Clear" [clear-face f]
	]
]

open-window
open-window
do-events

yes ...

Or, all the functions are rebinded by BIND-FUNCS:

That might be the easier way .. .to get the binding be handled by 
the function itself

hello: does [f/text: copy "hello" show f]

bind-funcs: func [ctx] [

 foreach window-function [hello][bind second get window-function ctx]
]

open-window: does [
	view/new center-face layout vid-context [
		f: field

  button "Hello" [bind-funcs self hello] ;  Pass to HELLO this context 
  (created by VID-CONTEXT).
		button "Clear" [clear-face f]
	]
]

open-window
open-window
do-events

(Oops - the comment should be ; Pass to BIND-FUNCS ...

you don't like the idea of the function itself doing the binding?

If you don't like the idea of modifying all your functions, then 
it might be more convenient. Also, you might call bind-funcs just 
once, then call several of your functions afterwards without having 
to pass them anything.

(Note, all this tricky function rebinding makes the functions non-reentrant.)

Another idea I have is to patch your styles (eg. BUTTON, FIELD etc.) 
so that when their action blocks are converted to functions, the 
blocks are bound to the right context.

You can see here the block: function

print mold get in svv/vid-styles/button 'multi
...
block: func [face blk][
        if pick blk 1 [
            face/action: func [face value] pick blk 1

            if pick blk 2 [face/alt-action: func [face value] pick blk 2]
        ]
    ]


It has all it needs to determine the context returned by VID-CONTEXT.

From the FACE argument (eg. the newly created BUTTON face), you can 
climb up to the window face, then search through its subfaces for 
one with a word VAR facet. That word should have been already bound 
by VID-CONTEXT, so that means we can pre-bind the action block to 
the context (just before the action function is created from it).

You would just need to modify the multi/block function for each of 
the styles which converts block to action functions.

why does re-entrance matter?

we don't have multitasking in R2

Actually, it looks like the multi/block function is the same for 
all styles.

If you want to port your code later, it might be significant. If 
not, don't worry.