From: Karl O. H. <ka...@hu...> - 2022-07-06 19:15:57
|
Bill Kendrick skreiv 06.07.2022 06:17: > WELL! :^D I wondered how mine could have been_so_ many revisions > (35!?) out-of-date, considering my distro is only 2 years out-of-date, > and SDL2 has been around forever.:-D > > I supposed, based on this, that we could simply call this a > known-issue, but I don't really think it's worth trying to address it. > In other words: recommend people_not_ use the SDL1.2 version of Tux > Paint with an SDL12-compat, and instead just use the SDL2.0 versions > of Tux Paint directly. I guess most users use Tux Paint packaged by their distro. And if the last official version SDL 1.2 was released 10 years ago, there are bound to be (security) issues. So distros would be wise to replace it with sdl12-compat. In other words, if they haven’t already replaced SDL 1.2 with sdl12-compat, they probably will do so. So more and more people will encounter the bugs. What’s the status of the SDL2 branch? Can it be made the default? (I have done some testing, and it seems to work fine. The only difference I can see, is that a different font is used in the UI.) BTW, it would be interesting to know what the root cause of the bug is. Is it a bug in sdl12-compat, SDL2 (since this is what sdl12-compat uses behind the scenes) or Tux Paint? If it’s a bug in sdl12-compat or SDL2, it is likely that other parts of the code could trigger it. It’s such a strange bug, in that only two brushes trigger it, and only if the selected colour is pure black. -- Karl Ove Hufthammer |