World: r3wp

no ...

don't use any on-focus triggers

process-keystrokes has been inlined into the display function. This 
fixes those errors where typing while the focus is on a button placed 
the characters into the previous field/area with focus.

Ok, so I can add my function key handlers there then.

Have you thought of adding them to rebgui ?

afterall, they are on the keyboard !

Are these global in nature or specific to a display?

mine are global .. and are just redefined by the user at startup.

e.g.

	display/F9 "Test" [...] [print "I pressed F9 on this display]

AT what point do you get the focus error? On app startup or tab navigation?

don't understand

Does the focus error occur before anything is displayed?

on app startup

I have one password entry screen, then a status window, and then 
before the main window pops up, I get this error.

password screen closes, status window appears, and then the error

Can you grep your source code for "focus-action: :on-focus" ... that 
line doesn't exist in the standard SVN source. Using any custom widgets?

drop-tree ?

yes, its in drop-tree

Is that a critical widget for you?

No, I am removing it now.

It was nice to have but no critical

chart, 
drop-tree, 
grid & 
input-grid need a bit of work to get 
them working again with Beta 2.

Ok.

What do you think then of adding global function key handlers?

Not a bad idea. How do you specify them (i.e. if not via a display 
refinement then where/how)?

It would make it easier for me each time I have to merge my sources 
with yours ;-)

well, I just have these functions f1-handler: does []

and just redefine them when I need to use them.

ie. stubs

f10 is inaccessible though

it appears to be trapped by windows

So they reside in the global name space, or do you define them within 
ctx-rebgui?

global name space

but one could put them into ctx-rebgui

F1 - F12? Do you have a sample of the code you've had to add back?

I just had this

in process-keystroke

			#" " [
				;	do button action on SPC
				if all [view*/focal-face view*/focal-face/type = 'button][
					view*/focal-face/action view*/focal-face
				]
			]
			
			;; GC function key handlers
			f1 [f1-handler]
			f2 [f2-handler]
			f3 [f3-handler]
			f4 [f4-handler]
			f5 [f5-handler]
			f6 [f6-handler]
			f7 [f7-handler]
			f8 [f8-handler]
			f9 [f9-handler]
			f10 [f10-handler]
			f11 [f11-handler]
			f12 [f12-handler]

BTW, in chat.r, in a multi line text message, the blue divider cuts 
across the first line of text

It fixes when you risize

resize

If there is a lot of text, it won't display all the text in a message

It preserves the formatting of the original size and needs to reflow 
the text

Got it. I've been thinking that the following accessors would probably 
cover most usage cases:

	add-message
	add-message/top
	delete-message
	delete-message/top
	set-user-color
	set-message-color
	redraw

edit-message ??

sometimes one has to do these things !!

Do you mean change-message (i.e. replace message 24 of 50 with the 
following ...)

yes

So a 'set-message-text accessor?

yes

http://www.compkarori.com/reb/chatlo.png