tuxpaint-devel — General discussion list for Tux Paint developers

[Tuxpaint-devel] Comments about some magic tools

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

Hi all! 

Some bugs, enhancement requests and ideas:


Enhancement requests:

Folder: Can be improved if click is used to select the corner, then drag
to were he want the corner go, do some calculation about how a sheet
should be plyed to get the corner there. You also can do a rough
"preview" like flower does. Then, in mouse release, draw it.

Some maths suposing 0,0 corner having to go to 100,200:
half point between 0,0 and 100,200 = (0+100)/2,(0+200)/2 = 50,100
Here you should check if there will not be a "by zero" division, then
0x point = 0,(50 + 100*100/50) = 0,250
0y point = (100 + 50*50/100),0 = 125,0

so you end up with lines 
from 125,0 to 100,200
from 125,0 to 0,250
from 0,250 to 100,200



Black and white: Can be converted to "color and white" just picking the
color like other magic tools do. The same is valid for threshold.



Bugs:

Flower, just noticed this: if you draw a horizontal flower you don't get
leafs.

Jigsaw, works right at 800x600, but at 640x480 I get pieces cutted at
the edge, and in bigger screens, the jigsaw is covering just the 800x600
topleft portion of the image

 

An idea for new magic tools:
I've been always fascined by those animations were a plant grows from
zero, or a flower opens, or clouds running accross the sky, etc. Theese
can be implemented in two ways:

a)  A sequence of some images, starting on mouse click, showing the next
image each second and drawing the image present on mouse release.
Depending on the animations, they can be positioned on mouse click or
aligned to a edge of the draw

b)  A computed animation like some screensavers do, starting on mouse
click and ending on mouse release. Even the direction of the animation
(when possible) can be controlled on mouse drag.



Hope this helps
Pere

Re: [Tuxpaint-devel] Rails plugin release

[foo-script <foo...@o2...>]

Luc, what version of Rails are you using? Primary (from szn.republika.pl), or CVS?
 
 _Bool is a cstdlib data type, it came with C99, so your compiler should recognize this type.

 For sure, I will change it to Uint8.

Newest version at: http://szn.republika.pl/tuxpaint-magic-rails.tar.gz
This release throws no warnings about comparison between signed and unsigned types. I've also written about idea's author.

Best,
Adam

Dnia 14 lipca 2008 13:07 Begasus <Be...@sk...> napisał(a):

