World: r3wp

request : to really test new AGG/draw, we needs a command list. The 
examples helps, but there is now way to tell the presence and purpose 
of optional parameters. Not a full doc, just a simple one line per 
command list, ie : 'line 1st-point [pair!] 2nd-point [pair!] ... 
n-point [pair!]

vincent: command list should be available soon

You can probably figure most of them out with the help of the existing 
AGG docs.

We will be finalizing the DRAW syntax very soon. After that step 
we release updated command list so your test scripts won't break 
in later releases.

Looks like this bug is still here:

make bitset! 1057222216 ; --> hang

excuse me !   It does work OK...

(sorry about that, was just going through my old bugs)

#3723 : an old bug (it was at least in /Core 2.2.0) The 'list-dir 
function is missing a 'dir? test on argument. A line like :

if not dir? dir [throw make error! reduce ['access 'cannot-open dir]]

just before "read dir"  would do it (as 'dir? works with ftp:// too.)

not sure it's worth a report : from /View 1.2.10, there is a 'lic 
global word. It's probably a missing /local from a mezzanine related 
to license checking (it's between 'set-license and 'license.key in 
system/words)

#3716: tested and worked  with original code that had problem. Thanks.

hum is it normal I submited a new ticket to rambo and I have this

RAMBO Ticket #-257

Yes the system allocates a negative number when you first submit 
a ticket. It seems to get allocated a positive number when it is 
viewed by a human.

#3716: The problem still seems to exist in more unusual cases :

REBOL/View 1.2.114.3.1 26-May-2005 Core 2.6.1
parse "string with 2 semi-colons ;; " none
== ["string" "with" "2" "semi-colons" ""]
>> parse "string with 2 commas ,, " none
== ["string" "with" "2" "commas" ""]

and the very extreme :

>> print mold parse "this string includes more ,,,,,,,,,,, semi-white 
spaces ;;;;;;;;
; " none

["this" "string" "includes" "more" "" "" "" "" "" "" "" "" "" "" 
"semi-white" "spaces
 
 
 
 
 
 
 
 
]

Should I re-submit to RAMBO?

thanks for the draw command list - (time to experiment and crash-test 
draw/agg :-)

anyone can confirm -258? http://www.rebol.net/cgi-bin/rambo.r?id=-258&

I do not know, if this is comparable.

If I work with ODBC, pull out the network connector  and catch the 
error with try [], sooner or later I can observe a consecutive fault 
 either at a different part of the program doing something totally 
unconnected with  that  or a GC fault.
Either way the process is no longer able to work as expected.


In server processes I help myself in this case with automatic closing 
and starting a new instance of the program.

but, is it possible to confirm that on 1.2.114?

if the crash noted on -258 only happens on 1.2.1 then it's probably 
already fixed (a bug with read/lines was fixed), and the ticket should 
be dismissed.

Gabriele re http://www.rebol.net/cgi-bin/rambo.r?id=-258&, perhaps 
can you contact  Giuseppe Chillemi by email to retest with 1.2.114 
.. (looks like he hasn't logged into altme since last december)

Peter - I think, submit again for the new cases, since the original 
cases in the bug are fixed. but mention the original ticket number 
in the new post.

Most annoying bug:  When REBOL accesses the sound the port it drops 
the Wave Volume down to 25% of the volume on Windows 2k

please delete --> RAMBO Ticket #-262

problem fixed...

This looks like a bug in the AGG compositing engine:

view center-face layout [

    f: box 100x100 white edge [size: 10x10 color: none effect: none] 
    with [

        pane: make face [edge: none offset: 50x50 size: 50x50 color: yellow]
    ]
]

At least the black angle in the bottom right corner isn't what I 
would've expected from an uncolored edge ... Is this a known issue?

Looks the same under older releases.

Not what I would expect either though.

Oh, true, I should've checked that ... But this looks so strange 
that I likely was thinking I would've seen it earlier if it was the 
case with older releases and betas ;-)

Might as well submit it.

Ammon, rebol sound system needs overhaul anyway. But rebol implements 
sound/volume by just setting the host os system volume. A bit naughty, 
perhaps.

sound/volume: 1.0  ;  is full volume

Gabriele #-258,  it doesn't look like it crashes View 1.2.114.3.1, 
even after more than 10 times engaging/disengaging the internet lock, 
just lots of rapid read errors, as you might expect.

Mmm.. I couldn't reproduce the bug on View 1.2.102.3.1, which is 
supposed to be the version just before the read/lines bug was fixed. 
I'll try an older one...

no crash on 1.2.100.3.1 either...

no crash 1.2.48.3.1
no crash 1.2.20.3.1
no crash 1.2.1.3.1   ; eh ?!  I can't reproduce this bug...

I'm also on WinXP.

I think I have a null-result, because I can't reproduce the bug even 
on View 1.2.1

and Giueseppe also previously posted this bug ~15 months ago, which 
is well after View 1.2.1 was released.  Hmm. Maybe there was a buggy 
set of betas that I skipped over...

I want more information from GIuseppe - what version of View did 
he test with ?

he told me 1.2.114 doesn't give him the problem. he had that problem 
with 1.2.1.

#3737 (call and file! datatype) : same problem on Win2k. The error 
message is right, it's a path problem - but if it works with string!, 
it should work with file!. A workaround :
call clean-path %prog.exe

it has been fixed. btw, the error actually came from to-local-file, 
i think.

>> layout [b: field hide]
>> set-face b "123"
>> get-face b
== "123"
>> view layout [b: field hide]
(enter "123" in the field, tab away and close window)
>> get-face b
== "***"

Is this intentional?

#3733 fixed...tested by me.  Thanks.

Cal found a fun little bug with Select/Skip when using it on a string. 
 Here's the shortest code snippet that we've come up with to reproduce 
the problem.  Only copy and paste this into a console session that 
you don't mind killing cause it is going to lock up...  Tested on 
Win2K with the latest stable release, Command and recent betas...

select/skip {"<a><mm></mmmmf>"} "foo" 2

We have been playing with changing the length of the string, the 
characters in the string, etc and haven't really been able to find 
any reason to this rhyme, perhaps some of you bug hunters could help 
us track down the actual cause of the lock up?  In the mean time, 
we'll keep playing with it as our schedules permit...