World: r3wp

then your work is turning into debuggin and finding workarounds, 
instead of concentrating upon development .... I am not sure other 
toolkits as Qt are so inconsistent ....

the thing is: what can we do about it right now? not much, other 
than either wait, or come up with sneaky solutions on our own. some 
did a solution and made RebGUI. I made LIST-VIEW, because I needed 
it and that's really the only way forward. Carl can't work on 50 
things simultaneously (or can he?) and designing a new VID, I don't 
think Carl can do that in an afternoon.

This is what we have now, and we better make best use of it, no matter 
the shortcomings

besides: read Announce and see if there are some critical VID bugs 
not in RAMBO

well, but that is new info to me, that accessors are not finished, 
yet they are used internally ...

now to do what? report new bug, or to check all styles?

besides that, I have issues with accessor's design anyway :-)

yep, it's not perfect

Carl is calling for bug to fix and (if possible) the fix for it for 
View 1.3.3.

I f you want it to be solved in next relase, just take some time 
to investigate and implemented missing accessors as you want them 
to work.

I dislike people who just go voting (half an hour) and complain during 
five years against their candidate.
On est jamais mieux servi que par soi même

accessors should not be introduced if not finished, period ....

I really start to wonder how our community does look from the external 
pov. It was my friend who got pissed, not me actually, so ...

go to RAMBO and check for my name and you will see that once I find 
a bug, I report it ... not to mention tonnes of my reports in earlier 
days ....

you should be carefull to your statements, as some ppl simply use 
REBOL as a tool, nothing more. Not like us. And to them your claims 
will become arrogant ...

btw - I have one long-standing bug there which I consider important 
to be solved, I reminded many times about it, I even (with help from 
Ladislav) tracked  down where the problem is, but still nothing, 
so :-) ... yes, the red-icons bug :-)

red icons is about ios, net view... so, you can get it fixed on new 
releases of ios, not on new releases of the sdk ;)

that is of course far from the truth ;-)

it was never fixed and it is still in Core ...

... just look at my ticket and you will find out, where is the problem 
... :-)

petr, the ticket is there and won't be forgotten. there's no problem 
with that. but, to fix the red icon problem you need more than that 
- you also need to release a new version of ios.

I am not sure about that ... we tracked down the source ... there 
is one condition actually involved ... which mistakenly fails because 
of how Core (or it is Windows, dunno), report timezone ...

I just call it "red icons" problem, but I don't relate it to IOS 
itself ......

I mean - I am interested in Core fix ... not IOS new release, that 
can come later ...

is there any other script other than ios that has problems due to 
this bug?

actually - no ... let's wait for new altme :-)

view layout [text "Test" font-color none]

This may sound silly, but doesn't one expect the text to be invisible?