> Trying to compile the rail tool on gcc 2.95 (BeOS) fails on line 162 and 
> line 260 (probly due to the use of the _Bool function).
> The other warnings are something shown in the BlackAndWhite tool also.
> 
> Greetings,
> 
> Luc
> 
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:22: warning: no 
> previous prototype for `rails_api_version'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:27: warning: no 
> previous prototype for `rails_modes'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
> `rails_modes':
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:26: warning: unused 
> parameter `api'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:26: warning: unused 
> parameter `which'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: At top level:
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:32: warning: no 
> previous prototype for `rails_set_color'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
> `rails_set_color':
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:31: warning: unused 
> parameter `api'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:31: warning: unused 
> parameter `r'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:31: warning: unused 
> parameter `g'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:31: warning: unused 
> parameter `b'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: At top level:
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:36: warning: no 
> previous prototype for `rails_init'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:60: warning: no 
> previous prototype for `rails_get_tool_count'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
> `rails_get_tool_count':
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:59: warning: unused 
> parameter `api'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: At top level:
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:65: warning: no 
> previous prototype for `rails_get_icon'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
> `rails_get_icon':
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:64: warning: unused 
> parameter `which'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: At top level:
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:74: warning: no 
> previous prototype for `rails_get_name'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
> `rails_get_name':
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:74: warning: unused 
> parameter `api'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:74: warning: unused 
> parameter `which'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: At top level:
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:76: warning: no 
> previous prototype for `rails_get_description'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
> `rails_get_description':
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:76: warning: unused 
> parameter `api'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:76: warning: unused 
> parameter `which'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:76: warning: unused 
> parameter `mode'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: At top level:
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:78: warning: no 
> previous prototype for `rails_requires_colors'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
> `rails_requires_colors':
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:78: warning: unused 
> parameter `api'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:78: warning: unused 
> parameter `which'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: At top level:
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:83: warning: no 
> previous prototype for `rails_release'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
> `rails_release':
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:80: warning: unused 
> parameter `api'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:80: warning: unused 
> parameter `which'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:81: warning: unused 
> parameter `canvas'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:81: warning: unused 
> parameter `snapshot'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:82: warning: unused 
> parameter `x'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:82: warning: unused 
> parameter `y'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:82: warning: unused 
> parameter `update_rect'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: At top level:
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:87: warning: no 
> previous prototype for `rails_shutdown'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
> `rails_shutdown':
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:86: warning: unused 
> parameter `api'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: At top level:
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:104: warning: no 
> previous prototype for `rails_switchin'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
> `rails_switchin':
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:103: warning: unused 
> parameter `api'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:103: warning: unused 
> parameter `which'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:103: warning: unused 
> parameter `mode'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: At top level:
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:117: warning: no 
> previous prototype for `rails_switchout'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
> `rails_switchout':
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:116: warning: unused 
> parameter `api'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:116: warning: unused 
> parameter `which'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:116: warning: unused 
> parameter `mode'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:116: warning: unused 
> parameter `canvas'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: At top level:
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:134: warning: no 
> previous prototype for `rails_get_segment'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:146: warning: no 
> previous prototype for `rails_extract_coords_from_segment'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:162: parse error 
> before `_Bool'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:164: warning: function 
> declaration isn't a prototype
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
> `rails_rotate':
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:165: `ptr' undeclared 
> (first use in this function)
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:165: (Each undeclared 
> identifier is reported only once
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:165: for each function 
> it appears in.)
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:168: `direction' 
> undeclared (first use in this function)
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:170: `dest' undeclared 
> (first use in this function)
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:172: `src' undeclared 
> (first use in this function)
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: At top level:
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:186: warning: no 
> previous prototype for `rails_click'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
> `rails_click':
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:183: warning: unused 
> parameter `mode'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
> `rails_select_image':
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:198: warning: 
> comparison between signed and unsigned
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
> `rails_draw':
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:260: `_Bool' 
> undeclared (first use in this function)
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:260: parse error 
> before `use_temp'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:262: `use_temp' 
> undeclared (first use in this function)
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:254: warning: unused 
> parameter `which'
> /boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:254: warning: unused 
> parameter `last'
> make: *** [magic/rails.so] Error 1
> 
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> _______________________________________________
> Tuxpaint-devel mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel
> 

Re: [Tuxpaint-devel] Rails plugin release

[Begasus <Be...@sk...>]

Trying to compile the rail tool on gcc 2.95 (BeOS) fails on line 162 and 
line 260 (probly due to the use of the _Bool function).
The other warnings are something shown in the BlackAndWhite tool also.

Greetings,

Luc

