World: r3wp

or 

at 50x20 #H to indicate vertical resizing ?

First problem is fixed easily enough:


 display "" [ area 50x20 #WH slider 5x20 #XH data [arrows]]	; note 
 the #X directive

Not sure what the second issue is as:


 display "" [at 20x20 area 50x20 #WH slider 5x20 #XH data [arrows]]

seems to work well enough.

but not if u do this 


display "" [at 20x20 area 50x20 #WH slider 5x20 #XH data [arrows] 
at 20x5
0 area 50x5 #WH ] do-events

#X directive noted .. thanks.

And #Y directive seems to fix my other problems :)

Not so much an absolute positioning problem as a by-product of RebGUI's 
simplistic resizing model. Compare:

	display "" [field #WH field #WH return field #WH field #WH]

with:

	display "" [field #H field #WH return field #Y field #YW]


This limitation is by design so won't be changing any time soon (I 
tend to design GUIs that conform to it naturally ... but that may 
be just me ;) )

In this example I can't get vertical positioning working 

display "" [  
    at 0x150
    

    text-list 30x15 #YH data [ "Joe" "Adam" "Bill" "Artur" "Phil" "Simone" 
    ] [ show-text chattofld pick face/data first face/picked ]

        chatarea: area 150x10 #YWH "Intra office chat appears here" slider 
        5x10 #YXH data [arrows]
 
    at 32x160
    chattofld: field 15 #Y chatfld: field 140 #YW [ 

            show-text chatarea rejoin [ chatarea/text newline chattofld/text 
            ": " chatfld/text] 
            show-text chatfld "" rebfocus chatfld
    ]

    ] do-events

neat. got my very simple gui app working in View, and I'm suddenly 
overwhelmed by the urge to try it with RebGUI instead.

How do I right-align the text in a field?

right

field font [align: 'right]
should work

perfect, thanks

Graham, best you can do is remove #Y directive from first 3 widgets. 
To make things even clearer, revert the span-resize function to its 
pre-0.3.4 definition (i.e. replace the following:

			;	protect against negative sizes
			if find face/span #"W" [
				...
			]
			if find face/span #"H" [
				...
			]

with:

			if find face/span #"W" [face/size/x: face/size/x + delta/x]
			if find face/span #"H" [face/size/y: face/size/y + delta/y]

in %rebgui.r (as has been done in the next build).

ok.

I've got to keep the #Y as otherwise the top three widgets don't 
move down on resizing ( there are widgets not shown above them ).

that change doesn't seem to have helped :(

Oh, and how do I scroll the text in the chatarea using the slider?

The area widget, like text-list, should have a slider that appears 
as needed. Hope to have that in the next build.

Ok.

The action associated with the first tab of a tab-panel does not 
fire when first viewed ... wonder if that should be the case.

Is there a way to alter the spacing vertically in a check-group? 
 It doesn't respond to space nxn ...

Do group-boxes resize?

No, but they should.

Latest build available at: http://www.dobeash.com/files/RebGUI-035.zip

Issue log: http://www.dobeash.com/it/rebgui/issues.html


*** Unzip this file into your existing RebGUI 0.3.0 distribution. 
Requires View 1.3.1 ***

Highlights include:


 - generic face-iterator function shared by all lists (text-list, 
 table, edit-list & drop-list)

 - new improved table widget finally supporting row (including multiple) 
 selection

 - updated drop-list & edit-list widgets (defocusing support still 
 limited though)
	- area widget now sports a slider by default

 - resizing code (supporting negative sizes) reverted to pre-0.3.4

 - IMPORTANT: resizeable windows that don't have min-size specified 
 are automatically assigned one the same as the original window size
	- Various multi-row text selection issues resolved
	- Various focus issues resolved
	- numerous other minor bug fixes and coding improvements

In the works

	- basic menu widget
	- revamped documentation 
	- stabilize existing code-base for 0.4.0 beta release

note that show-focus replaces rebfocus

Page up, down, and cursor keys do not scroll text within an area.

Great news on the table selection .. must try that out.

I want to scroll the pane within a tab panel.  It's the 7th tab. 
 I can find the tab itself

tp2/pane/8/offset/x: 

but what is the path to the panel face ?

Something like this:

display "" [
	t: tab-panel data ["A" [field] "b" [field]]
	return
	button "<" [t/pane/1/offset/x: t/pane/1/offset/x - 10 show t]
	button ">" [t/pane/1/offset/x: t/pane/1/offset/x + 10 show t]
]

Ahh.. it's the first pane in the main pane.

On reflection, I think I want to actually scroll the contents of 
that pane, and not that pane itself.

I've got about 80 check boxes on one tab panel scattered through 
a number of group checkboxes ... need to clear them in one hit. 
Need some way to run thru all the checkboxes and reset them.

Perhaps the 'clear-text accessor function can generalised to a clear-face 
function ?

display "Test" [

 c: check-group 30x15 data ["Item 1" true "Item 2" false "Item 3" 
 none]
	button [foreach item c/pane [item/data: true] show c]
]

if item/style = 'check [...]

oops, sorry, non-VID..

if widget/type = 'check-group [...]

Graham, I think a clear-widget accessor (with a "/default value" 
refinement) would make a good addition.

What do feel about adding a right mb click to tables ?  Just thinking 
of way to remove items from tables.

Sounds reasonable. What about a double-click action as well? I was 
thinking of expanding the layout parsing rules such that *any* widget 
could be specified as:


 widget [default left-click action] [default right-click action] [default 
 double-click action]

but I'm not sure whether this is overkill or not.

choice is good... already have tristate widgets :)

It also means we have a cleaner screen .. fewer widgets to clutter 
it up to do the things we need to do with tables ie. add, remove, 
elements

Another wish for tables .. a way to set the colour of a row, which 
is controlled programmatically.  So, you might have a table of messages 
in your inbox, some of which you have read ( one colour ), and those 
to be read ( another colour ).

Ashley, good idea. As long as the later two are optional.

display "" [ p: password return button "Login" [ if empty? p/text 
[ show-focus p ]] do [ show-focus p ] ] do
-events


if you tab out of the password field, and then activate the button 
with the spacebar, the password field fills with one character.

tabbing does not seem to work between fields in a modal window.

the docs says that display has a /layout refinement, but it doesn't.

Looks like the layout is not parsed correctly when you specify a 
modal layout with /dialog

Retract that last statement.

Should <CR> act the same way as tab in shifting focus ?
Should tab also fire an action associated with a field ?