World: r3wp

Any simple way to set a "field", or better serie of fields with the 
same style,  to  read-only  at  runtime?

and later back to writable off course?

off=of :(

enable-fields: func [pane][

    foreach face pane [if face/style = 'field [face/feel: ctx-text/edit]]
]
disable-fields: func [pane][
    unfocus
    foreach face pane [if face/style = 'field [face/feel: none]]
]
view lay: layout [
    field field field guide
    btn "Enable" [enable-fields lay/pane] return
    btn "Disable" [disable-fields lay/pane]
]

Thanks,  just what I needed

I discover today GUI4CLI language http://users.hol.gr/~dck/g4c/

Why not base REBOL/view widgets on GUI4CLI widgets maybe to save 
time it will be easyier to make the same kind of integration in this 
topic that it has been done for AGG integration

shadwolf:you using the Amiga or pc version?

windows version

Rolf, you may also want to consider allowing the text to selected 
for copy/paste actions when the fields are not active.  This can 
be done by simply setting FACE/FEEL to CTX-TEXT/SWIPE instead of 
setting it to NONE...

Thanks,  I still cannot find the view system really simple and/or 
well documented.

it does help to look at examples which others have done that work 
well and customize them.  Some of the more detailed scripts are in 
the IOS collection.

Have you sorted through the plugin examples?

Plugin sound advanced, so I did not examine,  I just started Rebol 
a month ago.

My programming style has yet  not adapted the Rebol style. It still 
feels like translating directly from procedural languages.
But I'll check the plugins.

the plugin examples are mostly just View scripts, which run, but 
you can see them in the Web browser. The examples have source with 
them....but maybe all of them are using just plain View code.

http://www.rebol.net/plugin/demos/index.htmllike these

I see,  for the webbrowser plugin. Back to IE.   No I'll check them 
in Rebol/View

Great,  an object browser
http://www.rebol.net/plugin/demos/anamonitor.html

Nice one, Ammon. That's an often-needed function worthy of writing 
down.

Just remember CTX-TEXT ...  That's the object in which all of VID's 
text handling is contained...

Rolf ---- The plugin also runs under Firefox -- but you'll need the 
instructions:

http://www.rebol.org/cgi-bin/cgiwrap/rebol/ml-display-message.r?m=rmlNRHC

I'm just giving those instructions a go now, using Firefox 1.0

----> moving to "plugin" group to discuss further...

Many changes occured on /View during 2004 and that's very good after 
a long period with no updates. What about 2005 now? How far is RT 
from an official cross plateform /View ? What will trigger the next 
new release?

Interesting question -what will trigger it? We now will have - newer 
GC, async core, AGG beta soon ... so what will come next? Maybe something 
from following stuff? - rif, rebin, plug-ins, rebservices? But only 
Carl knows his priorities ....

he has published them to us to read.

Is 'load allowed to modify source data? In all /View with sound support 
(on Windows,) when you do:
my-sound: read/binary %my-sound.wav
snd: load my-sound

'my-sound is modified! So successive 'load will return samples with 
bad data

Steve - what has Carl published?

snd: load copy my-sound

which is what I had to do to circumvent this problem.

Graham: yes, it's what I did after searching why all my riff-waves 
has unsigned big'endian data :-) 
- but is it a bug - or a documentation problem?

I've got one event that I am processing for timer events, and I want 
to start up another that shows a time elapsed.  But it seems I can't 
have both going at once ?

rebol []

newtimer: does [
	inform layout [
		timer2: info "00:00:00" 60 font [] rate 1 feel [
			engage: func [face action event] [
				if action = 'time [
					timer2/text: now/time
					show timer2
				]
			]
		]
	]
]

view layout [
	timer1: info "00:00:00" 60 font [] rate 1 feel [
		engage: func [face action event] [
			if action = 'time [
				timer1/text: now/time
				show timer1
			]
		]
	]
	button "New timer" [newtimer]
]

Both timers freeze when I inform the new layout.

when I close the new layout, the original timer restarts

Is that a bug, or just a by product of the way 'inform works?

If I change the button action to

	button "New timer" [timer1/rate: none show timer1 newtimer]

then the new timer starts up ...

Vincent, I'd say that's a bug. I also found just playing different 
sounds (inserting different sounds that were only loaded once each), 
that the audio format would change randomly ! 8-bit <-> 16-bit, 22.05kHz 
<-> 44.1kHz etc... and the sound quality eventually degrades, obviously.

Graham, I'd say that's a problem of the inform system. Check out 
Romano's INFORM patch and WAKE-EVENT patch.

why aren't those in latest alphas then?

dunno

Graham, you might have to additionally patch INFORM so that it calls 
SHOW-POPUP/AWAY (adding the refinement), because (from my notes):

SHOW-POPUP:

 There are 4 types of modal windows: plain, /window, /away, /window/away
	/window  - puts popup inside pane of an existing window

 /away    - allow handling of events of other faces than the popup 
 face eg. [time inactive key] in Romano's patch

(actually I think Romano mainly wrote that originally).

Pekr, those patches still have issues to be dealt with; they are 
very complex, affect a lot of things, and do not have a lot of discussion.

/away must be used for menu like popup

/window open a new window

/window/away is a window which behaves like a menu (disappears when 
user click outside)

any thoughts on Graham'

s timer inside a layout problem, above ?