World: r3wp

event/time is different when comming from the wake-event, it seems.

I need to skip events which are too old... my current event mungings 
work, but are hard to adapt as refresh slows down... having this 
time accurately would allow me skip events

If it's in milliseconds, try: to-time event/time / 1000

hum  good guess.

resize-image: func [
	dest [file!]
	size [pair!]
	file [file!]
	/local im
][	
	im:		load-image file
	save/png 	dest to-image layout [origin 0x0 image (im) (size)]
	im:		none
]

i use the above function to resize images but it leaks on 1.3.2.4.2 
 Am I doing something wrong or is it a bug ?

code looks good to me, though try: draw size [image im 0x0 size]

You might ask rambo group about it being a bug.

(notice you did)

I know it is preliminary, but maybe we should rethink button design 
:-) If you try following, there is some visual effect, you see small 
circles among buttons :-)


do http://www.rebol.org/cgi-bin/cgiwrap/rebol/view-script.r?script=periodictable.r

... but maybe it is because there is zero pixel space amongst buttons

there's nothing wrong with the cirles I think

hey, - there is - they hypnotise me :-))

actually moving the space between the buttons to -1 might improve 
the visuals a bit

as long as they're not changing their color and radius, it's hypnotizing 
level is OK i think ;)

for the VID 2 (or better let's call it VID 3.0?), we should count 
with things like space for hilite and visual focus representation 
....

Rebolek :-))

Electrons should  jump randomly around, no? ;)

but nice app indeed, no?

yes

someone on ml suggested to turn it into plug-in version ...

I suggest making a section in the viewtop for educational tools and 
put it in there.

i likethe idea. Isnt it  time for anothercontest  anyway?

it's one in five years, no? ;)

hoped  that  was5 month, and i missedone^^

anybody made a VID text area that can handle large amounts of text 
without spending minutes to display the face?

display just visible lines. but i don't think i've something right 
here to show you.

That's a good question.

How much is large?

mold system

but yeah, Henrik, what's your data ?

I had about 1 MB of text (output in Tester). It took 2-3 minutes 
at 100% cpu before it finished formatting it.

(or what ever it was doing)

can you split the  text in paragraphs yourself? then you could use 
 multiple faces.

split in lines and use just that part that fits the screen

copy/part at text first-visible-line <areasize> ?

should do the  trick. if  you do not  wrap

but even then should be good enough for theslider.

to get it precisely, it would be a matter of calculating the number 
of lines based on line height. A little more difficult if you are 
wrapping text.

yes. would  drop that.

actually, I found another thing: The data was really consisting of 
an almost 1 MB large line without linebreaks. It could be that it's 
very difficult to calculate the size of the text this way, but I'm 
not sure.

henrik, yes, the engine to calculate line breaks can be manually 
harnessed and its *VERY* slow.

it is used when you set face/para/wrap?: true.

you're best bet is to use a monospace font and do a very fast char 
count instead.

using scroll offset, window width you can select a line of text immediately.

using parse you can also break up a big text pretty quickly.  but 
you need to have a way to re-assemble the text later on, when you 
export the face's data.

obviously, you shouldn't using area, and well, the complexity is 
that you have to implement all the cursor managment manually..  :-(

glayout has an integrated function which can give you a line-block 
of wrapped text.  I had done tests for large files and this engine 
really is inadequate.

1MB line without breaks would kill my favourite text editor so it's 
not so bad:-)

this is direct REBOL useage...  a simple  loop using native rebol 
calls.  no fancy code... so it really is RT implementation which 
is ugly.


they should have made a native which returns a block of  lines directly 
using a face