World: r3wp

And I would take them out for beer even if they would not do AltME 
in particular :-)

You may remember that, before the Crash of March '07, REBOL.net was 
hosting a small, web-accessible archive of this world.....It showed 
the last 300 posts in all [web-public] groups.

Now, with Carl's permission, we're hosting it on REBOL.org. With 
some changes:
-- *all* the posts, not just the last 300

-- permanent URLs, so you can refer to classic posts by a fixed address
-- [one day soon: fully searchable]

http://www.rebol.org/cgi-bin/cgiwrap/rebol/aga-groups-index.r?world=r3wp
***

Posts will lag a day or so behind for the first few weeks until we 
properly integrate it into REBOL.org.

Thankyou.

Re: Serving multiple worlds. If I have a shortcut to start a second 
world, e.g.: 

	path/altme.exe -s "worldname" -p 5401


On the same machine where a world is running on port 5400, the second 
world starts fine, but the Check World tool reports that it's on 
Port 5400, and attempts to connect go to the other world (which *is* 
on port 5400).

Has anyone else seen this?

In a similar vein, does anyone else want the feature to be able to 
post via the command line or some nice API? e.g. 

	path/altme.exe -w world -to group|user -m msg

One problem with the command line approach could be message length/formatting.

Sending a quick note with the CLI would be nice and I'd use it.  
Maybe not everyday, but I can see the potential.  (Now I'm kidding...) 
Unless I had to boot into Windows to send the quick note.

Greg, my problems with worlds colliding has been limited of late, 
but I recall it had something to do with the fact that the original 
world associated with 5400 was not working when you regestered the 
new world.  So instead of the new world grabbing the 5401 port (the 
next in line) it grabbed the first available port, 5400.

In my experience that meant that you now have to simply drop that 
word and create another world that will respond to the proper port. 
 meaning have your original world running when you register the new 
world.

I had lots of problems with this early on when trying to run multiple 
worlds.  At one time I had 4 worlds that I attempted to keep going, 
for free without reserving the world name (I know, i'm cheap), but 
found it was a pain to keep restarting the worlds in sequence one 
one of the worlds inactivated.

not to mention the groups I was trying to keep in touch with had 
no interest in this type of tool.... now they all use facebook and 
Messenger.  Go figure.

Thanks Brock.

Glad I could finally help someone here.

I'm assuming this bug has already been reported but if not it seems 
when you have altme open and spend the windows taskbar so that it 
takes the maximum space that it crashes altme.  Not that many people 
would do that but still seems to be a bug.

Please describe this again in more detail...

I would have Altme open and if I "expand" the task bar to its maximum 
extent it would crash altme.

The windows taskbar that is.

I have never seen this.

What is your resolution?

Nothing - sometimes it does it and sometimes it doesn't it seems.

maybe it is just my computer that is doing this.

paul R is asking for your screen resolution ... pixels and whatnot

Clicking on this link, AltME thinks it's an invalid email address.
http://www.mail-archive.com/[rebol-bounce-:-rebol-:-com]/msg02185.html

Oh, sorry Tomc.  My resolution is 1024x768 32 bit color

Interesting, then I guess the only thing is............does anyone 
else see this bug?

I run at the same size and just dragged Altme out to cover the whole 
screen and expanded the task bar with no problem.But then maybe i 
did not understand the problem

Reichart: I also see the bug. But I noticed that occurs only when 
I put  the task bar in the right side of the desktop, and then expand 
it to the left

Alberto, I just did that and it crashed Altme on me.

Win XP pro here.

yep, also Win xp here

win xp pro

I tried but could not get a crash but maybe I misunderstand the protocal 

the "task bar".   what bar is this top of the altme window?  winrows 
task bar (typically at bottom of screen)
I have tried most everything I can think of 

the question might what graphics card/driver   virtual window manager 
 ...

I believe he is talking about the Windows task bar at the bottom 
right of the screen on Windows XP Pro   I could not get it to crash 
or any other odd behaviour and am also on XP Pro

crashes here too. just dragged the task bar size (remember to unlock 
the taskbar!) to maximum size so it takes up half the screen and 
presto, AltME   crashes.

I can replicate what Henrik describes. Using Win XP.

I can't seem to make it happen.

Having the TaskBar on teh right side is odd as an interface...

perhaps AltMe needs to be maximized?

I use the win2k skin.

I only have AltME (and all my windows) maxed.  Win2K skin, hmmmm...

no crash here (XP) with much fiddeling with windows and taskbars 
..

I've got some strange problem, Ican't see what I type in AltME. I'm 
able to send messages, but the area still remains empty. Never seen 
that before.

Check colour.

My next post is white-on-white:

White on white

You can see the text by pressing the colour-icon next to the AA icon.

jljkGeomol it's not a color problem, even the cursor does not move. 
I've got empty area but now I'm going to press CTRL+S and it will 
be send (and I hope without errors as I can't see what I type :)

If I type something but do not send it, and switch to different channel, 
the text in area is shown

So I've restarted my machne and it works again. Very very strange.

I just thought of a feature that a future version of Altme may want 
to look into, sub-texts.  I have an urge to make stupid off-topic 
comments sometimes, but also have a respect for keeping forums on 
track for the greater good and use of important time.  Perhaps some 
furture version could have a trigger or formatiing option for 'invisible' 
sub-text, only seen if requested.  Then we could make off-topic friendly 
comments without too much worry about disturbing serious discussion 
threads, while keeping said comments 'in the thread'.  Just thinking 
out loud.