Follow-up Comment #4, bug #7998 (project wesnoth):
ivucica here, the same guy as before. (I should really register here, I
guess.)
I began reporting this on SDL's bugzilla, but then I realized I'm not sure
what I should report, since this is pretty much Wesnoth-specific. I've just
tested against this bug again, and I must say that it is not a bug at the SDL
level. I can say that mouse is now visible, however it still does behave
oddly. Nevertheless, the behavior I described is most clearly visible on any
semitransparent surface, such as tooltips in status bar on the main menu, or
in the Credits screen.
>From what I observed, it is possible that this is caused by a lack of
doublebuffering in SDL surfaces when using fbcon driver. (It is fairly
obvious, since the way map is rendered is visible during initial map
display.) Detecting single-buffer surfaces is probably trivial in SDL (quick
skip through documentation did not reveal a way, but it's surely possible),
and turning off the semitransparency in that case might be helpful for user
experience. Of course, quick redrawing these surfaces should also be
avoided.
Only thing I cannot explain is the mouse pointer's behavior which might truly
be caused by a bug in SDL.
It might be helpful that someone really tests this as root in a console,
after booting Linux with vga=791 kernel parameter or similar mode:
# SDL_VIDEODRIVER=fbcon /usr/games/wesnoth
The only reason to justify "wont-fix" status might be that not too many users
are interested in this, however I'm sure there are few users who'd like to
play Wesnoth in console.
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?7998>
_______________________________________________
Message sent via/by Gna!
http://gna.org/
_______________________________________________
Wesnoth-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/wesnoth-bugs