/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:22: warning: no 
previous prototype for `rails_api_version'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:27: warning: no 
previous prototype for `rails_modes'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
`rails_modes':
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:26: warning: unused 
parameter `api'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:26: warning: unused 
parameter `which'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: At top level:
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:32: warning: no 
previous prototype for `rails_set_color'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
`rails_set_color':
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:31: warning: unused 
parameter `api'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:31: warning: unused 
parameter `r'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:31: warning: unused 
parameter `g'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:31: warning: unused 
parameter `b'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: At top level:
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:36: warning: no 
previous prototype for `rails_init'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:60: warning: no 
previous prototype for `rails_get_tool_count'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
`rails_get_tool_count':
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:59: warning: unused 
parameter `api'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: At top level:
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:65: warning: no 
previous prototype for `rails_get_icon'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
`rails_get_icon':
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:64: warning: unused 
parameter `which'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: At top level:
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:74: warning: no 
previous prototype for `rails_get_name'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
`rails_get_name':
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:74: warning: unused 
parameter `api'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:74: warning: unused 
parameter `which'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: At top level:
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:76: warning: no 
previous prototype for `rails_get_description'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
`rails_get_description':
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:76: warning: unused 
parameter `api'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:76: warning: unused 
parameter `which'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:76: warning: unused 
parameter `mode'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: At top level:
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:78: warning: no 
previous prototype for `rails_requires_colors'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
`rails_requires_colors':
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:78: warning: unused 
parameter `api'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:78: warning: unused 
parameter `which'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: At top level:
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:83: warning: no 
previous prototype for `rails_release'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
`rails_release':
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:80: warning: unused 
parameter `api'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:80: warning: unused 
parameter `which'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:81: warning: unused 
parameter `canvas'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:81: warning: unused 
parameter `snapshot'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:82: warning: unused 
parameter `x'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:82: warning: unused 
parameter `y'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:82: warning: unused 
parameter `update_rect'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: At top level:
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:87: warning: no 
previous prototype for `rails_shutdown'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
`rails_shutdown':
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:86: warning: unused 
parameter `api'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: At top level:
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:104: warning: no 
previous prototype for `rails_switchin'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
`rails_switchin':
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:103: warning: unused 
parameter `api'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:103: warning: unused 
parameter `which'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:103: warning: unused 
parameter `mode'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: At top level:
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:117: warning: no 
previous prototype for `rails_switchout'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
`rails_switchout':
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:116: warning: unused 
parameter `api'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:116: warning: unused 
parameter `which'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:116: warning: unused 
parameter `mode'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:116: warning: unused 
parameter `canvas'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: At top level:
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:134: warning: no 
previous prototype for `rails_get_segment'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:146: warning: no 
previous prototype for `rails_extract_coords_from_segment'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:162: parse error 
before `_Bool'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:164: warning: function 
declaration isn't a prototype
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
`rails_rotate':
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:165: `ptr' undeclared 
(first use in this function)
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:165: (Each undeclared 
identifier is reported only once
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:165: for each function 
it appears in.)
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:168: `direction' 
undeclared (first use in this function)
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:170: `dest' undeclared 
(first use in this function)
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:172: `src' undeclared 
(first use in this function)
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: At top level:
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:186: warning: no 
previous prototype for `rails_click'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
`rails_click':
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:183: warning: unused 
parameter `mode'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
`rails_select_image':
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:198: warning: 
comparison between signed and unsigned
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c: In function 
`rails_draw':
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:260: `_Bool' 
undeclared (first use in this function)
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:260: parse error 
before `use_temp'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:262: `use_temp' 
undeclared (first use in this function)
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:254: warning: unused 
parameter `which'
/boot/home/Desktop/develop/tuxpaint/magic/src/rails.c:254: warning: unused 
parameter `last'
make: *** [magic/rails.so] Error 1

Re: [Tuxpaint-devel] Rails plugin release

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

On Sun, Jul 13, 2008 at 11:55:51PM -0700, Bill Kendrick wrote:
> Oh, well, maybe I don't understand how it's SUPPOSED to work.
> As I clicked and dragged, it seemed to draw randomly-changing directions
> of track.

I see what's going on.  I figured it'd be a paint kind of tool, like
Bricks.  But I guess what's happening is as I clicked and dragged, it
was changing the orientation of the rail (North/South to East/West and back)
multiple times, very quickly, as I dragged across its cell.


> > BTW: A short howto:
> > 
> > double click same area: insert an image or rotate existing one.
> > 
> > When you want to make a "crossroad" just set all the rails' directions correctly and then click the area between.

I'm finding the crossroad feature _very_ difficult to use.  I got it to
work once, so far.  (I _am_ in bed, and using a laptop with a trackpad,
but still... not a bad way to simulate a young kid!)

I'd suggest re-thinking the UI.  Have it draw tracks as you drag around.
If your mouse is moving top-to-bottom (north to south, so to speak),
it draws up-and-down rails.  If you suddenly start going sideways, it
draws a curved track at the bottom of the up-down tracks, and then
starts painting left-right tracks.

