Re: [crossfire] Removal of output-count/output-sync from server

[Mark Wedel]

 Yes, I use it too to control how much garbage scrolls by in my client. Please 
 don't remove that until there is a replacement in the client.
 
 Gene Alexander

  Ok - followup question this:

  the current implementation in the server has several buffers that it uses to 
store/track different messages.  What this means is if you have messages like:

you hit orc
you hit orc hard
you hit orc hard
you hit orc
you hit orc
...

  They get compressed into something like:
3 times you hit orc
2 times you hit orc hard

  and so on.  Is that extra logic still needed, or is it sufficient to just 
track the last message an print repeat counts?

  I'm thinking that if this is most often just used for things like search 
locks 
or other repeated checks, just buffering/repeating the last message would be 
sufficient, and is certainly a bit simpler to do.

  The disadvantage is that if there is a bunch of other messages being 
generated 
as you search for traps (say your suffering from poisoning), that would cause 
the search messages to get broken up, etc.

  Thoughts?



___
crossfire mailing list
crossfire@metalforge.org
http://mailman.metalforge.org/mailman/listinfo/crossfire

Re: [crossfire] Removal of output-count/output-sync from server

[Brendan Lally]

On 10/7/06, Mark Wedel [EMAIL PROTECTED] wrote:
   One area that could use cleanup IMO is the output buffer handling in the 
 server.

 ...

   One question is whether it makes sense to put that code into the client.
 Given that both GTK clients have multiple panes for messages, and the only 
 thing
 that really benefits from this combinining messages is the attack messages, 
 the
 amount of benefit isn't as great.  Plus, since the attack messages where 
 changed
 to be more variable in terms of what they print, those often can not be
 combined.  IT seems the main area of benefit is spells.

The other useful one is searching for traps, especially at low levels,
I find that a small number of searches isn't sufficiant, and will hold
down the 's' key for a while, using the output count to bundle the
messages into groups of 10. That way I can search 50-100 times
(depending on how bored/paranoid I am feeling) without having the
searching messages spam the message list hopelessly.

Potentially client side support for this could be much better than
existing server-side support (if it were to say redraw the last
message on the same line it was on but with 'n times:' prepended to
it), but no existing clients do that.

___
crossfire mailing list
crossfire@metalforge.org
http://mailman.metalforge.org/mailman/listinfo/crossfire