size mismatch in copytotex

[Decision]

When starting with -Fullscreen, A subsequent Alt-<enter> causes ATITD to bomb out with the following message:

size mismatch in copytotex

This does not happen if I start in wondowed mode and switch back and forth using Alt-<enter>. Log attached.

[Pluribus]

Hmm, -fullscreen mode is documented at disabled... Doh... Well that is fixed... Next client will have it disabled again... (It was disabled for a reason)

[Decision]

Hmm, -fullscreen mode is documented at disabled... Doh... Well that is fixed... Next client will have it disabled again... (It was disabled for a reason)

I can't tell if it has changed yet, or something else is happening, but now it is even worse for me. I can't run in windowed mode at all, and the above is still happening. Did a fullscreen preference get set that I have to manually unset somehow?

[Pluribus]

THERE IS NO FULLSCREEN PREFERENCE... The client hasnt been patched to disable -fullscreen mode OR ALT-Enter... If you insist on continuing to use it you do so at your own risk... Next client patch will remove that functionality to match the docs.

EDIT: The only supported mode is windowed.

[Decision]

THERE IS NO FULLSCREEN PREFERENCE... The client hasnt been patched to disable -fullscreen mode OR ALT-Enter... If you insist on continuing to use it you do so at your own risk... Next client patch will remove that functionality to match the docs.

EDIT: The only supported mode is windowed.

You misunderstand. I cannot run it in anything except fullscreen anymore. It does not allow me to run it in windowed mode.

[Pluribus]

Client hasnt changed since Sep. 1. (4 days ago) What window manager are you using because it looks to be sending a resize event to window when the window is hidden which a distinct bad thing :-) Could you have told your window manager to save the clients parameters?

[Decision]

Client hasnt changed since Sep. 1. (4 days ago) What window manager are you using because it looks to be sending a resize event to window when the window is hidden which a distinct bad thing :-) Could you have told your window manager to save the clients parameters?

Possible. I will check. Sawfish 1.3, BTW.

[Decision]

Okay. It works when I give it no options now. (It didn't earlier, I don't know why.) Giving it a resolution, like -1280, causes it to go to fullscreen.

BTW, are you dropping fullscreen support because it is too hard to support?

[Pluribus]

It isnt a matter of dropping it... It was never supported (outside of the 2 month span that we used SDL for the linux client) The reason that most people run games fullscreen is to get higher performance, a maximized window actually gives lower performance than switching the Xserver resolution down to that of the window and dropping window decorations.

So rather than dealing with all the oddball crash and all the performance complaints from people folks, it is better to just continue not supporting fullscreen mode. (If and when it is stable and fast across all platforms, it will be considered again...) I have removed the listing for the command line entry from the docs since some people dont seem to understand that a disabled command means that it shouldnt be there... Next release distro will remove the command line option and support for switching to that maximized mode that FLTK calls fullscreen mode.