World: r3wp

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? :-)

ok, will remove text ;-)

wanted to ask that too.. ;) removing focus?

maybe focus is the cause? :-)

They are not modal windows. But the modal handling has changed in 
wake-event, so maybe the problem is there.

focus does that ...

in RAMBO ...

going home, later ...

cu Pekr

Type something in the box, press enter, click return - and unfocus 
the field (like clicking on the window) and it shows lay2 again - 
looks like it's just viewing lay2 when the field is unfocused - which 
is before the button is clicked, right?

good observation. when i add a 'print in the quit-button, it shows 
that action is never called. so no quit too.

When a field is dirty? and you click on another button the action 
of the field is done. This is a side effect of system/view/screen-face/feel/event-funcs/1

I did not know View 1.3 will not work with W95??? I noticed change 
of filesystem accessor function calls, but I thought those will be 
somehow called on newer systems only. Lotsa of W95 machines still 
around. I wonder if W98 is affected too?

I have found Win95 machines to be kinda rare, but 98 and 98se to 
be pretty common - 95 seems to only be used on machines without Internet 
access in my experience.

I think RT could afford to drop support for Win95

or, leave 1.2 for Win95