World: r3wp

all LAYOUT does is create a big object tree, and of course you can't 
just append blocks to that

Thanks Henrik. That's what I needed to hear (how layout works).

insert-event-func [
	if event/type = 'key [
		print face/text
	]
event
]
view layout [area "hello"]

;Can a/text update before it prints?

;There's a one keystroke delay

that should be view layout [a: area "hello"]

Nicolas, you could modify the area's engage function, as in this 
patch.

append blk: select select second get in a/feel 'engage [switch act][key] 
bind [print face/text] blk/2

Thanks Anton. That was really helpful.

You're welcome.

REBOL []

index: func [dir list /local files] [
	files: sort load dir
	foreach file files [append list join dir file]

 foreach file files [attempt [if find file "/" [index dir/:file list]]]
] index %/c/ files: []

l: layout [
	f: field 600 [call t/picked]
	t: text-list 600x400 data copy files] 

search: func [f-string] [
	t/data: copy files  

 foreach s parse f-string none [remove-each f t/data [not find f s]]
	show t]


append blk: select select second get in f/feel 'engage [switch act][key] 
bind [search f/text] blk/2

focus f view l



if I type something into the field, then I click the slider, it calls 
t/picked. Why? i can't figure it out.

Sorry. That should be this.

index: func [dir list /local files] [
	files: sort load dir
	foreach file files [append list join dir file]

 foreach file files [attempt [if find file "/" [index dir/:file list]]]
] index %/c/ files: []

l: layout [
	f: field 600 [call t/picked]
	t: text-list 600x400 data copy files] 

search: func [f-string] [
	t/data: copy files  

 foreach s parse f-string none [remove-each f t/data [not find f s]]
	append clear t/picked t/data/1
	show t]


append blk: select select second get in f/feel 'engage [switch act][key] 
bind [search f/text] blk/2

append clear t/picked t/data/1
focus f view l



if I type something into the field, then I click the slider, it calls 
t/picked.

Why?

This is just the same as:
	view layout [
		field [call t/picked]
		t: text-list
	]

It calls t/picked because [call t/picked] is the action block specified 
after FIELD.
Are you confused about action blocks in VID ?

Ah sorry, it's when you click the slider that the field action is 
done (unexpectedly by you).

It's ON-UNFOCUS in face flags.  Compare:
	view layout [f: field [print "action"] text-list]
	print mold f/flags

 view layout [f: field [print "action"] with [deflag-face self on-unfocus] 
 text-list]
	print mold f/flags

As I have mentioned before here I have been working on turning strings 
into code. I've used this:
set in get to-set-word "myobj" 'text   "change a value"
where myobj: make object! [text: "default"]

and this works! I just don't know why  get to-set-word "myobj"  behaves 
that way. I'm hoping it's not a fluke because it's my Mr. Helper. 
Anyone able to explain that?

You can get from a word! as well as the corresponding set-word! and 
get-word!.  They are all the same word, after all.

So, in your example, you could replace TO-SET-WORD with TO-WORD.

I see. But what am I "getting"?

GET gets the value of the word, which you previously set to an object. 
So, GET returns that object.

Then the to-word just know by context that myobj was an object, eh? 
 The reason I ask that is that if  it was just a word and not an 
object I don't seem to have to use get.:
>> a: "test"
== "test"
>> set to-word "a" "hello"
== "hello"
>> a
== "hello"
>> set in to-word "myobj" 'text "hello"
** Script Error: in expected object argument of type: object port
** Where: halt-view
** Near: set in to-word "myobj" 'text
>> myobj/text
== "eeee"

>> set in get to-word "myobj" 'text "hello"
== "hello"

It's all good. I just was curious. Thanks Anton.

Thanks Anton!

Nicolas, you're welcome.

James, TO-WORD does not interact with the value of the word it is 
creating.

glad to see VID3 with ability to
   some-useful-name: "you will debug listbox3 someday" 
   attach 'some-useful-name

I can't remember now .. but how do you start a rebol process with 
a systray?

I mean you start the systray with do-events, but then you can't start 
your forever [ process ]

I thought you used the system:// port.

I guess if you're using a gui, you can kick off your process with 
a timer event on a face ...

Just wondering how's it's done with just the systray icon and no 
GUI

and no console

graham, maybe look at my clips.r script, it is systray only.

http://www.colellachiara.com/soft/MD3/examples/clips.html

http://www.colellachiara.com/soft/MD3/examples/clips.r

Thanks

I've abstracted the systray/forever loop out here 
http://rebol.wik.is/Code_Samples/Systray.r

S3 backup? You have plans..... beware that for large volumes you 
*have to* parallelize. SQS is there for a reason

Yes ... but it's for small volumes ... maybe a few gbs only

Is there an option to have no caret but capture keyboard events? 
 I'd like to get navigation keys for example but don't want a visible 
caret.

I see notes about using detect for hot keys instead of engage, is 
that the best way or is there a way to turn the caret part off?

FOCUS/NO-SHOW will hide the caret.

Thanks Henrik, exactly what I was looking for.

There's  a problem with that, in that as soon as you show a parent 
face, the caret will appear, because the subface will also be rendered 
by SHOW.

So if you SHOW the window face that the field is in while the field 
has the caret, then the field will be SHOWn as well, and the caret 
will be rendered.

If you look in the source of FOCUS, you can see what it's doing. 
Just do the same, except without setting the caret.

Thanks Anton, I will dig deeper then and see what my best option 
is.  I have detect version working but want to know how to manage 
this with engage if I need to.

I have a patch to handle this situation in a general way (focus-system-patch).