World: r4wp

Let me simplify:

REBOL []
print "ok"
print system/script/args
ask "test"


When I encap this script and run with a parameter like "-cxx" it 
doesn't print ANYTHING.

no "ok" no "test" nothing. BUT when I WRITE system/script/args to 
a file it looks it is there.

REBOL []
print "ok"

write %test.txt system/script/args ;there is "-cxx" in test.txt file.

yes I tried both "options" and "script", same result.

It's very weird, so we don't have a chance to use a parameter starting 
with -c (and many other) in our encapped executables.

More simplified, encap following script, run it with -c, -w or --sec, 
it prints nothing. Run it with -i, -t, -? it prints "ok".
REBOL [] print "ok" halt

Might be a bug where encapped REBOL tries to consume its own command-line 
options (while it shouldn't).

It looks like. I thought that it confusing with REBOL's own command-line 
parameters but it happens only for some of them not for all. So no 
chance to use *some* parameters.

Aha PRINT and PROBE doesn't work in encapped executable if command-line 
parameter includes a "c" character.

Any "c" character? I guess then that I was very lucky with Cheyenne: 
http://cheyenne-server.org/wiki/Main/Command
:-)

Definitely!! But we should keep that in mind.

-c means cgi ==> So not ouput to the console

Endo, when you are using set-words with MAP-EACH and R3's FOREACH, 
be sure to include at least one regular word, or it won't advance 
and you'll get an endless loop. We made that possible in order to 
support the foreach [x:] data [... take x ...] code pattern. It's 
the type of thing that would generate a warning in other languages, 
but REBOL is inherently incompatible with warnings.

BrianH: Yes I realized that at least one word is required.

sqlab: I encap a script and run the executable, so I should able 
to use any command line parameter. And I don't encap with cgi option. 
Also -w parameter has no such a problem (which is "no-window option 
for REBOL)

Anything that include "c" char prevents to print/probe to the console.

On the other hand it doesn't prevent opening console window. I see 
"** Press enter to quit" message when program HALTed but PRINTs don't 
output anything.

this works, the other two do not

 system/schemes/default/timeout: 0:01:10
 ;system/schemes/http/timeout: 0:01:10
;system/schemes/https/timeout: 0:01:10

Confirmed.
Even system/schemes/default/timeout: none

A beginners question. I have some code that allows a user to input 
a date or leave it blank;

datetime: field

I get the data by accessing;

datetime/text


My question is, if the user leaves the field empty, how do I test 
for this? I have tried none? And empty?

If none? datetime/text [print "Select a date"]


produces a Script Error: 'datetime has no value'. How do I test if 
datetime/text is null so I can ask the user to go back and fill in 
the datetime field?

a one liner:

until [  view layout [fld: field]    not empty? fld/text ]

You seem to be trying to access datetime outside the VID context, 
where it is not defined

here, the field's action compares the field when pressing tab/enter, 
and will close the window when its not empty.


until [view layout [fld: field [unless empty? face/text [unview]]] 
not empty? fld/text]

not that within an action func, you can use  'FACE  to refer to the 
control triggering the action.

not => note

Maxim thanks for the code. I'll experiment.

Kaj, I think you are right. I'll check to see if that is what's hapening.

you get that vid error because you are referring to it before the 
layout function has run.

GrahamC, It was simpler than that. The program I am working on has 
over 1300 lines of code, and I mis-typed a variable name! So it turns 
out I was trying to access a word that did not exist, was not defined. 
I'll remember that for next time. (Yes, there will be a next time). 
Thanks for all the help. I am beginning to feel competent programming 
in Rebol2.

Caelem, D'oh moments are possible in any language.
I once wrote
    return: true
rather than
    return true

The protracted debug session that followed taught me the value of 
protect-system.

Hi I am trying to replicate this in Rebol: http://www.alistapart.com/articles/succeed/
I have the redirect setup but I want to know what url the user entered. 
Where can I get $DOCUMENT_ROOT.$REQUEST_URI ??

If you are using REBOL in CGI mode:

    get-env "DOCUMENT_ROOT"
    get-env  "REQUEST_URI"

Thank you, this works! I found and old conversation on ALTME this 
afternoon but that could not convince me being the answer, this answer 
will replace the old one. (I even typed get_env the first time). 
And for completeness I will write how to use it (cut and paste code) 
requestedurl: get-env "REQUEST_URI"

And the next step get-env "SCRIPT_FILENAME" 
guess I will have to post the complete script when I finish it.

These values are already processed by REBOL when it is started in 
CGI mode. I'm using
	cgi: system/options/cgi
The request URI is then in cgi/path-info

The script name is in cgi/script-name or something like that

Hi Kaj, wish it was that simple. I have put some strings into action 
and you can view the result here http://arnoldvanhofwegen.com/rebol/doesnotexist.html
Well as you can see path-info is none.

The script name is the script name of the script that is being executed, 
I knew that one already I redirected to it, not the requested page.

Ah, so REBOL does follow the major rule of other software: it does 
everything except the thing you need

Found some code/documentation about playing a sound (wav) on www.rebol.com/docs/sound.html 
 

but although rebol/view 2.7.8 (Win XP) has Sound 1.4.0 on board it 
seems using the sound:// port is reserved for use by the SDK version? 
** Access Error: Cannot open sound
** Where: halt-view
** Near: sound-port: open sound://
on MacOSX I get
** Access Error: Invalid port spec: sound://
** Where: halt-view
** Near: sound-port: open sound://

But that is less surprising since there is no Sound module available 
there.
So what is Sound (1.4.0) about?

Kaj is right again

Sound in REBOL is primitive, but I thought it had been in the free 
versions for many years

Did you initialise events like the doc says?

could be a rights issue? That the port may not be freely accessible.

That was a long time ago, and it should say "Feature not available 
in this REBOL"

Arnold, I've been using sound in a recent app with 2.7.8.3.1 with 
no issues (on XP too). I use a version of Nick's code http://musiclessonz.com/rebol_tutorial.html.
Look for "play-sound"

this works for me on free version of View: (XP)

sound-port: open sound://
play: func [file] [
 wait sound-port
 clear sound-port
 insert sound-port file
 wait sound-port
]

yes enabled in View. not core (like all /pro features) .

Ah, is that the problem again. Sigh

An answer in a not web public group -> Chit chat

Somehow indeed I managed to mix up core and view console so sound 
did work afterall. Sorry for the noise :( 
But still a wish for sound in REBOL on other platforms.

in R3 we can add sound support via the host-kit, but its not as good 
as it could be because we cannot add devices and/or any new type 
of event to easily (asynchronously) signal audio-related events.

Devices cannot be added?

Not at the moment, as far as we know. At least if there's a workaround 
noone has figured it out yet. You can signal asynchronous events 
with callbacks though, afaik.

I never realised, because I only looked at them in the C code. I 
suppose devices can be added there, but not yet afterwards from REBOL