TIP: Click on subject to list as thread! ANSI
echo: fidosoft.husky
to: Benny Pedersen
from: andrew clarke
date: 2003-02-24 16:32:12
subject: msged bug in x11 term

Sun 2003-02-23 21:24, Benny Pedersen (2:237/53) wrote to andrew clarke:

 ac>> I had it up to 167x56 with no crash.  Can you tell the terminal size 
 ac>> with the program below?

 BP> 261x85

Well that's an absurd size.  Surely you can't actually use Msged like
that unless you have a wall-sized monitor.  :-)

 BP> it does work upto 255x255 i suppose ?
 BP> but seqfault if one are over this range ? :)

Probably.  Keep resizing the screen width until it stops crashing.

A fair bit of the screen handling code of Msged will need to be
rewritten to not use unsigned chars (0-255) and use unsigned shorts
(0-65535) (or maybe just ints for simplicity) instead.  Probably not
worth doing unless you really are planning on using it with terminal
sizes above 255 rows/cols.

Which reminds me, Msged will crash in Windows 2000 using the default
Command Prompt window, because it uses a 300 rows (with a scroll bar).
I think Msged should just do the sane thing and not use anything above
200x200 (or whatever it can do before it crashes).

 BP> i have thinked to build the kfe, but i need som kde source to build it :(

KFE?

-- mail{at}ozzmosis.com

--- timEd/FreeBSD 1.11.a5
* Origin: Blizzard of Ozz, Mt Eliza, Victoria, Australia (3:633/267)
SEEN-BY: 633/267 270
@PATH: 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.