If you ever double-back over your previous tracks, that's when the
crossroads effect would take place.

I haven't looked closely at your code yet, but I think it'd be a simple
matter of setting two (or more) of four bits/flags for each cell, one
for each of the cardinal directions: up, down, left, right.

If your mouse comes into a cell from the right, and leaves it to the left,
then the left and right bits get set.  When it goes to (re)draw the
piece of track in that cell, it should draw a left-right track.

I think possibilities of what kind of rail to draw would boil down to simply:

  Bits  Shape

    LR   --
         --

  UD     ||
         ||

   D R   /-
         ||

   DL    -\
         ||

  U  R   ||
         \-

  U L    ||
         -/

And when you cross over:

  UDLR   ++
         ++

   DLR   =\/=
          ||

  U LR    ||
         =/\=

  UDL     ||
         -/|
         -\|
          ||

  UD R    ||
          |\-
          |/-
          ||

Whew!

-- 
-bill!
"Tux Paint" - free children's drawing software for Windows / Mac OS X / Linux!
Download it today!  http://www.tuxpaint.org/

Re: [Tuxpaint-devel] Rails plugin release

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

On Mon, Jul 14, 2008 at 03:55:11AM +0200, foo-script wrote:
> Dnia 14 lipca 2008 2:42 Bill Kendrick <nb...@so...> napisa??(a):
> 
> > Unfortunately, so far, it doesn't seem to _work_ very well, but
> > you can work on that next. :)
> 
> why?

Oh, well, maybe I don't understand how it's SUPPOSED to work.
As I clicked and dragged, it seemed to draw randomly-changing directions
of track.


> BTW: A short howto:
> 
> double click same area: insert an image or rotate existing one.
> 
> When you want to make a "crossroad" just set all the rails' directions correctly and then click the area between.

Oh, er.  Ok, I guess I'll need to give it another go.  I don't think I like
the idea of double-clicking, but we'll see how it works.

Thanks,

-- 
-bill!
"Tux Paint" - free children's drawing software for Windows / Mac OS X / Linux!
Download it today!  http://www.tuxpaint.org/

Re: [Tuxpaint-devel] Rails plugin release

[foo-script <foo...@o2...>]

Dnia 14 lipca 2008 2:42 Bill Kendrick <nb...@so...> napisał(a):

> Unfortunately, so far, it doesn't seem to _work_ very well, but
> you can work on that next. :)

why?


BTW: A short howto:

double click same area: insert an image or rotate existing one.

When you want to make a "crossroad" just set all the rails' directions correctly and then click the area between.

Re: [Tuxpaint-devel] Rails plugin release

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

On Sun, Jul 13, 2008 at 05:15:56PM -0700, Bill Kendrick wrote:
> 
> So far I get a segmentation fault when I try to run it.
> I'll see if I can debug. :)

Found it.  switchin() and switchout() were lacking 'mode' args.

I've corrected that, changed the description text a little, and
committed it to CVS.

Unfortunately, so far, it doesn't seem to _work_ very well, but
you can work on that next. :)

Thanks,

-- 
-bill!
"Tux Paint" - free children's drawing software for Windows / Mac OS X / Linux!
Download it today!  http://www.tuxpaint.org/

Re: [Tuxpaint-devel] Rails plugin release

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

On Sun, Jul 13, 2008 at 09:55:14PM +0200, foo-script wrote:
> Due to Pere Pujal i Carabantes idea I created "Rails" plugin.
> 
> Available at: http://szn.republika.pl/tuxpaint-magic-rails.tar.gz
> 
> Comments, ideas, bugs(?) are invited.

So far I get a segmentation fault when I try to run it.
I'll see if I can debug. :)


-- 
-bill!
"Tux Paint" - free children's drawing software for Windows / Mac OS X / Linux!
Download it today!  http://www.tuxpaint.org/

Re: [Tuxpaint-devel] switchin() switchout()

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

