World: r3wp

; find version
cont: read/binary file
version: none
result: parse/all cont [
	some [

  [to "REBOL/View " "REBOL/View " mark: version-rule end: (version: 
  copy/part mark end) to end]
		| thru "REBOL/View "
	]
]

digit: charset [#"0" - #"9"] ; "0123456789"

version-rule: [some digit "." some digit "." some digit "." some 
digit "." some digit]

Hooray for Romano's FTP!  I've found it to be very reliable.

I have one modification wish for the FTP scheme: to add a List-Options 
variable like other FTP client programs have. This would allow LIST 
-la which allows hidden files such as Apache's .htaccess to be transferred 
using the scheme. At present these files cannot be transferred.

Gabrielle: I submitted a bug to Rambo that  was just a mistake in 
my code. Sorry. Please could you delete it - #-233.

vincent: please add any crashing example to RAMBO with importance 
set to Critical.

Brett: please add that as a wish ticket. if it won't be in 1.3 it 
will be in 1.3.1. :)

Is there any status on the documentation yet? Perhpas we could review?

done: #-234

Didn't know I could - what is my logon?

Ignore that - just found it.

#3709-3710: sorry, got confused by linearity of image! mixed with 
useful pair! shortcuts. For #3709, I was thinking about "copy image 
from index to end" without getting out of bounds.

#3714 works

Yes, Hooray for Romano's FTP!  Just remember to disable your previous 
Romano FTP patch (if you have one) from your user.r.  I added a version 
check around mine:

 if (system/version * 1.1.1.0.0) < 1.2.110.0.0 [ ; View1.2.110 has 
 Romano's FTP handler built in.

  do load-thru site/patch/ftp-romano-patch/ftp-patch53.r  ; the old 
  patch
	]

I'm not sure it's a good idea to not allow 0-sized faces. Is it a 
speed improvement that makes things so much faster ? The user code 
must HIDE the face instead of sizing it to zero, but HIDE may have 
other unintended side effects that are hard to workaround. eg. time 
events are stopped by HIDE:

view layout [btn "hide" [hide f] btn "show" [show f] f: box red 0:0:1 
feel [engage: func [face action event][if action = 'time [print now/time]]]]

If you are making a generic resizer, you can't just go modifying 
the code of the controlled widgets...

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.