World: r3wp

I think we should kill all colour options.

scott: the reason is that with a black bg your eye will let more 
light in, because on average it's darker, and the white pixels will 
"burn" the retina. with more illumination the eye adjusts so that 
you don't get too much light in.

wouldn't break my heart, if AltMe used my system defaults.

sure, i agree it would be better to have user defaults.

i'm just saying that light bg is usually the default for a reason, 
not because we're all crazy ;)

quote from that article:

Several other important findings also resulted from the analysis 
including the fact that light-on-dark color combinations were rated 
the same as dark-on-light color combinations and the fact that as 
the overall brightness of the text/background combination increased, 
so did the overall user rating.

It's so we don't waste ink when we print!

but all my software seems smart enough to know what I want.  I can 
specify all text as black in IE.

that's weird.  why is all the white now pink?  maybe I just don't 
know what i'm doing, or I need to RTM

It's a general issue about usability.

Web browers are much more flexible -- they have to be: they have 
more users.

Soem accessibility options (like chosing fonts and sizes) need to 
be built into View rather than each application.....Then making fluid 
GUI applications will be easy.

Is there a "hot-key" to turn on/off the multiple-line (CR-mode) in 
Altme? I know it's just a mouse-click away but...

The pencil icon

ah, but you're looking for a hotkey... sorry, not that I am aware 
of.

Ctrl-E

For the future, just type "AltME shortcuts" into google.

Then bitch at us for not updating it : )

Which you can do here: http://www.altme.com/feedback.html

ha, nice website!

such face-lift would not hurt for RT's site :-)

Ah, you guys are on it! Thanks all. No complaining here, Reichart.

: )

I've been getting lots of these errors lately for some reason ( Never 
had this problem before):

Invalid data type during recycle
** Press enter to quit...

That is what we call the "rebol" bug.

I'm wondering if it might be cause by not enough ram? I've installed 
too many programs that leave drivers running in memory.

We see it randomly so far.

I think it was caused by my setting message limit to 10000 per chat 
room so I could do some searching.

I changed it back to 100 per chat room, and now the problem is gone.

Cool!  That is actually pretty solid info then.  WE are going to 
simply cap to 100 except for single operations.  In other words, 
you can search the past, but then return to 100.

Thoughts?

Good idea. It happened because I forgot to change back after searching. 
...didn't realize it for awhile.

Thoughts, yes. I'm not sure, if you read all history into mem!? If 
you set cap to 100, it may be a good idea to only load 100 posts 
into mem for each group. Searching should then be smart and search 
on disk, only loading those posts in, that's needed.

Yes, it would be much better if a search could be done without the 
user having to change any settings. Otherwise most users will probably 
not do any searching at all.

I would also want a browse mode where i could broese all history 
--- and that 100 is pretty small 500 or 1000 should work. (and if 
they dont there is something else learned about the bug) but I am 
sure I have never run with less than 1000 lines of buffer and only 
rarely had the recycle bug  and then most likely because of searching 
prompted me to increase my buffer and I would only decrease it if 
things got too sluggish

My computer is really low on RAM, which might have something to do 
with this.

I have a lot of RAM, and I tend to leave the history at 500. Please 
allow the cap to be specified, and then have the whole of history 
available for search.

How about loading stuff with a load/next loop? its a block of blocks, 
so that would work. and the loaded portions would be smaller.

I think it's related the RAM (or the lack thereof) as well. I normally 
see that when I've hit my limit and venture in virtual memory.

I think its related to timing. A big operation takes to long. Using 
vmem takes even longer.

on the detective the GC used to crash a lot when invoked while inside 
an awake function. i worked around it by deferring actions. i guess 
this is the same bug or very similar, and it should be fixed in view 
1.3, so a new build of altme should fix it.

Ok, so a large amount of data processing, the creation of a large 
block perhaps, or lots of small ones, could cause the GC to kick 
in to free some older data.

It may also have something to do with the after-effects of a full 
virus scan.

New AltME release (must download, will not auto update to this):
www.altme.com/download/altme-b1203.exe
www.altme.com/download/altme-osx-b1203.tar.gz

If you have bugs or minor enhancements (no majors accepted right 
now), be sure to report them using AltME feedback.  We do not scan 
this chat group (sorry, not enough time!)

Current version is 1.2.3

We can now add filesharing to this world, because 1.2.3 does not 
auto-load all files.

Running 1.2.3 under OSX, and it seems to work ok. Who desides, if 
filesharing shall be opened?

It is to be decided by the admin users of this world.

I think they have all requested it. So as soon as people are upgraded 
to the new 1.2.3, we can turn it on.

note, that 1.2.3 most probably fixes the "recycle error" crashes 
many people have seen. if you used to get that problem, please try 
this new version and let us know if it still crashes. :)

survived 1 start with 1000 messages. but never tried, may have worked 
before. now how to scroll precisely? :)