World: r3wp

I haven't found the on-fkey handler yet, but I am hoping that function 
keys are not defined at the face level.  I use function keys at the 
application level ... and modify their behaviour depending on which 
tab has focus.

do %rebgui.r
ctx-rebgui/on-fkey/f3: make function! [face] [print "Hi"]
...
display ...
...
do-events

The handlers are global, the face argument is the face of the display 
which was active when the key was pressed (see %display.r for the 
processing logic).

I tried this with no luck.

What REBOL version?

>> rebol/version
== 1.3.2.3.1

>> do %rebgui.r
Script: "Untitled" (none)

>> ctx-rebgui/on-fkey/f3: make function! [face] [print "Hi"] display 
"" [ text "hello" ] do-events

nothing happens when I have focus on the window and press f3

Works here, and I'm running the same View version.

ctx-rebgui/build?

hand built :(

A merge of my changes with your latest

checking out a new version now

BTW, would it be okay to add caret support to spinner so that we 
can change a single character?

At present we have to highlight, erase and then type over

Function keys working now :)

Must have screwed up the merge I did

You mean add the 'caret attribute to spinner?

if that is what it takes

OK. In your outcome example change the size to 1x5 and add color: 
red to see what is happening.

text (derived from label) is trying to protect you from:


 text 10 "A really long bit of text that should wrap even though I 
 didn't specify 10x-1"


but the problem is that if you specify 10x5 then it should honor 
that regardless of whether the text fits or not. The solution, I 
think, is to change the default size from -1x5 to -1x-1 but ensure 
that size/y is always a min of sizes/line.

I get a red line, which is deeper than specified

I want to hide the widget so, I really want to set it to 0x0

what about:

	text "blah" false

Hmm.  That works

Can I put that in the widget definition?

show?: false

I'm using these hidden widgets to controll the low, high range of 
acceptable values in a widget, and to provide them with database 
field names

ie.form validation and not field validation

Seems an obscure way of doing it ...

It allows a user to define a template like this:


label "Tender joint count? (0-28)" outcome "tender28" ifield  low-range 
"0" hi-range "28" return

so, outcome refers to the database field, and the user has integer 
field for the data, with a low range of  0, and a high range of 28

I guess I could use a custom widget and use options instead

or a spinner?

takes too many clicks

you have to highlight a spinner and type over it

extra work

then add spinner to hilight-on-focus and they can just type overtype 
the value directly.

I think I created this dialect pre-spinner days :)

Does a spinner allow blank field to start off with ?  Trying to avoid 
users accepting default values

Not at the moment. Should it? And if so, should it let them leave 
the widget without entering a value?

Well, I don't want to present a template with prefilled values

because then the user doesn't know which ones they filled in or not

Hmm.  Adding show?: false to the widget definition is not helping.

I guess the other reason I don't like using spinners in data entry 
forms is that it forces the user to switch from keyboard to mouse

Unless the spinner also accepts cursor keys

Agreed. It's one of the things my users have asked for (especially 
on drop-list/edit-list).

Guess my fix is going to be to add 'false to all the templates I 
have to hide the widgets in question

show?: false *should* work, haven't tracked down why not yet. Also, 
if you're going to be placing "hidden" widgets consider using box 
with a 0x0 size. This involved less processing and lets you use the 
data facet without having to "hide" the widget per sa. e.g.

	box 0x0 data "Text"

does what you want.

it would mean changing all the form processing logic which currenlty 
looks at the text facet