World: r3wp

I wonder if it's because I use ":" at the end of my labels

That would be it. "Name:" <> "Name"

Hmm. Screws it up.

words: [
Occupation:
 "Occ:"
	"Bytes"			"Octets"
	"Cancel"		"Annuler"

Instead of "Occ:" the label is now showing "Bytes"

Probably because you don't have a space between "Occupation:" and 
 "Occ:"

I do ..

one space and two tabs

just added those to be sure.

just tried it with other words . it causes the locale to skip the 
following word

for me anyway

Reproduced it, very odd. Looking at it now ...


re dynamic translations. Reading Gabriele's comments in the chat 
group on his TRANSLATE func got me to thinking we could do something 
similar, as in:

	display "Test" [
		button "Old Text" [face/text: translate "New Text" show face]
	]


'translate would return a string translation if passed a string, 
otherwise a block of translated strings if passed a block.

why not just show-translate instead of show-text ?

or, show-text translate "sometext"

show-text widget translate "sometext"

Yep, that's how it works The important point in the example I posted 
was not that it didn't use show-text, but that it is a func that 
is called to explicitly translate string(s) used by other function(s).

For your label problem, how many words are defined:

	...
	button [print length? ctx-rebgui/locale*/words]

Seems to me you might as well put the translate inside show-text

64

even !

hmm.  retract that ... regarding show-text

hmm ... retract my being able to reproduce the problem. Change your 
locale.dat file to have the following:

words: [
	"AA:"	"A:"
	"BB:"	"B:"
]

and verify labels "AA:" and "BB:" are translated correctly.

AA: gives me BB:

Really? Even with code as simple as:

	display "Test" [label "AA:"]


The code that does the translations is nothing more than a simple 
select, which you can run manually by adding a halt to your code 
and doing the following from the console:

	select ctx-rebgui/locale*/words "AA:"

It's not the ":" .. all my labels are doing this.

I get "A:"

but BB: as the label!

well, this is very puzzling.

Maybe it is something to do with the build# after all. I'm running 
on build#46 here.

Oh well ...

In the above example it is vey important that the label was "AA:" 
not "A:" (which would explain a "BB:" result returned by select)

personalgb: group-box "Personal" 77x35 data [  
    label "AA:" ethnicfld: edit-list 50 "Caucasian" 
data [

Build 46 works okay.

Nailed it ... you can reproduce the error with:

	display "Test" [
		label "AA:"
		group-box "Test" data [label "AA:"]
	]


The block handling code seems to be the culprit ... investigating.

Whew! :)

Build#47 committed to SVN, fixes locale bug and adds new translate 
function as described above.

Regarding 'put-input, I don't think you should report an error if 
there is insufficient data ...

this is with build 47

display "" [ r: radio-group data [ "M" "F" ] button "M" [ r/select-item 
1 ] button "F" [ r/select-item 2 ] button "
Probe" [ probe r/selected] ] do-events

note that whatever the state of the radio-button, the selected value 
is always none, and the radio buttons are not mutually exclusive 
:(

The values are only 1 and 2 if the mouse is used to select the radio 
buttons

Build#48 committed to SVN, incorporating Robert's/Cyphre's extensive 
changes ((including new chart, drop-tree, grid, input-grid & panel 
widgets). Panel & Input-Grid added to %tour.r.


These new widgets (apart from panel) have an impressive range of 
options/features ... but scant documentation or usage examples. If 
Robert/Cyphre could post a few examples here that would help. If 
anyone reads the source code and figures something out then an entry 
or two here would be appreciated: http://trac.geekisp.com/rebgui/wiki/WidgetList

could there be a package produced from #48?

I'm going to hack in some notes/docs on the web-page. (As I'm currently 
using our changelog as documentation, and it's way to much these 
days.).

Ashley, did you incorporated all changes or are there are some left 
out?

the grid released is version of grid Cyphre did for me?

no, it's something different. I write some docs for it.

I am just curious if those two grids overlap in functionality?

that would be unnecessary waste of Cyphre's dev resources imo ....

It doesn't.