World: r3wp

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 ...

forced micropauses

And, later it can be fixed in a better way. But, right now, R3 needs 
attention.

Preventing RSI, inducing madness and general insanity :)

BTW, I probably should mention that the altme.exe on www.altme.com 
is 1.2.21.

doesn't it redirect to download.com ?

Not anymore. But, that's a good point... probably needs updating 
there too.... but I think they charge for that now.

Why not default a new install to only retrieve the last months worth 
of data.  Include a button much like the "Mark all Read" button, 
"Retrieve History", that prompts the user how far back they want 
to retrieve... or when they search a group, they can specify a date 
and all records will be retrieved in the date range.

[
    across
    text bold "Mark all Read before"   
    field 30
    rotary "minutes" "hours" "days"  
]

This can be put in "Settings and Network Options"

Something odd . I logged into the r2beta world with 1.2.21 and it 
asked me if I wanted to update!

Logged out and in again and no issues.

Explicit latency is good. Please don't remove it. Shows the user 
that the program is working.

and most certainly never overwrite the clipboard without the user's 
consent.

:)

Clipboard is broken in Altme most of the time

yes cleaning up the various cliboard "copy" modes would be nice.

I wouldn't mind getting rid of right click to copy. Just depends 
on cleaning up the "rich text" entries with URLs in them. Alternatively, 
there should be an option to not format URLs.

enough work has been done on Altme to last 10 more years.  on to 
r3

Someone posted (Oldes, Rebolek, Anton?) the code to fix URL hilite. 
Maybe we could get finally that ugly display bug fixed :-)

It was Oldes, IIRC

Showing that the program works is fine, but only if it's unintrusive. 
Blocking the message area is extremely intrusive. Please, add an 
option to disable that behaviour.

My hosted worlds were down...
Message stated they exist but were not online.

I have never got this message before even with the other problem 
of wrolds becoming unregistered..

The worlds were running. 

Could this have been due to some of the changes Carl made...new versions 
and switching servers etc....

maybe if the client is more recent than the server?

there is one issue which is SO ANNOYING, I sometimes close altme 
before throwing out my computer by the window.

 when the display becomes a blue screen if the client loses its connection 
 with the server...


this is both useless and highly irritating, cause when the world 
re-connects (99% of the time on its own) you have to re-click on 
the group, which looses the "unread msg" beige highlight.  it also 
forces you to have to re-click on the text entry with the mouse.


when your internet connection is buggy or a server has troubles... 
disconnection may happen repetitively every few seconds.  the blue 
just makes altme unusable in a situation where it should just stall, 
until a new message is sent.


when a world disconnects, it should just change the color of something 
or put a label somewhere obvious in red color... but don't touch 
the GUI's functionality.... please

(and don't pop up a requestor until it stops trying... like it does 
now)

agree

I wonder if we shouldn't just move to rebol4 world .... and leave 
this one

It's hard for new people to sync all the messages and to post here.

I don't like how recent altme updates treat msg post. The caching 
(or undo) should be done some other way. This grey area blocking 
unless the message is delivered makes AltME feel like the JS crap 
out there ;-)

It interrupts my flood of thougts. I am used to send, and imediatelly 
starting to type new msg. So - as for me, the new implementation 
of lost-post-protection does not feel right here ...

True... I think the trick might be to make it look like it used to, 
but put a [Sending] message at the top (for example).  You can go 
on and send more, which get cached.  If anyone fails to send, or 
too much time goes by it changes to something like like ["Timed out"]. 
 This is a button in fact, so clicking on it will let you resend, 
and you have not lost the message, or where to post it.


This is our plan on Qtask well, which indeed is JS crap.  Bit by 
bit we are all in this industry figuring out how to make everything 
"Feel" better.  Sometimes it is simply reversing the order of things. 
 Same time, but it just looks better...

I'm getting a busy signal again ... is it only me?

Maybe it's just me, but I never try to start typing until a message 
is properly sent in any IM program, so the feel is right for me. 
Also doing it this way makes it clear what you are sending.

Alternatively, the message is immediately put at the bottom with 
a "sending..." notifiier which disappears when the message is sent. 
That might be problematic for message sequencing in the list, though.

http://www.rebol.net/altweb/rebol3/

are not being updated

for me I've been stinged so often, and the delays are so short that 
i like the new system.. it could be a bit less dark.. it seems a 
bit "drastic" to me... seems to make it more dramatic than it really 
is.

Still more to do on it... the original plan from long ago was to 
put it in the list immediately, like other IMs... but indicate that 
it is pending (in date field.)

ALERT: an OS X Intel update to AltME is on www.altme.com/download

www.altme.com/download.html

To install, click on the "Run from current location"... otherwise 
it may hang (not sure why)