World: r3wp

I was looking at (and don't grasp all the implications of) the parsing 
 set-word!  occurances and how a set-path! may be inserted.  But...it 
looked too simple, so it had to be wrong.  :)  And again, I don't 
get all the implications, so I'm completely accepting of Ashley's 
nice short no.

make object! [
    code: 501
    type: 'access
    id: 'not-open
    arg1: "Port"
    arg2: none
    arg3: none

    near: [line/pane/:i/font/color: either find p/options 'no-action]
    where: 'confirm
]

face-iterator init func as it tries to create a table ... now that 
one should be reproducable?

I'm just logging errors here as they occur!

so I can add traps around them and then log them to the rebgui.log

Are these errors you're generating or your users are generating? 
I've got a dozen or so users who've been pounding away at a large 
RebGUI app for almost 2 years now, and the rebgui.log files on their 
PC's are pretty much empty. Might just be a case of YMMV ;)

these are ones I am generating :(

btiffin, maybe this works:
fields: context [a: b: c: none]

display "test" compose [(to-set-word in fields 'a) field (to-set-word 
in fields 'b) field]

Hey...that should get rid of a few more globals, cool.  Thanks Ashley. 
 First tests worked great. :)

Anton, very cool. I'll think I'll add that trick to the [RebGUI] 
cookbook.

Anton;  Yep, thanks.  This has opened up all kinds of RebGUI goodness.

well, but will it bind those variables to those one in 'fields object?

Ah it works, good :) I couldn't remember if the binding was kept 
or not.

Pekr, do you know what   in fields 'a   means ?

yes, from the help ....

I am just not sure, if the 'a in the 'display is the same as in the 
'fields ....

Check this out:
>> o1: context [a: 1]
>> o2: context [a: 200]
>> print probe compose [(in o1 'a) (in o2 'a)]
[a a]
1 200

I mean - does it create global 'a, referencing fields/a?

The only concern for me was if to-set-word kept the binding. (I guess, 
possibly, long ago it did not.)

yes, but you are creating global var anyway, no? via the set-word?

sorry ... not good at those topics :-)

No,   in object 'word   actually refers to the word that is in that 
object. :)

Try the above example, then see if 'a has a value globally.

eh .... can't believe it :-) it should translate into: display "text" 
[a: field b: field]

your above example does not use setword

No, to-set-word keeps the binding of the word (thankfully).

shit, it works :-)

o: context [a: 1]
print o/a
reduce compose [(to-set-word in o 'a) 5]    
print o/a
value? 'a

results:
1
5
false

it is just not clear, how to-set-word could bind it to o's 'a

>> blk: compose [(to-set-word in o1 'a) (to-set-word in o2 'a)]
== [a: a:]
>> get blk/1
== 1
>> get blk/2
== 200

to-set-word is not doing any binding. The word retains its binding. 
Each word knows to which context it is bound.

So, as the word travels around the place, it knows in which object 
its associated value can be found.

ah, that is like sucking 'a from object to upper context, while 'a 
still remembers, where it belongs ;-)

We should move to Core group.

Just ran RebGUI from the Desktop Demos folder:

** Script Error: yello has no value
** Where: append-message
** Near: get msg-color

yello is a new colour since....

since View1.3.2

I'm post-1.3.2, but clearly a little behind...

system/version?

1.3.61.3.1 -- works after downloading 2.7.5

1.3.61 is actually older than View 1.3.2
I've renamed mine to:
rebview1.3.061.3.1  and  rebview1.3.2.3.1
so that they sort properly, by release.

Hmm, I guess it's the same as for 1.3.50.3.1 ?

Shows how long it is since I last really used View : )

This has happened a few times now, so I might add a check for these 
misnumbered versions. Any other versions apart from 50 & 61 I need 
check for?

1.3.2?

value? 'yello

I have
rebview1.3.000.3.1.exe 
rebview1.3.001.3.1.exe 
rebview1.3.001.3.1c.exe 
rebview1.3.001.3.1d.exe 
rebview1.3.050.3.1.exe 
rebview1.3.051.3.1.exe 
rebview1.3.052.3.1.exe 
rebview1.3.060.3.1.exe 
rebview1.3.061.3.1.exe 
rebview1.3.2.3.1.exe 
rebview2.7.000.3.1.exe 
rebview2.7.001.3.1.exe 
rebview2.7.002.3.1.exe 
rebview2.7.004.3.1.exe 
rebview2.7.005.3.1.exe

The above list is in chronological order, thanks to the zero-padding 
I used.

'yello first appears in 1.3.2

I want to use RebGUI with MySQL using Doc Kimmel's protocol. Doc's 
protocol provides a block of blocks of data but RebGUI's table widget 
I believe is looking for a single block for the data. What is the 
best way to handle the sql blocks. Having each row in a block is 
handy for  manipulation.