Re: [Tuxpaint-devel] SDL issue when opening at 640x480 (Was Re: Tux Paint - Canvas Size)

[Doug S. <do...@do...>]

Bill,

I added the windib system variable and then started TuxPaint, 
TuxMath, & TuxTyping both windowed and full screen.  I only checked 
each to see if it stayed running or not.  The results are essentially 
the same as before: TuxPaint works both ways. (I do have the Native 
bit set in the config.) Tuxmath and TuxTyping both work in the 
windowed mode, but flash the non-optimum screen setting error msg and 
them minimize themselves to the taskbar.

Here are my notes from the tests. (It formats better in TextPad, 
which wraps long lines to the same indentation as the start of the 
line.) I have included the contents of stderr.txt and stdout.txt.  In 
some cases these files existed in the application directories, left 
over from my earlier running of the programs.

Any suggestions?

Regards,
Doug


=
-2152 Added new System EnvironmentVariable per
     http://www.tuxpaint.org/docs/windib/
     Variable name: SDL_VIDEODRIVER
     Variable value: windib
-2155 Checked TuxPaint logs
     Try running Tux Paint again. If no window appears, check the 
directory containing the "TuxPaint.exe" file (typically in 
"C:\Program Files\TuxPaint\") for files named "stdout.txt" and/or 
"stderr.txt" and examine them for errors. (Windows NotePad or WordPad 
should be suitable for opening these files.

-2203 TuxPaint
     stderr.txt 20080319-2322.txt
         Warning: Asking for native screensize in a window. Ignoring.
         [This was probably from earlier tests with full-screen but 
not setting Native bit.]
     Windowed: ok
     Full screen: ok
     No stderr.txt in c:\program files\TuxPaint

-2207 TuxMath
     stdout.txt 20080322-1813.txt
         scandir : findIn orign=data/missions/lessons
         scandir : findIn processed=data\missions\lessons\*
         scandir : findFile=.
         scandir : findFile=..
         scandir : findFile=lesson00
         scandir : findFile=lesson01
         scandir : findFile=lesson02
         [I removed the lines from lesson03 to 45.]
         scandir : findFile=lesson46
         scandir : findFile=lesson47
         scandir : findFile=less
     Windowed: ok
     Full screen: Same innappropriate screen settings error
         Program sets minimized to task bar
         R-click in task bar: no means to quit
         Used Task Manager to kill it
     stderr.txt 20080322-2207.txt Contains
         Could not find high score table.
         [This is the same as prior to running now.]
     stdout.txt 20080322-2207.txt
         Could not find high score table.
-2212 TuxTyping
     stdout.txt 20080321-2312.txt
         enter unload_menu()
     Windowed: ok
     Full screen: Same innappropriate screen settings error
         Program sets minimized to task bar
         R-click in task bar: no means to quit
         Used Task Manager to kill it
     stderr.txt 20080322-2212.txt
         Cannot support UTF-8, ASCII-only words will be used
         [This is the same as prior to running now.]
     stdout.txt 20080322-2212.txt
         [empty]

===



At 18:37 3/22/2008, Bill Kendrick wrote:

>On Sat, Mar 22, 2008 at 10:19:24PM +0000, Caroline Ford wrote:
> >    I can open using the windowed shortcut (with the -w switch) and get a
> >    normal 640x48 window.  My problem occurs when I try to open with the
> >    full-screen shortcut (with the -f switch).  TuxPain works fine 
> windowed or
> >    full screen, but it has a config program that lets me set the Native bit
> >    that tells it to detect and use my screen size when opening 
> full screen.
> >    Since TuxPaint works correctly, I don't think it is a graphics driver on
> >    my PC.  It seems like TuxMath and TuxTyping are not detecting my screen
> >    size.  If I don't set the native bit in TuxPaint and try to open full
> >    screen, I get the same behavior as I am describing for TuxMath and
> >    TuxTyping.  Is there a command line option for setting the native bit?
>
>Doug, the only reason Tux Paint works is that it's able to resize itself
>to something other than 640x480.  You said that Tux Paint _did_ have that
>issue, when you didn't have the Native Screen Size setting checked.
>
>The other apps insist on 640x480, and therefore that's _all_ they can do.
>
>SDL on Windows can either use DirectX or WinDIB as a back-end.
>Recently, they changed the default.
>
>You can set it yourself, by following these instructions from the Tux Paint
>site (this tells you how to run using WinDIB, versus DirectX, which was the
>SDL default; eventually, Tux Paint overrode that setting internally, and
>eventually the SDL folks changed the default to be WinDIB on their end).
>
>   http://www.tuxpaint.org/docs/windib/
>
>Try using both "directx" and "windib" as the setting, and see if any
>of the apps work with one or the other.
>
>Good luck!
>
>--
>-bill!
>bi...@ne...
>http://www.newbreedsoftware.com/