World: r3wp

Hello, everyone... Ii am using encryption in Rebol/SDK, and I would 
like to store the actual binary value returned from the port as a 
string... not the to-string value, but the binary value... for example, 
if I get back #{455121D505CD240595E530589ADCD7787F22EF9DE899D6D8} 
from the port, I would like to store 455121D505CD240595E530589ADCD7787F22EF9DE899D6D8 
as a string in a file... does anyone know if this is possible?

enbase/base #{...} 16

sweet!  thank you very much

Thanks Kru! I'm editing it now.

Hey all, what is the current expected syntax for the Needs header 
of a REBOL script?

Last time I checked (a while ago) it was undocumented.

needs: 'rebol

There is some way of specifying the Core and View versions, I remember, 
but don't remember how.

I would suggest that is probably like the tested-under block

viz: needs: [ core tuple! view tuple! ]

Some examples here:
http://www.rebol.net/notes/rv13-changes.html
eg  needs: [view 1.3.0 sound 1.2.4]

Thanks! I'm currently testing my script compression code to see what 
the minimum versions of REBOL it needs.

i am testing version 2.0.1 of RebDB, and I am having problems doing 
a selection with an equality 'where' predicate... 
do %db.r
if any [ exists? %my-table.ctl 
         exists? %my-table.dat ] 
       [ delete/any %my-table* ]
db-create my-table [col1 col2 col3 col4 col5]
db-insert my-table [next "1" "2" "3" "4"]
db-commit my-table
test: db-select/where * my-table 1
print ["key: " test] 
test: db-select/where * my-table 
	'col1= 1 'col2= "1" 'col2= "2"
print ["eq:  " test]
test: db-select/where * my-table 
	all ['col1= 1 'col2= "1" 'col2= "2"]
print ["eq:  " test]
test: db-select/where * my-table 
	[all ['col1= 1 'col2= "1" 'col2= "2"]]
print ["eq:  " test]

can anyone tell me what i am doing wrong in this test?  tia

The where refinement expects a block, so just use code like the following:

	db-select/where * my-table [col1 = 1]
	db-select/where * my-table [all [col1 = 1 col2 = "1"]]

Could you help me anybody? I have a simple sequences of commands: 
  view layout [label "hello"]  tx: request-text "something" ... I 
need invoke request-text immediately after main window showed - not 
after the main window is closed...

view/new instead of view

what an easy solution :-)  Thank you!

I thought, that view/new i can use only if i  allready have the other 
window.. (sorry for my english..)

are you looking for DO-EVENTS ?

whoops, seems you are not, but VIEW/NEW and DO-EVENTS usually go 
hand in hand with the first opened window

So if i use view layout [.....] it is as some as if i use: view/new 
layout [....] do-events ?

correct, and between VIEW/NEW and DO-EVENTS, you can do initialization 
stuff after showing the window

you can also, if you have a console running in the background, restart 
a "stopped" view window with DO-EVENTS

great, that i needed, thanks a lot for explanation..

excuse me i can not undertand this my example:

I can not understand behaviour of my example:
If i have a script1.r:
view layout [ ...
  btn "script2" [
    do %script2.r      
    print 123
  ]
]
... and sript2.r has: view layout [.....]
I expected that <print 123> will not execute because 
script2 has view layout... (no view/new layout [...])

but <print 123> will execute ...

view does not wait if there's another view waiting already.

thanks..

Bobik, looks like you want to make a script launcher. See if you 
can use LAUNCH to run your script. (limited to one level though.)

uuoop, i don't know this command :-)

thanks..

so i'm testing this now :-)

Gabriele - in Bobik's example - has it anything in common with waiting 
actually?

rebol has not tasking. So I wonder how is that once you execute %script2.r, 
print 123 is printed

ah, maybe now I understand .... :-)

source view :-)

one almost starts to think, that there might be some multitasking 
involved :-)

btw - Gabriele - you are the author of modal system update for 1.3? 
Not sure it ever worked, but Graham said so, it is in RAMBO already 
- but - using show-popup, should we be able to get modal window?

.... as with 1.3, when you use dialog boxes (alerts for eg), you 
can click background window ...

modal, yes. always-on-top, no (that needs native support)

modal? How - it was one of bobik's earlier questions, we tried a 
lot, but nothing worked for us ...

use inform instead of view

as for always-on-top or other modes of Windows, it is a pity we don't 
have them. It is just one single function call, which even C lamer 
as me was able to wrap ;-) ShowWindow or ShowWindowPos

it does not seem to work:

view layout [btn "So what?" [inform layout [text "So what?"]]]

I can get to underlying window ...

you can get to it, but it ignores events. again, always-on-top needs 
native support, there's nothing we can do about it.

aha .... it is a bit tricky, because you can get-to-it, exactly as 
you said - so it does not receive events, but it can get focus, so 
your dialog-box may go under the initial window and user might think 
app is blocked ...

hopefully the parent option will be made to work again.

one trick might be to check regularly if the modal window is on top, 
and if not, bring it on top.