World: r3wp

I think that can't be good for people with vision problems. I say 
stick to the simple old ways.

of rotating guis?

I was referring to Reichart's "hide-until-mouse-over" UI suggestion.

Oh...

Graham - you have still some problems with RebGUI non-stability?

Yes :(

but only since I incorporated Cyphre's radio-button

I seen stack overflow crashes due to infinite recursion

happens once a day now

ok, and when you remove it? goes it stable once again?

never saw it before... so haven't removed it yet.

had to make lots of changes in the source to accomodate the new way 
of getting data viz rg/picked and rg/selected

instead of get in rg 'data

what was wrong with get in rg data way? well, never mind, whatever 
.... should I ask Cyphre to look into it?

can you isolate the crash in some shorter example?

%radio-group.r ?

does it crash in all usage cases? or do you have any short code example?

IIRC Graham said on tabbing out, but hard to reproduce.

And his error-message said in "into-widget". Thats in %rebgui-edit.r 
, looks for a tabbable face and is recursive.

it's unpredictable.  Other errors in rebgui I've been able to reproduce 
with code examples.  Not this one.

A little bug is in the foreach. A pane-block can still conatin functions 
(for lists), and that is not checked.

But that should be more predictable IMHO.

and radio-button would need to usethat trick.

the smallest screen I've seen it on is with one radio-group and 2 
fields and 3 buttons

Would have to use what trick Volker?

put a function in a block in a pane.

for an iterated face.

usually the function is put in face/pane. but "face/pane: reduce[:iter-func]" 
works too AFAIK., that would crash 'into-widget because "tabbed? 
child" would now call it.

nothing fancy in my screen

but thats a theoretical possibility. the code does not look like 
it.

that's not Ashley's code ..

that was added by someone else to allow tabbing out of group-boxes

is the error always in 'into-widget ? Or could it be indirect recursion 
and we have to look somewhere else too?

its not the cvs-version?

svn..

Isn't it?

That's where i got it from.

ok. i read "its not ashleys code", thought its from somewhere else.

Yes, it is in the svn

just talking to Cyphre on icq - he will look into problem - he thinks 
there is overall problem with iterator in rebgui ... he tried to 
fix inside/outside drop-list parameter, so now it works, but in outside 
mode it looses hilite .... he will look into it, once he produces 
newer grid update for me ...

he also asks for eventual code example, if there is any, to being 
able to reproduce the problem ...

unless find [object! block!] type?/word get in face 'pane [      
       ; [che] -- An iterated faces may of course be tabbable, too. 
I don't handle this case for now, though.  

            return none                                                      
               ; [che]

        ]                                                                
               ; [che]

how does this code work?

looks in the pane and allows only object! and block!. on other things 
it returns none. especially on functions, thats why it uses 'get.

needs to be rewritten to be a non recursive function

or perhaps to pass the recursion count so it can exit gracefully...

its called from 'next-field too. That recurses too. looks a bit suspicious 
to me at first read. but then the error-m,essage should sometimes 
show it and not always bail out on 'into-widget IMHO.

the face-tree is recursive, so is the function.

and back-field

WHat looks suspicious is: it goes thru the parent-face. but it does 
not exclude the current face.