[GEM-dev] [pix_texture]: how to make 'mode 0' default?

Roman Haefeli reduzierer at yahoo.de
Sat Sep 29 04:35:31 CEST 2007


On Fri, 2007-09-28 at 02:52 +0200, Roman Haefeli wrote:
> On Tue, 2007-09-25 at 12:55 +0200, IOhannes m zmoelnig wrote:
> > oops sorry i was unclear here: i thought, in addition to applying my 
> > first patch, you should change the lines mentioned.
> 
> np. 
> 
> ok, i resume:
> 
> testprocess:
> ------------------------------------------------------
> 
> - create/get Gem binary
> 
> - start pd -lib Gem
> 
> - load pix_texture-help.pd
> 
> - load image (png 3-channel image of dimensions 454 x 459 px)
> 
> - try both modes 'mode 0/1'
> 
> - gather data from [pix_texture]'s second outlet.
> 
> 
> 
> results:
> ---------------------------------------------------------
> 
> 
> TEST A
> 
> with gem binary from sources of todays cvs checkout:
> 
> [pix_texture]: using mode 0:GL_TEXTURE_2D
> print: 1 0.886719 0.896484 3553 0
> 
> [pix_texture]: using mode 1:GL_TEXTURE_RECTANGLE_ARB
> print: 1 0.886719 0.896484 3553 0
> 
> 
> ...............................................
> 
> 
> TEST B
> 
> with gem binary made of sources more than two months old. 
> 
> cvs update -D 2007-07-12 -dP
> 
> when turning rendering on, i get:
> 
> GL: invalid enumerant
> 
> no image, respectively only one pixel of the image is displayed
> image becomes visible after sending 'mode 0'.
> 
> [pix_texture]: using mode 0:GL_TEXTURE_2D
> print: 1 0.886719 0.896484 3553 0
> 
> [pix_texture]: using mode 1:GL_TEXTURE_RECTANGLE_EXT
> print: 1 0.886719 0.896484 3553 0
> 
> 
> ................................................
> 
> 
> TEST C
> 
> gem binary compiled with todays sources and applied patch AND manually
> changed lines as proposed in previous mail of this thread.
> 
> 
> sorry, i just realized, i cannot apply the patch anymore. i get:
> 
> roman at yoyo:~/pd-cvs/Gem-cvs/src$ patch -p0 < pixtexture.diff 
> patching file Base/GemMan.cpp
> Hunk #1 succeeded at 1172 (offset -2 lines).
> Hunk #2 succeeded at 1196 (offset -2 lines).
> patching file Pixes/pix_movieNEW.h
> patching file Pixes/pix_texture.cpp
> Hunk #2 FAILED at 64.
> Hunk #3 FAILED at 97.
> Hunk #4 FAILED at 138.
> Hunk #5 succeeded at 189 (offset -1 lines).
> Hunk #6 FAILED at 231.
> Hunk #7 succeeded at 264 (offset -3 lines).
> Hunk #8 succeeded at 332 (offset -8 lines).
> Hunk #9 succeeded at 357 (offset -8 lines).
> Hunk #10 succeeded at 435 with fuzz 2 (offset -8 lines).
> Hunk #11 succeeded at 556 (offset -8 lines).
> Hunk #12 FAILED at 672.
> 5 out of 12 hunks FAILED -- saving rejects to file
> Pixes/pix_texture.cpp.rej
> patching file Pixes/pix_texture.h
> 
> 
> it seems, that pix_texture.cpp was changed since the patch was created.
> does the patch needs an update as well?
> 
geeezz..... sorry for complicating things so much. it turned out, that i
was still using the old (2007-07-12) sources. since i was not sure, how
to revert to actual state (is that what is meant by 'reset
stickiness'?), i just did everything from scratch:

TEST C

- i deleted whole tree
- i checked out a fresh sources
- i applied IOhannes' patch from a previous post
- i manually edited Base/GemMan.cpp according to a previous post of
IOhannes
- i deleted Manips/glsl*.cpp
- aclocal && autoconf && ./configure && make

(i hope i did everything right this time)

but the test results don't seem to contain any new information, i still
get:

[pix_texture]: using mode 0: TEXTURE_2D
print: 1 0.886719 0.896484 3553 0

[pix_texture]: using mode 1: TEXTURE_RECTANGLE
print: 1 0.886719 0.896484 3553 0

..........................................................


yo, IOhannes, in case i still did something wrong, please give me
detailed instructions, even if they seem to be redundant in your eyes.
otherwise you need to tell me what to do else. an interactive session 
(#dataflow) would probably be cool.

and sorry for the delay.

roman







	
		
___________________________________________________________ 
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de





More information about the GEM-dev mailing list