[Opensim-dev] mono *.exe crashes if screen is smaller than created...

[Sean Hennessee]

Thank you Melanie. Your suggestion for adding -gui=true helped 
immensely. While it doesn't work with the UGAIM services we are using 
right now, it did help with the regions, which is what we have multiple 
users connecting to.

Peace,
Sean

Melanie wrote:
> This stuff is somewhat of a work in progress.
> 
> One, there is a Mono bug. While .NET makes the variables for screen 
> and window size track changes to the window, Mono does not. However, 
> it also doesn't keep the process' window at a fixed logical size. 
> Rather, it does the worst of all options: It doesn't tell us the 
> size has changed, but throws an exception if your code assumes it 
> hasn't. There is no way to get the new size even after the 
> exception,, as the variables are never updated again after initial 
> program start.
> 
> Now, in the region server, you can currently use -gui=true on the 
> commandline. That tells it to expect being controlled by an external 
> GUI, which makes the console go stdin/stdout with no fanciness at all.
> If this is not used, you get the fancy, cisco-like console, but you 
> also get the crashes when resizing. On .NET, resize is not an issue.
> 
> Two, The legacy UGAIM server lack support for this and always 
> provide the fancy console only.
> 
> Three, B.U.S.T. has an option, -console=basic|local|rest, where 
> basic is the stdin/stdout console, local is the fancy one and rest 
> is a remote console connector using web protocols, which is a work 
> in progress.
> 
> B.U.S.T. aims to replace the UGAIM, it already replaces A and I if 
> configured. Therefore, the issue is really present only on U, G and 
> M. G is the next server slated to be dragged into B.U.S.T., leaving 
> only U and M for the moment.
> 
> The simple Console is actually part of UGAIM, it's merely missing 
> the glue code to plumb the command line option through to the 
> console. That could be added if really needed.
> 
> Melanie
> 
> Mojito Sorbet wrote:
>> Not to mention various ways of spawning and piping to construct console
>> aggregators.  I had one almost working over Jabber once, except for that
>> darn ReadChar in there.
>>
>> On Sat, 2009-07-11 at 03:50 +0200, Torrid Luna wrote:
>>> Also sprach Mojito Sorbet (mojitotech at gmail.com):
>>>
>>>> Why can't the consoles just use ReadLine and WriteLine?  That would make it
>>>> easier to interface with in a variety of ways?
>>> +1 
>>> Coming from Unix, I had these kind of problems only with Cisco
>>> Terminals, Windows Telnet emulations and Opensim so far. stdin/stdout is
>>> so much more convenient, and it would save a lot of screen sessions. 
>>>
>>>
>>> Cheers,
>>> Torrid
>> _______________________________________________
>> Opensim-dev mailing list
>> Opensim-dev at lists.berlios.de
>> https://lists.berlios.de/mailman/listinfo/opensim-dev
>>
>>
> _______________________________________________
> Opensim-dev mailing list
> Opensim-dev at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/opensim-dev
> 

-- 

Sean Hennessee
mailto:sean at uci.edu
http://www.nacs.uci.edu/~sean
Central Computing Support
Network & Academic Computing Services
UC Irvine
(949)824-8225 Office
(949)293-5224 Cell


... . .- -. /  .... . -. -. . ... ... . .