On Sun, Jul 13, 2008 at 04:56:57PM +0200, foo-script wrote:
> I see many useful applications of these functions, but I can't solve this:
> Tuxpaint calls switchout() when user decides to create new image, but also calls this function when user uses Undo. Can I avoid calling switchout() when Undo?
> 
> Using switchin() I create an important data - table. Each image can have quite different values in this variable, so each switchout() frees this data (in case of creating new image). Undo also calls switchout() - that's makes problem.

The way it works right now is useful for cases where you don't want to leave
junk on the canvas when the user is 'done' (either temporarily, or
permanently) with your Magic tool.

Albert's history stuff (see his post) is interesting and likely useful.
Another thing that could help is to tell you, in switchin()/switchout(),
what's going on.

-- 
-bill!
"Tux Paint" - free children's drawing software for Windows / Mac OS X / Linux!
Download it today!  http://www.tuxpaint.org/

[Tuxpaint-devel] Rails plugin release

[foo-script <foo...@o2...>]

Due to Pere Pujal i Carabantes idea I created "Rails" plugin.

Available at: http://szn.republika.pl/tuxpaint-magic-rails.tar.gz

Comments, ideas, bugs(?) are invited.

Enjoy! :)


Best,
Adam

Re: [Tuxpaint-devel] switchin() switchout()

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

On Sun, Jul 13, 2008 at 10:56 AM, foo-script <foo...@o2...> wrote:

> Using switchin() I create an important data - table. Each image can have quite different values in this variable, so each switchout() frees this data (in case of creating new image). Undo also calls switchout() - that's makes problem.

It sounds like these are not the functions you are looking for.

Perhaps you'd be better off with the ability to attach your
table to the history stack. There could be a destructor
function that gets called when the history level is freed.

[Tuxpaint-devel] switchin() switchout()

[foo-script <foo...@o2...>]

I see many useful applications of these functions, but I can't solve this:
Tuxpaint calls switchout() when user decides to create new image, but also calls this function when user uses Undo. Can I avoid calling switchout() when Undo?

Using switchin() I create an important data - table. Each image can have quite different values in this variable, so each switchout() frees this data (in case of creating new image). Undo also calls switchout() - that's makes problem.

Best,
Adam

[Tuxpaint-devel] [Fwd] Re: check file 'tuxpaint.exe' ? * ( Mac here )

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

Someone forwarded me a copy of 'tuxpaint.exe' that they received,
with the following note.

(It appeared to be _just_ the EXE of the program that gets launched on
Windows, _not_ the installer app that John P. produces).

> Mac 10.3.9 -- no tuxpaint program --
>
> someone sent me the file i'm sending you:
>
> as soon as it downloaded from the email, all folders
> on desktop piled onto the harddrive icon, while it
> materialized in the download folder.
>
> what is this supposed to be doing, Please ?

I told them I have no idea what Macs would do when they encounter a
Win32 EXE these days, so I'm passing the question along to this list,
in case anyone here knows.  Any idea why their icons would apparently
move around...?  (I have neither a Mac nor a Windows box up and running,
so I can't test it.)

In the meantime, I directed them to the Tux Paint download page for Mac OS X,
of course, and they seem to like the program. :)

Just curious.  Thanks in advance,

-- 
-bill!
"Tux Paint" - free children's drawing software for Windows / Mac OS X / Linux!
Download it today!  http://www.tuxpaint.org/

[Tuxpaint-devel] GSoC Status

[Bruno D. <bru...@gm...>]

Hi people,

Luc asked me to send an email about my project status. I've
implemented 2 new options: open file and save file. I draw the toolbar
icons myself, but I'm not very skilled =)
I've taken 2 screenshots:
- http://littlechina.org/~dilly/Tuxpaint-Screenshot-Save.png
- http://littlechina.org/~dilly/TuxPaint-Screenshot-Open.png

I'm using gtk+ toolkit. It's working fine in ubuntu hardy, but if who
uses others platforms could test it and give me feedback... it will be
great!

A version to be tested is ready in alternative repo, so if you want to
test it (you will need a svn client):

