tuxpaint-devel — General discussion list for Tux Paint developers

Re: [Tuxpaint-devel] Kaleidoscope crash

[Caroline F. <car...@go...>]

On 30/11/2007, Pere Pujal i Carabantes <pe...@fo...> wrote:
>
> El ds 01 de 12 del 2007 a les 00:14 +0100, en/na Pere Pujal i Carabantes
> va escriure:
> > El dj 29 de 11 del 2007 a les 07:50 -0800, en/na Bill Kendrick va
> > escriure:
> > > Someone reported a bug about Tux Paint crashing (on an RPM-based platform,
> > > FWIW) when using the new Kaleidoscope tool:
> > >
> > >   https://sourceforge.net/tracker/?func=detail&atid=516295&aid=1840828&group_id=66938
> > >
> > > Anyone seen this? :(
> > >
> > Running with sound works fine, but without sound:
>
> BTW magic displace crashes as well without sound.
>

Running on Ubuntu gutsy without sound I get a crash with the
kaleidoscope tool when I clicked on a new colour.

I have the following from valgrind:

Process terminating with default action of signal 11 (SIGSEGV)
==19239==  Access not within mapped region at address 0x4
==19239==    at 0x40F3630: Mix_HaltChannel (mixer.c:829)
==19239==    by 0x80597F9: magic_stopsound (in /usr/local/bin/tuxpaint)
==19239==    by 0x7E39D19: kalidescope_release (in
/usr/local/lib/tuxpaint/plugins/kalidescope.so)
==19239==    by 0x8065B3C: main (in /usr/local/bin/tuxpaint)

I have the full trace I can send as I've no real clue on how to read
valgrind traces.

Caroline

Re: [Tuxpaint-devel] Kaleidoscope crash

[Pere P. i C. <pe...@fo...>]

El ds 01 de 12 del 2007 a les 00:14 +0100, en/na Pere Pujal i Carabantes
va escriure:
> El dj 29 de 11 del 2007 a les 07:50 -0800, en/na Bill Kendrick va
> escriure:
> > Someone reported a bug about Tux Paint crashing (on an RPM-based platform,
> > FWIW) when using the new Kaleidoscope tool:
> > 
> >   https://sourceforge.net/tracker/?func=detail&atid=516295&aid=1840828&group_id=66938
> > 
> > Anyone seen this? :(
> > 
> Running with sound works fine, but without sound:

BTW magic displace crashes as well without sound.

Re: [Tuxpaint-devel] Segfault with more than 127 font families detected

[Pere P. i C. <pe...@fo...>]

El dv 30 de 11 del 2007 a les 23:49 +0100, en/na Pere Pujal i Carabantes
va escriure:
> > I get this when compiling, not sure if it is related, any hints?
> > src/tuxpaint.c:15858: warning: passing argument 1 of ‘TTF_SizeUNICODE’
> > from incompatible pointer type
> > 
Forget to mention, this is with debug activated, without debug, tuxpaint
compiles and runs fine.

Re: [Tuxpaint-devel] Kaleidoscope crash

[Pere P. i C. <pe...@fo...>]

El dj 29 de 11 del 2007 a les 07:50 -0800, en/na Bill Kendrick va
escriure:
> Someone reported a bug about Tux Paint crashing (on an RPM-based platform,
> FWIW) when using the new Kaleidoscope tool:
> 
>   https://sourceforge.net/tracker/?func=detail&atid=516295&aid=1840828&group_id=66938
> 
> Anyone seen this? :(
> 
Running with sound works fine, but without sound:

tuxpaint --nosound --600x480

==555== Conditional jump or move depends on uninitialised value(s)
==555==    at 0x4084868: (within /usr/lib/libSDL-1.2.so.0.11.1)
==555==    by 0x4084FD0: (within /usr/lib/libSDL-1.2.so.0.11.1)
==555==    by 0x40539D6: SDL_PumpEvents
(in /usr/lib/libSDL-1.2.so.0.11.1)
==555==    by 0x4053EE6: SDL_PollEvent
(in /usr/lib/libSDL-1.2.so.0.11.1)
==555==    by 0x804E317: mySDL_PollEvent (tuxpaint.c:16045)
==555==    by 0x80698D3: main (tuxpaint.c:1556)
==555== 
==555== Invalid read of size 4
==555==    at 0x412C834: Mix_HaltChannel
(in /usr/lib/libSDL_mixer-1.2.so.0.2.6)
==555==    by 0x8054821: magic_stopsound (tuxpaint.c:17184)
==555==    by 0x745EC79: kalidescope_release
(in /usr/local/lib/tuxpaint/plugins/kalidescope.so)
==555==    by 0x806355E: mainloop (tuxpaint.c:3619)
==555==    by 0x8068EC6: main (tuxpaint.c:1779)
==555==  Address 0x4 is not stack'd, malloc'd or (recently) free'd
==555== 
==555== Process terminating with default action of signal 11 (SIGSEGV)
==555==  Access not within mapped region at address 0x4
==555==    at 0x412C834: Mix_HaltChannel
(in /usr/lib/libSDL_mixer-1.2.so.0.2.6)
==555==    by 0x8054821: magic_stopsound (tuxpaint.c:17184)
==555==    by 0x745EC79: kalidescope_release
(in /usr/local/lib/tuxpaint/plugins/kalidescope.so)
==555==    by 0x806355E: mainloop (tuxpaint.c:3619)
==555==    by 0x8068EC6: main (tuxpaint.c:1779)
==555== 
==555== ERROR SUMMARY: 203 errors from 23 contexts (suppressed: 414 from
1)
==555== malloc/free: in use at exit: 17,043,315 bytes in 15,374 blocks.
==555== malloc/free: 260,609 allocs, 245,235 frees, 122,713,957 bytes
allocated.
==555== For counts of detected errors, rerun with: -v
==555== searching for pointers to 15,374 not-freed blocks.
==555== checked 26,319,088 bytes.
==555== 
==555== 

Re: [Tuxpaint-devel] Segfault with more than 127 font families detected

[Pere P. i C. <pe...@fo...>]

> I get this when compiling, not sure if it is related, any hints?
> src/tuxpaint.c:15858: warning: passing argument 1 of ‘TTF_SizeUNICODE’
> from incompatible pointer type
> 
valgrind shows this amog a lot of other output

getfonthandle(394)...
Setting 'name' to fi->filename[0 (0x0)]
Which is: metalord.ttf
fi->handle was set (0x59427a0)
==29509== 
==29509== Use of uninitialised value of size 4
==29509==    at 0x4117BE1: TTF_SizeUNICODE
(in /usr/lib/libSDL_ttf-2.0.so.0.6.3)
==29509==    by 0x8063220: mainloop (tuxpaint.c:15858)
==29509==    by 0x8069C56: main (tuxpaint.c:1779)
==29509== 
==29509== Invalid read of size 4
==29509==    at 0x4117BE1: TTF_SizeUNICODE
(in /usr/lib/libSDL_ttf-2.0.so.0.6.3)
==29509==    by 0x8063220: mainloop (tuxpaint.c:15858)
==29509==    by 0x8069C56: main (tuxpaint.c:1779)
==29509==  Address 0x322F5357 is not stack'd, malloc'd or (recently)
free'd
==29509== 
==29509== Process terminating with default action of signal 11 (SIGSEGV)
==29509==  Access not within mapped region at address 0x322F5357
==29509==    at 0x4117BE1: TTF_SizeUNICODE
(in /usr/lib/libSDL_ttf-2.0.so.0.6.3)
==29509==    by 0x8063220: mainloop (tuxpaint.c:15858)
==29509==    by 0x8069C56: main (tuxpaint.c:1779)
==29509== 
==29509== ERROR SUMMARY: 401 errors from 22 contexts (suppressed: 421
from 1)
==29509== malloc/free: in use at exit: 36,794,729 bytes in 56,518
blocks.
==29509== malloc/free: 379,102 allocs, 322,584 frees, 165,859,510 bytes
allocated.
==29509== For counts of detected errors, rerun with: -v
==29509== searching for pointers to 56,518 not-freed blocks.
==29509== checked 47,540,848 bytes.
==29509== 
==29509== 

> 
> Yours
> Pere
> 
> 
> -------------------------------------------------------------------------
> SF.Net email is sponsored by: The Future of Linux Business White Paper
> from Novell.  From the desktop to the data center, Linux is going
> mainstream.  Let it simplify your IT future.
> http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
> _______________________________________________
> Tuxpaint-devel mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel

Re: [Tuxpaint-devel] SDL-pango (was bugs)

[Caroline F. <car...@go...>]

On Fri, 2007-11-30 at 14:19 -0800, Bill Kendrick wrote:
> On Fri, Nov 30, 2007 at 10:25:23PM +0000, Caroline Ford wrote:
> > I don't think Ubuntu Dapper 6.06 LTS has the SDL Pango package. It has a
> > ttf one which I have installed. According to packages.ubuntu.com
> > libsdl-pango1 first makes its appearance in Ubuntu feisty. I'm puzzled
> > why 0.9.17 compiled fine..
> 
> FYI Pango support was added to Tux Paint in this version (0.9.18).
> Do you have the -dev packages, too?
> 
> -bill!
make nopango produces more errors:

secret@eser:/media/feisty/home/secret/Music/tuxpaint-0.9.18$ make
nopango

Building with Pango DISABLED

make NOPANGOFLAG=NO_SDLPANGO SDL_PANGO_LIB=
make[1]: Entering directory
`/media/feisty/home/secret/Music/tuxpaint-0.9.18'

...Linking Tux Paint...
obj/tuxpaint.o: In function `wordwrap_text_ex':tuxpaint.c:(.text
+0x3e39): undefined reference to `SDLPango_SetDefaultColor'
:tuxpaint.c:(.text+0x3e5c): undefined reference to
`SDLPango_SetMinimumSize'
:tuxpaint.c:(.text+0x3e87): undefined reference to
`SDLPango_SetBaseDirection'
:tuxpaint.c:(.text+0x3ec0): undefined reference to
`SDLPango_SetText_GivenAlignment'
:tuxpaint.c:(.text+0x3ecd): undefined reference to
`SDLPango_CreateSurfaceDraw'
:tuxpaint.c:(.text+0x3f66): undefined reference to
`SDLPango_SetBaseDirection'
obj/tuxpaint.o: In function `render_text':tuxpaint.c:(.text+0x642d):
undefined reference to `SDLPango_SetDefaultColor'
:tuxpaint.c:(.text+0x6443): undefined reference to `SDLPango_SetText'
:tuxpaint.c:(.text+0x644d): undefined reference to
`SDLPango_CreateSurfaceDraw'
obj/tuxpaint.o: In function `do_render_cur_text':tuxpaint.c:(.text
+0xa2e9): undefined reference to `SDLPango_SetDefaultColor'
:tuxpaint.c:(.text+0xa490): undefined reference to `SDLPango_SetText'
:tuxpaint.c:(.text+0xa49d): undefined reference to
`SDLPango_CreateSurfaceDraw'
obj/tuxpaint.o: In function `main':tuxpaint.c:(.text+0x16f71): undefined
reference to `SDLPango_Init'
obj/fonts.o: In function `TuxPaint_Font_CloseFont':fonts.c:(.text+0x38):
undefined reference to `SDLPango_FreeContext'
obj/fonts.o: In function `TuxPaint_Font_OpenFont':fonts.c:(.text+0x137):
undefined reference to `SDLPango_CreateContext_GivenFontDesc'
obj/fonts.o: In function `charset_works':fonts.c:(.text+0x1ba0):
undefined reference to `SDLPango_SetDefaultColor'
:fonts.c:(.text+0x1bb9): undefined reference to `SDLPango_SetText'
:fonts.c:(.text+0x1bc6): undefined reference to
`SDLPango_CreateSurfaceDraw'
collect2: ld returned 1 exit status
make[1]: *** [tuxpaint] Error 1
make[1]: Leaving directory
`/media/feisty/home/secret/Music/tuxpaint-0.9.18'
make: *** [nopango] Error 2
secret@eser:/media/feisty/home/secret/Music/tuxpaint-0.9.18$

This is on Ubuntu Dapper. I'll switch to my feisty partition and try
there.

Caroline

Re: [Tuxpaint-devel] bugs

[Caroline F. <car...@go...>]

On Fri, 2007-11-30 at 14:19 -0800, Bill Kendrick wrote:
> On Fri, Nov 30, 2007 at 10:25:23PM +0000, Caroline Ford wrote:
> > I don't think Ubuntu Dapper 6.06 LTS has the SDL Pango package. It has a
> > ttf one which I have installed. According to packages.ubuntu.com
> > libsdl-pango1 first makes its appearance in Ubuntu feisty. I'm puzzled
> > why 0.9.17 compiled fine..
> 
> FYI Pango support was added to Tux Paint in this version (0.9.18).
> Do you have the -dev packages, too?
> 
> -bill!

Ah - I though it was added in 0.9.17.. (now this makes sense..)

Dapper (and Edgy) don't have any of the SDL-pango packages. I've
downloaded and compiled SDL_Pango but it's still not happy complaining
with:

...Linking Tux Paint...
obj/tuxpaint.o: In function `wordwrap_text_ex':tuxpaint.c:(.text
+0x3ec0): undefined reference to `SDLPango_SetText_GivenAlignment'
obj/fonts.o: In function `TuxPaint_Font_OpenFont':fonts.c:(.text+0x137):
undefined reference to `SDLPango_CreateContext_GivenFontDesc'
collect2: ld returned 1 exit status
make: *** [tuxpaint] Error 1

Caroline

Re: [Tuxpaint-devel] Segfault with more than 127 font families detected was: Tux Paint 0.9.18rc1 available

[Pere P. i C. <pe...@fo...>]

Adding this in fonts.c at line 577 tuxpaint reach to show all fonts, at
least more than 600

num_font_families += 256 ;

but crashes whith less than 127 fonts, so maybe a if then statement
willl be need.

Anyway, it crashes when typing anything but at least it shows them.

I guess there are two bugs:
one that crash when fonts>127 just by clicking on the text tool.

And the other that shows when fonts are aproximately 127>nfonts>100 and
happens randomly when writing.



I get this when compiling, not sure if it is related, any hints?
src/tuxpaint.c:15858: warning: passing argument 1 of ‘TTF_SizeUNICODE’
from incompatible pointer type


Yours
Pere

Re: [Tuxpaint-devel] bugs

[Bill K. <nb...@so...>]

On Fri, Nov 30, 2007 at 10:25:23PM +0000, Caroline Ford wrote:
> I don't think Ubuntu Dapper 6.06 LTS has the SDL Pango package. It has a
> ttf one which I have installed. According to packages.ubuntu.com
> libsdl-pango1 first makes its appearance in Ubuntu feisty. I'm puzzled
> why 0.9.17 compiled fine..

FYI Pango support was added to Tux Paint in this version (0.9.18).
Do you have the -dev packages, too?

-bill!

Re: [Tuxpaint-devel] bugs

[Caroline F. <car...@go...>]

On Thu, 2007-11-29 at 09:12 -0800, Bill Kendrick wrote:

> 
> Yes, it'd be a good habit.  Tux Paint's Quality Assurance is close to
> nil these days, sadly.  <:^Z  When's someone gonna pay me to do this
> project fulltime? ;^)
> 
> 
> > Second of all, stamps don't work with 15 BPP.

I know this is a little late but I can't seem to get 0.9.18 to compile
on Ubuntu Dapper. 0.9.17 compiled fine, but 0.9.18 complains with:

/usr/bin/ld: cannot find -lSDL_Pango
collect2: ld returned 1 exit status
make: *** [tuxpaint] Error 1

I don't think Ubuntu Dapper 6.06 LTS has the SDL Pango package. It has a
ttf one which I have installed. According to packages.ubuntu.com
libsdl-pango1 first makes its appearance in Ubuntu feisty. I'm puzzled
why 0.9.17 compiled fine..

Caroline

[Tuxpaint-devel] Tux Paint 0.9.18 OS X testers needed

[Bill K. <nb...@so...>]

0.9.18 was PowerPC only, and even then, had some issues running.
Martin (with help) has put together a new build that seems to work
on 10.4 Intel systems.

  ftp://ftp.tuxpaint.org/unix/x/tuxpaint/testbuilds/macosx/

(Currently, it's "tuxpaint-0.9.18.03-macosx.dmg")


Can people here please try it out and let us know if it works, and
what version of OS X you're using, and on what platform (Intel or PowerPC)?

If it DOESN'T work, try running it from a Terminal, and let us know
if any error messages appear:

  Launch the "Terminal" application in your Mac's "Utilities" folder.
  Right-click (or [Control]+click) on the "Tux Paint" application icon.
  Choose "Show Package Contents" from the menu that appears.
  Open up the "Contents" folder, and then 'MacOS" folder within.
  You will see a single file named "Tux Paint".
  Drag the "Tux Paint" icon into the Terminal window, and press [Return].
  As Tux Paint will attempt to launch, let us know if anything gets printed
    out to the Terminal window. (Copy/Paste it into your reply email to us)

Thanks!

-- 
-bill!
bi...@ne...
http://www.newbreedsoftware.com/

Re: [Tuxpaint-devel] bugs

[Caroline F. <car...@go...>]

On Thu, 2007-11-29 at 09:12 -0800, Bill Kendrick wrote:
> On Mon, Nov 26, 2007 at 12:50:51AM -0500, Albert Cahalan wrote:
> > First of all, I got a crash.
> 
> Where'bouts?
> 
> 
> > Those of you with fast machines might want to make a habit of
> > running tuxpaint under valgrind.
> 
> Yes, it'd be a good habit.  Tux Paint's Quality Assurance is close to
> nil these days, sadly.  <:^Z  When's someone gonna pay me to do this
> project fulltime? ;^)

is there a way of "making" tuxpaint with debug symbols in?

Caroline

[Tuxpaint-devel] passing -128 to malloc considered harmful

[Albert C. <aca...@gm...>]

==981== Thread 1:
==981== Conditional jump or move depends on uninitialised value(s)
==981==    at 0x804CA48: stamp_xor (tuxpaint.c:14862)
==981==
==981== Conditional jump or move depends on uninitialised value(s)
==981==    at 0x404BA1D: (within /usr/lib/libSDL-1.2.so.0.11.1)
==981==    by 0x4043716: (within /usr/lib/libSDL-1.2.so.0.11.1)
==981==    by 0x405B3C3: SDL_LowerBlit (in /usr/lib/libSDL-1.2.so.0.11.1)
==981==    by 0x405B600: SDL_UpperBlit (in /usr/lib/libSDL-1.2.so.0.11.1)
==981==    by 0x80616E1: mainloop (tuxpaint.c:4705)
==981==
==981== Conditional jump or move depends on uninitialised value(s)
==981==    at 0x404BA99: (within /usr/lib/libSDL-1.2.so.0.11.1)
==981==    by 0x4043716: (within /usr/lib/libSDL-1.2.so.0.11.1)
==981==    by 0x405B3C3: SDL_LowerBlit (in /usr/lib/libSDL-1.2.so.0.11.1)
==981==    by 0x405B600: SDL_UpperBlit (in /usr/lib/libSDL-1.2.so.0.11.1)
==981==    by 0x80616E1: mainloop (tuxpaint.c:4705)
==981==
==981== Conditional jump or move depends on uninitialised value(s)
==981==    at 0x404BB06: (within /usr/lib/libSDL-1.2.so.0.11.1)
==981==    by 0x4043716: (within /usr/lib/libSDL-1.2.so.0.11.1)
==981==    by 0x405B3C3: SDL_LowerBlit (in /usr/lib/libSDL-1.2.so.0.11.1)
==981==    by 0x405B600: SDL_UpperBlit (in /usr/lib/libSDL-1.2.so.0.11.1)
==981==    by 0x80616E1: mainloop (tuxpaint.c:4705)
==981==
==981== Conditional jump or move depends on uninitialised value(s)
==981==    at 0x404BB73: (within /usr/lib/libSDL-1.2.so.0.11.1)
==981==    by 0x4043716: (within /usr/lib/libSDL-1.2.so.0.11.1)
==981==    by 0x405B3C3: SDL_LowerBlit (in /usr/lib/libSDL-1.2.so.0.11.1)
==981==    by 0x405B600: SDL_UpperBlit (in /usr/lib/libSDL-1.2.so.0.11.1)
==981==    by 0x80616E1: mainloop (tuxpaint.c:4705)
==981==
==981== Conditional jump or move depends on uninitialised value(s)
==981==    at 0x406B17B: (within /usr/lib/libSDL-1.2.so.0.11.1)
==981==    by 0x406BB09: (within /usr/lib/libSDL-1.2.so.0.11.1)
==981==    by 0x4037EF6: SDL_PumpEvents (in /usr/lib/libSDL-1.2.so.0.11.1)
==981==    by 0x4038406: SDL_PollEvent (in /usr/lib/libSDL-1.2.so.0.11.1)
==981==    by 0x804D026: mySDL_PollEvent (tuxpaint.c:16045)
==981==
==981== Conditional jump or move depends on uninitialised value(s)
==981==    at 0x406B196: (within /usr/lib/libSDL-1.2.so.0.11.1)
==981==    by 0x406BB09: (within /usr/lib/libSDL-1.2.so.0.11.1)
==981==    by 0x4037EF6: SDL_PumpEvents (in /usr/lib/libSDL-1.2.so.0.11.1)
==981==    by 0x4038406: SDL_PollEvent (in /usr/lib/libSDL-1.2.so.0.11.1)
==981==    by 0x804D026: mySDL_PollEvent (tuxpaint.c:16045)
==981==
==981== Warning: silly arg (-128) to malloc()

[Tuxpaint-devel] tuxpaint crash: read past a 141056-byte malloc

[Albert C. <aca...@gm...>]

==1937== Thread 1:
==1937== Conditional jump or move depends on uninitialised value(s)
==1937==    at 0x406B17B: (within /usr/lib/libSDL-1.2.so.0.11.1)
==1937==    by 0x406BB09: (within /usr/lib/libSDL-1.2.so.0.11.1)
==1937==    by 0x4037EF6: SDL_PumpEvents (in /usr/lib/libSDL-1.2.so.0.11.1)
==1937==    by 0x4038406: SDL_PollEvent (in /usr/lib/libSDL-1.2.so.0.11.1)
==1937==    by 0x804D7ED: mySDL_PollEvent (in /home/olpc/tuxpaint/tuxpaint)
==1937==
==1937== Invalid read of size 8
==1937==    at 0x40639FD: (within /usr/lib/libSDL-1.2.so.0.11.1)
==1937==    by 0xE7: ???
==1937==  Address 0x97B8E60 is 8 bytes after a block of size 141,056 alloc'd
==1937==    at 0x40224E5: malloc (vg_replace_malloc.c:149)
==1937==    by 0x405BC83: SDL_CreateRGBSurface (in
/usr/lib/libSDL-1.2.so.0.11.1)
==1937==    by 0x804E62A: thumbnail2 (in /home/olpc/tuxpaint/tuxpaint)
==1937==
==1937== Invalid read of size 8
==1937==    at 0x4063A04: (within /usr/lib/libSDL-1.2.so.0.11.1)
==1937==    by 0xE7: ???
==1937==  Address 0x97B8E58 is 0 bytes after a block of size 141,056 alloc'd
==1937==    at 0x40224E5: malloc (vg_replace_malloc.c:149)
==1937==    by 0x405BC83: SDL_CreateRGBSurface (in
/usr/lib/libSDL-1.2.so.0.11.1)
==1937==    by 0x804E62A: thumbnail2 (in /home/olpc/tuxpaint/tuxpaint)

My screen size is 1200x900, 2 bytes per pixel.
This is 32-bit x86 with MMX enabled.

Re: [Tuxpaint-devel] Kaleidoscope crash

[Albert C. <aca...@gm...>]

Running tuxpaint under valgrind, I got this:

==1937== Conditional jump or move depends on uninitialised value(s)
==1937==    at 0x406B17B: (within /usr/lib/libSDL-1.2.so.0.11.1)
==1937==    by 0x406BB09: (within /usr/lib/libSDL-1.2.so.0.11.1)
==1937==    by 0x4037EF6: SDL_PumpEvents (in /usr/lib/libSDL-1.2.so.0.11.1)
==1937==    by 0x4038406: SDL_PollEvent (in /usr/lib/libSDL-1.2.so.0.11.1)
==1937==    by 0x804D7ED: mySDL_PollEvent (in /home/olpc/tuxpaint/tuxpaint)

I guess I didn't have debug info in the build. Doing this
on the XO hardware is really hard because the CPU is slow.
Anyway, mySDL_PollEvent has a problem.

Re: [Tuxpaint-devel] bugs

[Albert C. <aca...@gm...>]

On Nov 29, 2007 12:21 PM, Bill Kendrick <nb...@so...> wrote:
> On Mon, Nov 26, 2007 at 12:50:51AM -0500, Albert Cahalan wrote:
> >
> > Third of all, there are two fonts that are terribly
> > defective. The clone of Comic Sans gives me
> > weird stuff when I type non-ASCII stuff like the
> > multiplication symbol. There is another font
> > that won't even do ASCII right.
>
> ta.ttf, the Tamil font.  We should consider only loading
> locale fonts and showing them in the Text tool when that
> locale is being used...

I doubt that font is even good for Tamil.

Fonts are supposed to have Unicode tables.
The OS is supposed to let you type in Unicode.
One should be able to mix Tamil with ASCII.

If that font is used on a modern system, do you
just get rectangular boxes when you type Tamil?
Typing ASCII to get Tamil is wrong. You should type
Tamil if you want Tamil.

Fontforge can be used to recode the font.

Re: [Tuxpaint-devel] bugs

[Bill K. <nb...@so...>]

On Mon, Nov 26, 2007 at 12:50:51AM -0500, Albert Cahalan wrote:
> 
> Third of all, there are two fonts that are terribly
> defective. The clone of Comic Sans gives me
> weird stuff when I type non-ASCII stuff like the
> multiplication symbol. There is another font
> that won't even do ASCII right.

ta.ttf, the Tamil font.  We should consider only loading
locale fonts and showing them in the Text tool when that
locale is being used...

-bill!

Cc'ing tuxpaint-i18n


-- 
-bill!
bi...@ne...
http://www.newbreedsoftware.com/

Re: [Tuxpaint-devel] bugs

[Bill K. <nb...@so...>]

On Mon, Nov 26, 2007 at 12:50:51AM -0500, Albert Cahalan wrote:
> First of all, I got a crash.

Where'bouts?


> Those of you with fast machines might want to make a habit of
> running tuxpaint under valgrind.

Yes, it'd be a good habit.  Tux Paint's Quality Assurance is close to
nil these days, sadly.  <:^Z  When's someone gonna pay me to do this
project fulltime? ;^)


> Second of all, stamps don't work with 15 BPP.

Ah, I see... unscaling.  I'll make a note.


> Third of all, there are two fonts that are terribly
> defective. The clone of Comic Sans gives me
> weird stuff when I type non-ASCII stuff like the
> multiplication symbol. There is another font
> that won't even do ASCII right.

Happen to know their filenames offhand?  (I'll dig, in the meantime.)

Thanks!

-- 
-bill!
bi...@ne...
http://www.newbreedsoftware.com/

Re: [Tuxpaint-devel] Kaleidoscope crash

[Bill K. <nb...@so...>]

On Thu, Nov 29, 2007 at 04:20:25PM +0000, Caroline Ford wrote:
> On Ubuntu bug trackers we normally ask for back traces etc. Is there a
> point in doing so here? I've no idea how debug version of packages are
> put together etc.

A backtrace was actually included (as an attachment). :)

-- 
-bill!
bi...@ne...
http://www.newbreedsoftware.com/

Re: [Tuxpaint-devel] Kaleidoscope crash

[Caroline F. <car...@go...>]

On Thu, 2007-11-29 at 07:50 -0800, Bill Kendrick wrote:
> Someone reported a bug about Tux Paint crashing (on an RPM-based platform,
> FWIW) when using the new Kaleidoscope tool:
> 
>   https://sourceforge.net/tracker/?func=detail&atid=516295&aid=1840828&group_id=66938
> 
> Anyone seen this? :(
> 
No but I'll see if I can reproduce.

On Ubuntu bug trackers we normally ask for back traces etc. Is there a
point in doing so here? I've no idea how debug version of packages are
put together etc.

Caroline

[Tuxpaint-devel] Kaleidoscope crash

[Bill K. <nb...@so...>]

Someone reported a bug about Tux Paint crashing (on an RPM-based platform,
FWIW) when using the new Kaleidoscope tool:

  https://sourceforge.net/tracker/?func=detail&atid=516295&aid=1840828&group_id=66938

Anyone seen this? :(

-- 
-bill!
bi...@ne...
http://www.newbreedsoftware.com/

[Tuxpaint-devel] bugs

[Albert C. <aca...@gm...>]

First of all, I got a crash. Those of you with
fast machines might want to make a habit
of running tuxpaint under valgrind.

Second of all, stamps don't work with 15 BPP.

Third of all, there are two fonts that are terribly
defective. The clone of Comic Sans gives me
weird stuff when I type non-ASCII stuff like the
multiplication symbol. There is another font
that won't even do ASCII right.

[Tuxpaint-devel] Tux Paint RPMs for Fedora CORE 2 thru Fedora 9

[Bill K. <nb...@so...>]

Shin-Ichi has provided RPM packaged for i386-compatible systems running
Fedora CORE Linux 2 thru 6 and Fedora Linux 7, 8 and 9:

  http://www.tuxpaint.org/download/linux-rpm/

Thx and enjoy!

-- 
-bill!
bi...@ne...
http://www.newbreedsoftware.com/

Re: [Tuxpaint-devel] About starters (was Tux Paint 0.9.18 coming this week)

[Pere P. i C. <pe...@fo...>]

El dc 21 de 11 del 2007 a les 10:45 -0800, en Bill Kendrick va escriure:
> On Wed, Nov 21, 2007 at 07:39:49PM +0100, Pere Pujal i Carabantes wrote:

> 
> > For the dotted ones, I'd prefer they were on the back, so you can paint
> > over, but renaming as *-back.png tuxpaint doesnt show them :(
> 
> Yeah, you'd need a completely transparent non-"-back" PNG to go with them,

Thanks for the tip, now they show right on back.
I've had to compose the backgrounds over white as they were transparent
and Tuxpaint showed over black.
 
Has any of them any chance to reach Tuxpaint?
If so, is better to draw the numbers with some specific font? or is fine
handwrited as they are?


Thanks
Pere

Re: [Tuxpaint-devel] Changes for OLPC XO (was Re: Tux Paint 0.9.18 coming this week)

[Albert C. <aca...@gm...>]

On Nov 21, 2007 1:32 PM, Bill Kendrick <nb...@so...> wrote:
> On Wed, Nov 21, 2007 at 01:49:59AM -0500, Albert Cahalan wrote:

> > I'd like to check in lots of OLPC-related changes as soon as I get
> > them done, hopefully this weekend. It really can't go into this
> > release though.
>
> Excellent.  A number of people have contacted me, recently, about Tux Paint
> on the XO.  Glad to hear you're looking into it again!  Out of curiosity,

For 2/3 of a year I just put it aside.

There is a Python cabal that loves non-standard undocumented
interfaces that are only provided via Python libraries, so it has
been like pulling teeth to expose the non-Python interface and/or
get things switched over to being more standard.

Also the hardware changed. The old hardware had 50 MB left
over after all the bloated Python code got loaded. Now there is
an additional 128 MB, though of course more Python bloat too.
I didn't get the new hardware until just recently.

> what kind of changes will you be making to Tux Paint?  Will they be XO-specific
> (via #ifdef, for example), or broader changes?

It's a mix. Some things will need #ifdef, and some things not.
Stuff falls into two catagories, hardware and UI. You may have
noticed two types of #ifdef I added; "SUGAR" is for the UI.

The screen is 1200x900, but blurry. There is often a key on
the keyboard for multiply and divide, with the gradeschool
math symbols. The CPU has 3dNow! instructions. The CPU
does floating point faster if set to 32-bit; I think this may
require setting a mode bit in the CPU. The speakers are
strong from 3500 Hz to 4000 Hz, but weak below 600 Hz
and nothing below about 300 Hz.

The system UI expects to hand files to Tux Paint. It is not
normally allowed for an unpriviliged program to request a
specific file. Looking around in $HOME is blocked. There is
some per-program persistant storage that I can use, but
really I'm supposed to let the system UI handle the files.

The quit button is kind of forbidden, being replaced by
a stop button that kind of does a suspend. The idea is
that one can always keep going from where they last
were. So "stop" is really "save and quit w/o asking".
One can later select the saved data from the system UI
and ask to resume the activity.

I don't even like thinking about scrolling and zooming,
but they might be needed for this slightly older audience.
The competition, a normal wimpy paint program written
in Python, does have those features.

I think we're missing many of the languages from
south-east Asia, western Africa, the Middle East,
India, and the rural areas of South America. A few
of these languages present nightmare-level rendering
difficulties. Letters go in spirals, sort of, with the
whole bunch of them wildly mutating as you add
each additional letter. (connected, of course)

Currently OLPC is not using dead keys. Accents get
typed after the letter they modify. So you get the letter
"A", render it, and then find out later that the user adds
a ring on top... and then the user adds a second accent,
and maybe a bunch more! You only know the letter is
done once a non-accent letter is typed.

I'm going to need to place an X window property on the
window. I hope SDL lets me get at the low-level stuff.

Got any ideas for sharing? Apps are supposed to be
able to be usable by multiple people at once. I guess
the ideal would be that all users edit the same image,
but that doesn't sound easy to code.

There is a camera that does 640x480.

There is a 7-level button for brush size. It maps to
the keys F5 through F8, plus 3 in-between keys.

The mouse pointer is terribly inaccurate.

Programs can't see each other. It seems that the
stamps must go in the main package.

If much of this makes no sense, remember that
the OLPC is designed to let users share hostile
code with each other. Bad programs can't swipe
your files, upload your picture somewhere, etc.

> I'd like to add some fixed-point math support to the Magic API at some point,
> but it'd probably be best if I used some existing library for that, rather
> than try to roll my own.  Anyone have recommendations?  (The best would
> be something that could somehow be compiled using floating-point for systems
> with FPUs, and compiled as fixed-point for systems that don't (Nokia, Zaurus,
> etc.))

I was thinking I might do that and/or assembly.
Any part in particular that needs to be optimized?

> > BTW, I'm not so sure pre-XP is anything these days.
> > If nothing else, the hardware itself will have died.
>
> Heh, yeah.  I wouldn't be surprised to hear that many schools are still
> running older stuff these days.  (When I was in high school, we had nothing
> but Apple IIe systems, aside from the random Mac, until 1992!  I have no
> idea how soon the lab full of 486es running Windows 3.1 was replaced when
> Win95 came out...)

It's not like that. Those old Apple IIe systems were tough.
They lacked: hard disk, CPU fan, power supply fan, CD

Also, malware makes old Windows systems hopeless.