World: r3wp

I think it's worth half a day's work to get some fixes done for things 
that have been problematic for a few years now.

How about marking groups read on the starting of a new instance?

New instance of what?

Or a separate utility ...

new installation of Altme is the only time you really want the group 
color reset ..

I think that's too specfic. I'd rather have a manual procedure using 
a button. People are used to that from their mail clients.

Ok, logical place is in settings ..

I like that idea. Such a change can happen very soon, and there's 
room to offer a couple options.

I experience some troubles with AltME now ... it disconnects me from 
the world after not being logged-in for more than 1 minute ...

Nothing in that part of the code has changed.

Does it happen in all worlds or just this one on the cloud?

it is stable now ... it happened some 20 minutes ago ..

Pekr, there is a new update 1.2.20. Did you get it?

It's not automatic?

logging off and on again ...

where 1.2.20 ?

1.1.29 here on Linux ?

19 ?

Terry: can you explain 
duplicated itself"? Do you mean it was sent twice?"


I posted a message to a group, and it just stayed grey (yet posted)

I then moved to another group, and it posted it there too, and turned 
white.

I didn't hit the button twice.

1.2.21 - fixes black edit box, adds Mark all to the divider toolbar 
options (the small wrench above scroll bar)

Carl, maybe you could add an option to store the read/unread flag 
for each group on server? This way when user logs in from different 
machine the state of groups which were marked read previously will 
be in sync.

Yes, I want that too. One step at a time. ;)

That's a button I've been waiting 6 years to click. Wonderful. :-)

yup, just quick idea while reading this group. It's great Altme updated 
again.

osx10.6.2/intel it says "A change has occurred that requires you 
to download a newer version of the software. Download it now?" than 
it says this file is not found http://www.altme.com/download/altme025

OS X version not updated for quite a long time.  Let's jump forward 
with it and make it a 2.7.7 based build.   However, things are generally 
crazy today... even the weather... a powerful Pacific storm from 
here all the way to L.A. (1000km to the south).  Knocked out Reichart's 
power, it seems.

one of the downsides of the OSX version is the problems with clipboard, 
but they are general for OSX REBOL/View

Got into an update loop ... started up in 1.2.21 and then it asked 
if I wanted to update again .. downloaded 1.2.21 again and asked 
the same. I demurred at this point.

black edit box is stil there if shift focus

Two things:

1. The REBOL3 AltME world seems to be horribly slow at the moment. 
Is that only me, or do others observe that as well? From pressing 
send the message area is regularly grayed for several seconds.

2. I find this graying out of the message area to be highly annoying. 
Being able to type the next message while the last one is sent is 
very valuable to me.

Right after posting that msg above, we lost power.

Storms?

Yes. Graham... try this: in your altme dir, remove mods/ directory. 
Then restart it.

ok ..

Andreas: how long has it been slow for you?  Where are you located? 
We moved the server from Canada to Texas a few days ago.

Curious ... I went to 1.2.11 (!) and then updated to 1.2.21 ...

What OS?

Windows 7 Pro

Slow only since the graying of the message area started. So I guess 
that's since today.

That's quite interesting.

My idea was to store the outgoing message in the clipboard rather 
than blocking like this

Restarted .. and stitll woring okay now.

It may not actually be slower than usual, but rather that the graying 
of the message area makes the latency more explicit.

Yes, I've noticed that too. Makes the time difference much more obvious.

I'm not sure that you could type anyway while the message was being 
sent ...

And it really annoys me if I can't just continue typing, but have 
to wait ... seconds ...

It would be possible to make it optional.

I think it's to prevent RSI

Please ...