World: r3wp

I'm seeing some strange behavior with Parse...

ws: charset rejoin [space tab newline]

parse "   This is a test!" [s: some ws e: (probe copy/part s e) to 
end]
; == false

parse/all "  This is a test!" [s: some ws e: (probe copy/part s e) 
to end]
; "  "
; == true

I shouldn't need /all when I provide a rule block should I?

In truth it doesn't always fail but I'm not sure what causes it to 
change it's behavior.

Heh.  Or rather I don't know why SOME was ever working but I saw 
it work once.


parse "  ^- this is a test!" [s: any ws e: (probe copy/part s e) 
to end]

ANY appears to work all the time though.  Strange.

charset is bugous in R3 currently

So this is a problem with Charset not Parse?

I made my own function.
charset: func [str /local bitset][
	bitset: make bitset! 256
	foreach char str [append bitset char]
]

to be right, is used this to make complement of charsets

you made a mistake bout the understanding of /all refinement, see 
help

You're not making much sense.

Sorry, i mean, forget my charset function. your problem is the missunderstanfing 
og /all refinement

/all -- Parses all chars including spaces.

if not, spaces are skiped.
spaces are : space, newline, tab

Yeah, I read that part.  For some reason I thought parse didn't skip 
whitespace if you provide a block but this clearly shows otherwise...


>> parse " a b c ddd " [ "a" (print 'a) "b" (print 'b) "c" (print 
'c) some "d" (print 'd)]
a
b
c
d
== true

But why does ANY work without /all while SOME doesn't???

because any is an optionnal rule not some

basics

That doesn't make sense to me still.  If the parser is skipping whitespace 
unless you use /all then any should fail the same way that some does.

No, Optionnal means that if ANY fails , the parsing process continue 
with the next rules

Ah, but ANY didn't fail.  The paren was evaluated which means that 
ANY succeeded.

show me your code

But whatever.  I have what I need and as long as parse is behaving 
as Carl intended then, whatever...

I posted the code a few messages back.

Then, it's not related, the parent is not associated with the ANY 
rule. So that, the ANY rule can failed and the parent will be executed 
each time

cardinality of ANY is  0,N
cardinality of SOME is 1,N

I changed my mind, i uses the default caret and highlight behavior, 
much simple.

Ammon some doesn't work for SOME reason   ^^ .... probably  ^^

Most widgets are rectangular in shape ... any reason for this?  Are 
other shapes feasible?

So far, there is not much widgets, which could have different shape, 
no?

Lack of imagination?

edge / hgit testing is the main reason

easier computationally?

much

you have to use alternative methods like colour testing for non-regular 
shapes

well, what can you do with quad core cpus ??

I've watched those multitouch demos ... seem to use irregular shapes

ill dig out my radial menu thingy and update it for r3 and test it 
for speed.. have a old version at http://rebol.mustard.co.nz/readial.tar.gz

http://rebol.mustard.co.nz/radial.tar.gz.. oops

Ok, that is cute

meh - ive done it in assembly before - its rather sad in rebol :(

though I suspect it's not working ... I only see shapes and no text

its 2003 - back before the text in agg changed

ahh...

I'm surprised you were able to find it so quickly!

i downloaded my website today to look for some old sudoku code :P

Silverlight is starting to use radial menus too

My Daylight Map used color to detect irregularly shaped hit spots...

yeah colour testing is fast and maps nicely to functions

Are you still working on your own graphics system for R3?

http://ross-gill.com/r/daylight/map.jpg
http://ross-gill.com/r/daylight/map-zones.png

im waiting for Carl/Cypher to fix some of the view holes.. and also 
for modules and timers and threads :P