World: r3wp

which stops the crash.

OK, back on board now.

Wow, took you 3 days to read down this far ?  ;)

Plus every other group! ;)

Updated issues log with all issues raised since 0.3.7.

Let me read and see if any are missed ..

You're missing all the problems with the area widget .. or rather 
the editor.

oops .. looking at closed issues.

Wishfull thinking ;)

Added Czech dictionary file (see http://www.dobeash.com/it/rebgui/roadmap.html) 
and dat files provided by Bobik (see http://www.dobeash.com/files/CzechWin.dat
and http://www.dobeash.com/files/CzechLinux.datfor different char 
encodings - win-1250 & ISO-8859-2 respectively).

by 51, I mean that the drop list does not display below the boundary 
of a group box

Fixed in next update.

I altered display to return the layout rather than no return value

Also, I don't think there's a way to set the window options viz no-border

Is the group-box a functional grouping?  I'd prefer that tabbing 
moves to the next group box and not recycle within the same group

I use the group box as a visual container and not a functional one

In a radio group, if you preset a value eg data [ 1 "M" "F" ], the 
radio/data is none, whereas it should be 1.

Hmm.  Works in my test .. just not in my program :(

1) display mod - just by adding "view-face" at the end of the function 
I presume? Does that give you what you need? (I was thinking of adding 
a "no-show" type refinement for folks who wanted display to return 
a face *without* doing a view - to-image being the main usage case)


2) Window options - needing to set these implies a new widget is 
required or you need more control than RebGUI was designed for


3) Group-box is a functional grouping, tabbing between widgets within 
the same group-box is normal behaviour - what is missing is *another* 
mechanism to tab into and out of group boxes

1. yes.

shadwolf - is your list-view widget (v0.52) ready for me to merge 
into 0.3.8 or should I wait until it's 100%?

Having view-face returned means I can create an image of the layout 
with to-image.

How can I set the title of an existing window ?

show-title

which requires a face object

So, how to find face object ?

You need the view-face returned by display/

This is what i am doing to fill a form up from data

display "" [ r: radio-group 30 data [ "M" "F" ] return
button "Value" [ print r/data ]
do [	r/pane/2/feel/engage r/pane/2 'down none ]
] do-events

print r/data gives none instead of 2

Ok, I can set r/data: 2 at the same time.

1) show-title

	display "a" [button 200 [show-title face/parent-face "b"]]

	or

	display "a" [button 200 [show-title p "b"] do [p: face]]

2) radio-group

	display "" [
		r: radio-group 30 data [2 "M" "F" ]
		return
		button "Value" [ print r/data ] 
	]

ok.

in the radio group though, I have a form already up, and I am pulling 
in data from a file to repopulate the form.

So, in the do block of the window, I am reading the data from a file, 
and then settting all the values.

Fair enough, although in that case you could also do something like:

	blk: read my-file
	display "" compose/deep [
		...
		r: radio-group 30 data [ (blk/5)  "M" "F" ] 
		...
	]

Not sure if you are looking for any inspiration or other ideas... 
here is a link to a javascript version of a pretty nice Data Grid... 
http://www.activewidgets.com/

I believe the code is downloadable as well.

r: radio-group 30 data [ (blk/5)  "M" "F" ]


Except doesn't this mean I now will need two versions of the same 
layout?  One with compose, and one without?

Is there a way to stop data wrapping inside a field, or row of a 
table - like the nowrap option for VID fields?

Only one layout needed as the compose would be within a func (i.e. 
dynamically built as opposed to static). nowrap option? Do you have 
a VID example, havn't used that VID option myself.

I think it's just 

area 200x40 nowrap

Not sure I understand what you mean about compose being within a 
func.

Perhaps you could allow this

radio "blah" data [ none "1" "2" "3" ]

to indicate no choice as an option.

currrently it creates an extra button labelled "none"

What's wrong with the current behaviour? e.g.:

	radio "blah" data [ "1" "2" "3" ]

Compose within a func:

	show-my-display: has [ blk ] [
		blk: load ...
		display "" compose/deep [
			...
		]
	]

So, what do you do if the user did not previously select an option 
in a radio group?

That  () within the data block has to be removed.

I see the problem. Perhaps radio-group should treat none and / or 
0 as "no selection" as well?

yes please.