World: r3wp

view layout [btn "search" [view/new center-face layout [h1 "results..." 
f: field] focus f]]

view layout [btn "search" [view center-face layout [h1 "results..." 
f: field do [focus f]]]]

well, don't want to have two windows, so I don't need view/new. Just 
wondering, that once I call view lay2 from lay1 and there is another 
function in button action block in lay1, it gets executed, although 
theoretically events should be in lay2 already, no?

ah, maybe it does not, sorry ...

good question. looking into layout ...

yes, it really does, just tried it ...

LAYOUT does not DO-EVENTS a second time, therefore it does not "break" 
a block of code being done by ... wake-event (I think).

view only calls do-events when there is no window visible. in your 
button action it is, so view just returns and the 'focus is executed. 
(if that was your question).

yes, exactly. So everything in button action will be executed, right?

yes.

I thought that if I have do [focus f] in lay1 and from lay2 button 
code I call view lay1, that it will be executed once again, but that 
"do" is somehow lost already ...

yes, the do-prts are only executed on building.

means on layouting. after that you have a big face and that initialisation-stuff 
is lost.

Yes, lay1 is obviously the window FACE.

does anyone has any quick effect for dialog box, when I press enter, 
and search criteria is not found in database, I don't want to display 
empty grid, but then I have user to notify, there was no search result. 
Don't want to use label, as I would have to refresh it from various 
places. Nor dialog box - so sound (is that easy to play some default 
Windows action sound?) or some few flashes of background or so :-)

if you layout again, [ view layout lay1-source ], it would be executed 
again. but if i understand right, you do just [ view lay1 ]

exactly, Volker ...

A while ago we had some fun "beeping" faces. IIRC Anton started that. 
He made an image! from some layout and played that as wave. Needs 
low memory in script, if you find a good one.

How about graying the grid with an alpha-face in front? or shall 
it show the old content?

there is no grid ... I have just search field, focused, Close and 
Search button for mouse. If something is found, new layout appears 
- a grid, plus "focused" close button, which gets you back to first 
layout ...

flashing can be done by rate. change color, rate changes color back 
and disables itself.

hmm, then using two layouts? one with grid, another with "sorry"-message?

now the only thing missing is - close window upon ESC

notify-func does not do it, and hotkey not too?

long not dealed with such events..

I remember using insert-event-func to catch it on global level ... 
I have to find it - It was somewhere on rebolforces iirc ...

sensor #"^[" [unview]

should basically work loke closing on close-button - ah, i to late 
:)

what, ESC? :-) cool!

(you'll use unview/only, or unview/all ... whatever you need)

^(esc) works too

mroe readable maybe

*more

hmm, when I call quit from lay1, I get back to lay2, instead of quitting 
:-)

Hu? And you did not redefine quit?

no ....

I will try to shorten my example ....

Volker, it playing images wasn't my idea at the time. It's cool though.

try following?

lay1: layout [f: field [view lay2] btn "Quit" [quit]]
lay2: layout [text "just a try" btn "Return" [view lay1 focus f]]

view lay1

probe :quit  ; == native

enter something in the field, press enter ... press Return on second 
dialog, press Quit on first one - instead of quitting rebol, you 
will be brought once again to lay2

you are right...

so is that a bug or what?

interesting.

its the first time i see quit not quit. IMHO a bug.

Gabriele is guru of modal system ... hey Gab, what's happening here? 
Can I twist even so short code or is that a bug? :-)

I will RAMBO it ....

looks like a bug to me. try to make the example smaller first.

smaller? :-)