World: r3wp

Yeah, a sdk 2.7.5 issue.

This seems to work in lInux.  In display.r, change

							find [f1 f2 f3 f4 f5 f6 f7 f8 f9 f10 f11 f12] event/key
to 

       find [ console listen tcp udp icmp dns local odbc oracle mysql crypt 
       compress ] event/key

and redefine on-fkey in rebgui-ctx.r

	on-fkey: make object! [

   console: listen: tcp: udp: icmp: dns: local: odbc: oracle: mysql: 
   crypt: compress: none
	]

so that function keys work in 2.7.5

Any possibility of getting 2-state checkboxes and groups?

Uploaded build#102 with 'bistate option for check and check-group. 
Option disables right-click state selection.

Ooh, I thought 101 was the latest release. Been away for a while

HI, I'm new to Rebgui. Is it possible to use Draw or AGG in Rebgui 
personnal widgets ?

Yes, no problem.

Ok but when i Try a simple example I receive an error :

REBOL []

do %rebgui.r

append-widget make rebface [ draw [
            pen yellow
            line 20x20 80x80
        ]

** Script Error: draw expected image argument of type: image pair
** Near: draw [
    pen yellow
    line 20x20 80x80
]

Is it possible to use drag'n'drop in Regui ?

append-widget [
	my-widget: make rebface [
		effect: [draw [pen yellow line 20x20 80x80]]
	]
]

Cool & simple !

Drag'n'drop support is not 'built-in' as such ... you have to add 
/ code it on a widget by widget basis.

ok

I try to use RebGui with Q-Plot but the plot is in a separate window 
instead of to be inserted intto rebgui  display.

do %rebgui.r
do %q-plot.r
   
append-widget [ 
    plot-widget: make rebface[                             
    view quick-plot [
        300x300
        fill-pen blue
        pen red
        bar-width 15
        bars [5 3 8 2 10 3 4 9 5 7]
        label "Meaningless bars"
        y-axis 9
        ]
        
    ]
]    
                                                 
display "Plot 1" [

                group-box "Graphique" data [plot-widget]                      
                 ]
do-events

I'm having some trouble that I was hoping you could help me with.. 
again :)


I want to have a tab in a tab-panel that contains some kind of group 
block and a button. Every time the button is pressed the group block's 
contents should change to a new, dynamically generated, GUI block.


It works up to the part where the button is pressed, but the group 
block is never changed.

I can add that the dynamically generated GUI consists of a mixture 
of texts, fields and another button. When that button is pressed 
all fields are evaluated and possibly modified.

I found the solution by myself :

pane: reduce [                             
     quick-plot [
        300x300
        fill-pen blue
        pen red
        bar-width 15
        bars [5 3 8 2 10 3 4 9 5 7]
        label "Meaningless bars"
        y-axis 9
        ]             
      ]

remove the" view" command & add a reduce command

Ashley, I just tried the 'bistate option from 1.12 and am not sure 
that it works properly. I can toggle between green checkmark and 
blank box via left MB (and the red cross via the right MB has become 
unreachable).  I would have now expected the blank state to replace 
the off state but apparently it still does stand for NONE and displaying 
a CB in False state still shows the red cross......?

A null selection in [default] tri-state mode is none! and I didn't 
want to confuse the issue by changing it to false in bi-state (even 
though taken in isolation that would be logical, pardon the pun). 
The bi-state option merely disables the RMB action, it doesn't change 
how or what data you pre-populate with.


If enough folks want it I can make the widget a pure bi-state affair 
that returns true and false (I no longer need the tri-state functionality) 
... but that may break exisitng apps that either depend on the functionality 
or expect none!

Let us know if you do so I can fix my apps

Using Linux, I don't see the characters I expect with the fast forward, 
rewind etc ...  I guess due to the different fonts involved.  Is 
there a work round?

Or a symbol font we can sub.

I have a problem, possibly a bug, with the following code. If I press 
start, I get a popup window. Both these can be closed as expected. 
It also works if I press the next button - popup nr 1 is replaced 
by nr 2. Again, both windows can be closed as normal. However, if 
I press next twice and close both windows then Rebol seems be be 
stuck in do-events and the program never terminates.

print "bugz"
do %script/rebgui.r

maingui: [
	text "Hello" return
	button "Start!" [ display-next-word	]
]

count: 0

secondgui: does [
	compose [
		text (join "popup nr " count: count + 1) return
		button "next" [ display-next-word ]
	]
]

display-next-word: make function! [] [
	hide-popup
	display/dialog "Go!" secondgui
]

display "word!" maingui
do-events
halt

Think I've found a bug.. If have a button that does some stuff and 
then hides itself. Works great if I click it, but if I select it 
with tab, press space and then tab again the button will reappear.

Hello.  Sorry for the huge number of questions I ask  ^^

Is it possible to move a widget within a display block ?

for example, transform: display "MyFace" [
               box red               
               box blue               
           ]

to:   display "MyFace" [              
               box blue               
           ]

(sorry, it's a mistake)

to: 
display "MyFace" [
               box blue       
               box red                                       
           ]

by clicking on a button by example

Daniel; Check out http://www.rebol.org/cgi-bin/cgiwrap/rebol/view-script.r?script=layout-1.8.r
for a what you see is kinda what you get layout editor.   The tricks 
will be buried in the code, but it has to do with ordering the face/pane 
entries.  Also see http://rebol.com/docs/view-system.html#section-3
for a description of face/pane.

My bad.  Just noticed this is RebGUI ...  although the same principles 
apply.

I think display should always return a value.

>> do %rebgui.r
Script: "Untitled" (none)
>> test: display "Test" [ text "Hello" ]
>> test: display "Test" [ text "Hello" ]
** Script Error: test needs a value
** Near: test: display "Test" [text "Hello"]
>>

In the second instance, display picks up the window already exists, 
and just exits without returning a value.  Perhaps it should return 
none instead ?

foreach window view*/screen-face/pane [all [title = window/text exit]]

perhaps change to 


foreach window view*/screen-face/pane [if  title = window/text [ 
return none]]

Actually this has been a source of a long standing bug ... I didn't 
realize till now that the return behaviour differed.

bug for me ...

returning none! is better than returning unset! so changed in next 
build as above.

display "" [ area 100x100 options [ info ] on-click [ print "You 
clicked me"]] do-events

- the area does not respond to the on-click action whereas


view layout [ info 40x40 [ print "You clicked me" ]] works fine in 
VID

display "" [ button "Test2" [ display/parent "Test2" [ text "test2" 
button "close" [ unview/only face/parent-face ]]]

button "Test3" [ display/parent "test3" [ text "test3" button "close" 
[ unview/only face/parent-face ]]] button "Halt" [
unview/all ]] do-events

click on "test2" and then click on "test3".  Now close down the test2 
window and the test3 window also closes down.

Now click on the "test3" button ... nothing happens ... I guess it 
thinks that the test3 window is still open.

Did 2.7.6 break tooltips, or did I manage to screw up my program 
without noticing?