Probably yes. (and doesn't sound silly).

Is there a way to have "invisible" text in a face, i.e. invisible 
text even if ALL [STRING? FACE/TEXT NOT EMPTY? FACE/TEXT] is true?

This seemed to be the natural approach; I can't come up with a solution 
to this question (driven by cure curiosity).

I don't think you can do it in a single face... but so I can understand 
the goal, why do you need it ?

ah just pure curiosity.

Here's a way using DRAW dialect text:

view layout [box navy at 30x30 text 200x30 effect [merge draw [pen 
0.0.0.255 text "hello there"]]]

Actually, my idea was to have a FIELD style with DRAWn text without 
having to write my on CARET-TO-OFFSET and OFFSET-TO-CARET as mezzanines. 
Maybe that's a bit over-the-top, though.

Well, the font color could be the same as the background colour - 
effectively invisible.

You would have to change it when the field was selected/unselected 
though...

Mmm....

Put a feature request in Rambo (if it's not there already). I am 
sure I also wanted to use such a feature before for such things.

Yes, I'll do so, Anton.

But, then, such things may change with the upcoming rich-text support, 
so I think I'll first evalute the possibilities this will bring us.

You dont need to measure in the same face.

measure ?

CARET-TO-OFFSET and OFFSET-TO-CARET

Hi Anton, about the list bug with sqlite. We were both right. It 
_is_ a series copy bug. And it _is_ an sql problem ... sql reuses 
the series it has given as a return value on the next call :-(

Volker, of course you're right, I always forget that. So here's a 
proof-of-concept of an AGG field style:

do decompress #{
789CED5A4B8FE344103E7081F9015CB8149EC326BB1827D999D9DDB04B0408B8
8090B84639F4D8EDC48C6347B63371B8F0D7A9AAF6DBDD4E323B487BA0478AEC
7E54D7BBBE6ECFD59F3FFFF8C76FB05C5D5D651B69FB7194CD612B1E24F8C295
0EBDC332125B3907EBF7388AB3E34EC24F7192068FC28234F81B076EDE821B87
713287288E24A4D931C4DE7423BCF850F4C5BE9F4AA43CC92720C2601DCDE145
28FD0CB7DD2501EE6181851CC83CB389E6620EFE3E7261493DB04C339CB3FE7A
058A9DF8FE2FE966F8EA1C024F8213C6AE0821DD21C3CCD10AF6A984E536761F
56B0BC026CF4DC90ABE8A5B613892846E8B131422D4E82751029BEB722A99E83
C8935121CF2111BB05C909A99BC461C8BD159555F524BDB554EAB8AA07EAED88
4547E99F7EAB7E37942251A3A40DB483558D550F818F8433607D2C8328954956
2F012BB756FD35ACB0396BCCE669B440435A518BCA198A24FDD494D80D4E1112
A9BD1341C2F39C1C6CC5003E71C7B1500A7A04357222EADE8A349349A1A620DA
ED5101F7718E92669B86F294DE4A0FAE752712F2BA4AE75A839736B6A793494E
3FB5AE3601FAEA067D32134936EF75CBC89BE36B8B7C4BE4D60B3363FB49BC2D
BD5B45052C492DE4CE8523B3B7AF3A9EA87AE7B091C253A45AC3223A761628B5
24222C296AC659A97E119D6889F730F28324CD8A1E66B6583D8625EEB94FA295
890AEDA4DF82DA00E1F73503C6E5C32CB27316E4B4245666C6EE13291E1C255B
41434FA2D7DBEFC94410EA68D43335717888132F9D7754778FBEF060BBFB248D
D1FBFB7AF1A41F8AB5CDC92C9207CCA641248BF97D37684F6DD2EECD655562A6
4B0D02506BEC75166F831B5E20C729DE34CA6D78491975557C6D450E334CE0A3
BAEE6021DB1D1DCC0B990AB42272EC29BCE29C9F2FCA2ECA33637809D37CA2CB
AD9A4AE04B199635081F3B064FA4978843C923EB43B859104785086576E0D0C7
DDDD7DBA505EB2C07CB4DE00A7A46ED6A0562441AEE7CDA0E18E7E2669C95136
8E6D5ED04A89BC33A6403DEDD6D47EB0F469623E05508298F86D4DEDD3D46440
5294A2061F203D6239D93A8F813C60AD457DB2E7F55695E643E3A289C94F264A
8D5CB7B64154BD315355459B4DCEE0885648DF4708334777DBEEE2543A9E943B
43F224B718C8AB1C2F58F7B11C4EBEBD859D8CD02B44A3FE761B554F822DA38A
75647C9A4FC770675C4354475E0CBBC07D80E57DB8975CF456857AC7E6BCED07
6168D37286810D6667830C223F6D0667F96C0CB7347C7A2BDA0521D3247F0D4D
319D23D2793786771398E29F1B6334AD137144FC113E22C6386C824C0EFF0EF2
FC1AF76BF17C93DF8CE1C6B8C60D831D8CDEE4B7E3F6B2B7F99DBE88B1908480
4715361F37553AADADDFD13BA3B21167B43AEA715BBBF074CC6E6FF2C9181ED1
29110EA162BE135116D808D5452A3D1D37E794C35E07A284227319B088C29A5C
461B71E2CC4022DE431B55C562A122FA45BB4E9A75ADE26C6006B54A5F95F6C8
D5079790E1472A4DA8CCFC0AFD8E2C5AA25D0556CAB1BAD2A8B34B5D6E6ABBA0
1DEBB357DB7BEF0622AD1440B9EBF91228DFD03332EECAC65E72CA35B8E961E2
000E3BCF447A773FB9A42FC72D94CE8F424E30DDBC6CE9FA5563AA7D57CFBD54
DE274689A9DE766BA0AEDE330963209D56733F0A46084EC8B1BFA5BFE9EC8D59
0B8D706050D2D5F4A0A18A852C5C6725BE3672E44B2083D9F87B3736D03CA5F8
F65BEB45466B4127F53E12938F78E82F81D883C4CAB109FC8C4063942197880D
0F62A73309E53D848FB0F4E203023AAC36AB92A6DE0EA6331673F3FE7B038E19
302AA75D278AED74131F400B7AFA6AA916572961DE7856A88C7552E0B4F345D1
7616399E7DBFD0CE0778C12AA3CB0DB513ABDCE4F615B3ED83FB10D4D52EE383
7DEF585FB68124D6A772626BADC29F76C2EE0B7E369B667429534C248BF2ECD3
83E0BA7EF3D6038AA3C8999FCF9741CF4F90BEF010DAFF8288D0760E87D6532B
4115089470F40AD409C41742A60AC2FEB83248710832778327125FECC332EA78
6F73F6BEB6BEB48ADD8A345114A0069848F8E20A31EF7D2C126FEE38AB012C7F
6D7D669D4002CF50259BED90106C6AF2D70567C37B0C6EA077A2E1914DBC9570
82F1A6C63BE87E701DDD27E021966B863AD33583BA7D6E6FE6DD73E89B25A20B
FF4B24BAE783CCA72C51C250E57C89F802EB9396485DC19C2F518D303F5589AE
AD2F2CFABE651ADFEFE87760020390A109D7D657B8C33E628CC5CC0ECDFDE754
62FBCEB6C193A11CB86EA0D6444BCF94039B864DE41671EAF3A4BF8A76A74619
1156D906008399E773DDF12949F9DAFAFC1CF351E6E2AF5BFF5BF034CFC5B74B
AA5F8B2660586A4CDB29096643F1DECF7739F18C60E3BF32D1C5E631AB6718C8
5588F002BC5CD8B899D47B57FF8A5DE3FADED9E3834E651751350376D36581E6
534F100559F7EB5DA13B0290ED2FE5D4D457FC9E69D4C5D39CBF36D0D55F79D5
31FDE6166637260EF883395D03808BAA9589BA0708C531DE679DBB1E8A1DFE3F
8DC65D367F5187BB9B0958FC8F20CE0FBFFE6AFF12C8D0B39809BEAB84D777EA
85FE0FA4E816516AA363A05D7A1FF79E81E647D1F1835C7AF054BEDECD7A7C5D
CA9286C447ABCBC016599F88FC0B87A1CF98C7230000
}

I really like the idea of implementing it to improve the look of 
fields using larger font-sizes because it seems to respond fast enough 
to be usable.

If only I'd have an idea of what the problem occuring in WAKE-EVENT 
is. Looks like an invalid face or broken draw block to me, doesn't 
it?

Ingo, thought it must have been there.. Interesting behaviour. I 
wonder if it is intentional ? Could be for speed in high-throughput 
applications.

Christian, that looks really nice !  I will have to follow this up..