svn checkout http://tuxpaint-system-file-dialogs.googlecode.com/svn/trunk/
tuxpaint-system-file-dialogs-
read-only

To compile it, use the target gtk
$make gtk

Surely, you will need libgtk. I'm using libgtk2.0

I've got 2 question:
- should the default open/save tools be hide when open-file/save-file are shown?
- it's ok to keep the target gtk or I should use another approach?

Any suggestion is welcome, and what I will do next depends on the feedback.

Cheers

Re: [Tuxpaint-devel] Confetti + Fold: newest version

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

On Thu, Jul 10, 2008 at 03:28:16PM +0200, foo-script wrote:
> I just put the updated version of Fold tool and Confetti tool.
> This version supports the newest API.
> 
> http://szn.republika.pl/tuxpaint-magic-GSOC.tar.gz

Looking good.  For the corner folding, might I suggest adding a kind of
shadow gradient to the corner that gets pulled up, so it doesn't look as
much like a flat fold (or just a triangle :) )?

Something like this (but your shape is way better :) )

  http://bp0.blogger.com/_skCowMS4EAg/RlWyDXmcUnI/AAAAAAAAAD0/hHjSzSS6Dcw/s400/Redju_folded_paper_template1_promo.jpg

Of course, it wouldn't be pure grey, it would be a darkening (and perhaps
lightening) of the pixels from the original canvas that you're already
currently 'peeling'.


I've added your C source and PNG images to CVS.  I'm going to grant you CVS
write access.  Please pull Tux Paint from CVS using your SF.net account,
and then you can commit changes back to the repository as you make them.

** REMEMBER TO INCLUDE USEFUL COMMIT LOGS! :)

People will be able to see your CVS commits via the tuxpaint-cvs mailing list
and the CVS RSS feed, as well as, of course, by browsing CVS Web on SF.net. :)

Thanks!

-- 
-bill!
"Tux Paint" - free children's drawing software for Windows / Mac OS X / Linux!
Download it today!  http://www.tuxpaint.org/

[Tuxpaint-devel] Confetti + Fold: newest version

[foo-script <foo...@o2...>]

I just put the updated version of Fold tool and Confetti tool.
This version supports the newest API.

http://szn.republika.pl/tuxpaint-magic-GSOC.tar.gz


Best,
Adam

Re: [Tuxpaint-devel] [(almost)Solved]Plugins crash

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

On Thu, Jul 10, 2008 at 04:44:01AM +0200, foo-script wrote:
> 
>  I found the solution. At the beginning "canvas" is only a pointer to SDL_Surface, without any data. So we have to blit snapshot/last (source image) to canvas manually. This is new requirement and all the tools in today release support this change.

I'm not sure I fully understand what you're saying here.  If you're talking
about the SDL_Surface* being '0x1' instead of a valid pointer, this has
to do with a missing 'int mode' argument in your _click() function.


> There's only one problem. Bill, I have reviewed the docs, magic tools codes, CHANGES and tp_magic_example.c .
> 
> This new feature/requirement is _undocumented_. Even example tool (provided with Tuxpaint)  crashes the program when I try to use this tool.

Apologies, you're right, I didn't get to the docs yet.  (The new 'mode'
args ARE mentioned specifically in CHANGES, though :) )


> Please, mention anywhere about this. 
> 
> Sorry for this mails attack, but I after 3 hrs of searching a bug/libs updating & recompiling I just had to ask you :)

Heh, I even though I mentioned it in a previous email to you. Sorry! :)

-- 
-bill!
"Tux Paint" - free children's drawing software for Windows / Mac OS X / Linux!
Download it today!  http://www.tuxpaint.org/

Re: [Tuxpaint-devel] Plugins crash

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

Note that _click() and _get_description() now receive an 'int mode'
after 'int which', so be sure to update your functions to receive them!

-bill!


