World: r3wp

Nope .. try this .  Send a message.  After it has been sent, click 
on the "M" and this area turns black

Same here.

test

I get error windows when AltME is idle now.

I can see the black area even if you change groups, and also when 
I clicked http link ...

The area seems to turn black if the area loses focus.

Got a message Altme need a new version, downloading, dowload failed. 
with Altme intel osx, running the old PPC version works ok

Yep -- also seeing black area at times.

Should be working.. it's alpha though

hmm.. that last message duplicated itself as i switched groups.. 
not digging the new "gray box" posting method

Pekr: I could use that feature too. Where would the button be put, 
in the divider options panel perhaps?
Henrik: 1.2.20 fixes that bug.
Will: what download failed? On auto update or exe?

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

Others: yes, odd. Input area seems to go black on loss of focus.

Upgraded to 1.2.20. So far, nothing exploded.

I see a duplicate message in the REBOL3 group by shadwolf.

Mark everything read: I suggest more room in the area where the icons 
are in the upper left corner for a row of buttons, where the "mark" 
button could be situated. That leaves room for more options.

Carl - the small button can be put in front of "B" (bold) button 
....

I wonder if the dup msg was perhaps caused by hitting return twice 
(during a long delay)?

I just tried it, but seems to be ok.

Testing duplicate message

Pekr: such a button be better somewhere in the area as noted by Henrik, 
not in the edit window icons.

Carl, I found it. Try hammering the send button many times.

Ah, confirmed.  An interesting thing. The feature is intended to 
allow sending again... as a way not to lose the message when "Internet 
Busy" happens.

(I look forward to the day when AltME can use R3 with the new rebdev 
comm methods!)

Carl, did you see the discussion with YueM? A new user who won't 
use AltME, because he claims it's broken, when in fact it's simply 
downloading all messages, which takes time and he can't post in the 
meantime. To him, the program appears unstable. An intended feature, 
I know, but maybe there could be done something to allow bulk downloading 
on first connect to a world.

Yes, it presents an interesting problem... to enter a large world 
like this with so many prior messages.

I've been thinking about this problem for R3 Chat, and I have a solution 
that I think would work well.  It's essentially the same idea as 
virtual memory, where older messages are not loaded until the user 
asks to read them.

Interesting, I just tried changing message groups while my message 
was pending (gray).

So -- it causes the msg to remain gray, and does not get cleared. 
 But, it can be edited and resent.

It'sa known problem :) [though it should read ... stays gray untl 
you send again]
http://www.rebol.org/aga-display-posts.r?post=r3wp151x4293

Time on this is distracting from R3!

Well... whatever pays the bills, no?

Does Altme earn income??

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 ?