On Thu, Jul 10, 2008 at 03:52:12AM +0200, foo-script wrote:
> After today upgrade to newest CVS-version my plugins just stopped working.
> Each attemption of use my plugin ends with crash. I run tuxpaint under gdb and here's sample result (fold.c):
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1218578752 (LWP 24142)]
> 0xb6859083 in confetti_click (api=0x824e378, which=0, canvas=0x1,
>     snapshot=0x811c0e8, x=135351072, y=424, update_rect=0x7d)
>     at magic/src/confetti.c:106
> 106             return SDL_MapRGB(canvas->format, temp_r, temp_g, temp_b);
> 
> 
> This is first time when any occurs when program is running. Same code, but without switchin() , switchout() and modes() functions, on previous CVS-release was working really fine . As I noticed all these crashes are caused by any instruction using "canvas" surface. Isn't it bizzare that the address of canvas is 1? And why x value is so incredible high?
> 
> No matter of _modes() the result is the same.
> 
> SDL, SDL_ttf, SDL_image: newest, stable
> Tuxpaint: CVS, 2008.07.10-0.9.21 - downloaded today.
> 
> Any ideas?
> 
> Best,
> Adam
> 
> 
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> _______________________________________________
> Tuxpaint-devel mailing list
> Tux...@li...
> https://lists.sourceforge.net/lists/listinfo/tuxpaint-devel

-- 
-bill!
"Tux Paint" - free children's drawing software for Windows / Mac OS X / Linux!
Download it today!  http://www.tuxpaint.org/

[Tuxpaint-devel] [(almost)Solved]Plugins crash

[foo-script <foo...@o2...>]

 I found the solution. At the beginning "canvas" is only a pointer to SDL_Surface, without any data. So we have to blit snapshot/last (source image) to canvas manually. This is new requirement and all the tools in today release support this change.

There's only one problem. Bill, I have reviewed the docs, magic tools codes, CHANGES and tp_magic_example.c .

This new feature/requirement is _undocumented_. Even example tool (provided with Tuxpaint)  crashes the program when I try to use this tool.

Please, mention anywhere about this. 

Sorry for this mails attack, but I after 3 hrs of searching a bug/libs updating & recompiling I just had to ask you :)

Best,
Adam

[Tuxpaint-devel] Plugins crash:Supplement

[foo-script <foo...@o2...>]

Of course it was confetti.c file, not fold.c
In this source I used inline function (to make code more optimized), so in gdb listing you can see that _click() function returns anything. It doesn't. It was just gdb mistake caused by inline function call. After removing such functions we get:
"0xb6862c90 in confetti_get_new_color (ptr=0x824e378, canvas=0x1)
    at magic/src/confetti.c:105
105             return SDL_MapRGB(canvas->format, temp_r, temp_g, temp_b);
"

Again :/

Best,
Adam

[Tuxpaint-devel] Plugins crash

[foo-script <foo...@o2...>]

After today upgrade to newest CVS-version my plugins just stopped working.
Each attemption of use my plugin ends with crash. I run tuxpaint under gdb and here's sample result (fold.c):

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1218578752 (LWP 24142)]
0xb6859083 in confetti_click (api=0x824e378, which=0, canvas=0x1,
    snapshot=0x811c0e8, x=135351072, y=424, update_rect=0x7d)
    at magic/src/confetti.c:106
106             return SDL_MapRGB(canvas->format, temp_r, temp_g, temp_b);


This is first time when any occurs when program is running. Same code, but without switchin() , switchout() and modes() functions, on previous CVS-release was working really fine . As I noticed all these crashes are caused by any instruction using "canvas" surface. Isn't it bizzare that the address of canvas is 1? And why x value is so incredible high?

No matter of _modes() the result is the same.

SDL, SDL_ttf, SDL_image: newest, stable
Tuxpaint: CVS, 2008.07.10-0.9.21 - downloaded today.

Any ideas?

Best,
Adam

Re: [Tuxpaint-devel] Magic API updated: switchin() and switchout()

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

On Tue, Jul 8, 2008 at 8:35 PM, Bill Kendrick <nb...@so...> wrote:

> I understand the jist, but could you give me an example chunk of code
> (within a Magic tool) where this is used, so I can make sure I do it
> properly?  (I don't want to forget to do this, which I will in a matter
> of days :^/ )

magic/src/bricks.c

static unsigned char *map;
...
  if (!api->button_down())
  {
    if (map)
      free(map);
    // the "+ 3" allows for both ends and misalignment
    x_count = (canvas->w + nominal_width - 1) / nominal_width + 3;
    y_count = (canvas->h + nominal_height - 1) / nominal_height + 3;
    map = calloc(x_count, y_count);
  }


That "map" variable should be associated with the history.
Better code would be:

When we draw a brick, we start by creating a brick map.
If the top history item is the same size brick, then we do
a memcpy() of that. Otherwise, we zero-initialize the map.
We then push the history stack, attach our brick map to
the newly added history entry, and attach a destructor
(a function pointer) to the newly added history entry.
When the oldest history entry is freed by Tux Paint, the
core code calls that function pointer. That then lets the
magic plug-in free the brick map.

Note that a callback is needed because some tools may
wish to use a linked list or tree. It would be nice to have
a function pointer that is compatible with free() though, so
that magic plug-ins can directly use that. For plug-ins that
do not store state in the history, there should not be any
need to do anything. Tux Paint can initialize the pointer to
a dummy function.

Re: [Tuxpaint-devel] Magic API updated: modes (paint vs. entire-image)

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

On Tue, Jul 08, 2008 at 07:53:52PM -0700, Bill Kendrick wrote:
> 
> Tux Paint's Magic tools now have _modes() functions, which act
> similar to the "_requires_colors()" function.  It tells Tux Paint what
> mode(s) the tool can work in.

Furthermore, "_get_description()" is now given a 'mode' value
(and called that many more times, if your plugin's tool(s) supports
more than one tool).

This lets your tool have diff. descriptions depending on the mode
(i.e., "Click and drag to ..." vs. "Click to ... the entire picture.")

-bill!

[Tuxpaint-devel] Magic API updated: modes (paint vs. entire-image)

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

Tux Paint's Magic tools now have _modes() functions, which act
similar to the "_requires_colors()" function.  It tells Tux Paint what
mode(s) the tool can work in.

The current options are simply:

  MODE_PAINT
  MODE_FULLSCREEN

and, of course, both:

  MODE_PAINT | MODE_FULLSCREEN

Users are presented with two buttons, below the scroling list of tools,
one for each of these modes.  (One or the other appears greyed out if your
Magic tool only supports one mode.  "Flowers", for example, will only ever
do MODE_PAINT, I think.)

I expanded the "Negative" tool to utilize this new feature.
A number of other tools could benefit, too.


For simplifyng the UI for younger kids, you can use "--nomagiccontrols"
(or "nomagiccontrols=yes" in the config file.)

(I still need to add an option to control this feature in Tux Paint Config.)

It's in CVS.  Enjoy!

-- 
-bill!
"Tux Paint" - free children's drawing software for Windows / Mac OS X / Linux!
Download it today!  http://www.tuxpaint.org/

Re: [Tuxpaint-devel] Magic API updated: switchin() and switchout()

[foo-script <foo...@o2...>]

This question was to Albert but maybe... (I'm not sure of this solution)
Albert, if I use this signals incorrect let me know please.

void plugin_set_color(magic_api * api, Uint8 r, Uint8 g, Uint8 b)
allow you to fetch RGB values, but doesn't allow to create unified color value using SDL_MapRGB, but switchin() does.

void plugin_switchin(magic_api * api, int which, SDL_Surface * canvas)
{
	plugin_color=SDL_MapRGB(canvas->format, plugin_r, plugin_g, plugin_b);
}


Dnia 9 lipca 2008 2:35 Bill Kendrick <nb...@so...> napisał(a):

> 
> I understand the jist, but could you give me an example chunk of code
> (within a Magic tool) where this is used, so I can make sure I do it
> properly?  (I don't want to forget to do this, which I will in a matter
> of days :^/ )
> 
> -bill!