| |
| |
| |
|
Page: 1 2 3
Comments:
<0> what would cause two different programs (spline computations) to produce slightly different out puts
<1> the fact that the programs are different...
<0> yes
<0> the outputs are about 1 percent different
<1> so?
<1> what is the 'difference' between both programs?
<0> you saying so what big deal?
<1> maybe the difference between both programs is one has return x; and the other has return x*1.01; - unless you give me more information
<0> the one difference is that on program computes the new tangents each time i add a point and the other computes the points/tangents all at once
<2> I have a window open. I'd like to open another. I'm given to believe this is not possible. Are there any hacks or workarounds?
<1> I never tried myself
<1> but I think with SDL it's Impossible to open more than once window
<1> s/once/one
<2> I think I'll have to move my work to something else then. That means a rewrite of quite a bit of code *sigh*
<3> Why didn't he just spawn two processes?
<3> (duh)
<1> ugh... this code sux
<1> and each time I search for something else on the code, I find something else that ****s
<4> PovAddict: I use GLUT *shudder* for multi-windowed apps.
<1> :O!
<4> It's no SDL, but at least it works =)
<1> that's how the whole BOINC code seems to be... 'at least it works'
<1> some things seem a miracle that they work
<1> ugh, reading stuff from a socket in a single read() because "they are small enough that they probably won't be fragmented by the network"
<1> all *newbie* how-to-do-socket-programming tutorials insist on not doing that
<4> Eek.
<4> We all know that recv and send boundaries match up exactly, right? ;)
<1> I want to help fixing some "broken" stuff (in practice they work *most* of the time so devs dont care)
<1> but I dont know where to even start
<1> We all know that recv and send boundaries match up exactly <- suuuure
<1> also, the main dev said I shouldn't care for two messages coming on a single recv() because that will never happen
<1> the other end BLOCKS waiting for a reply, so never two requests will be sent without a reply in the middle
<1> problem is, GUI is hanged during that block :|
<1> and that request is done once a second
<1> that explains why GUI is laggy when connected remotely
<1> and with "laggy" I mean "so damned unresponsive"
<0> man textbooks are expensive
<0> i bought the games gems books today
<1> there are man textbooks?
<1> :P
<0> yuck yuck
<0> PovAddict, i wish i had witty comeback
<1> lol
<1> sometimes I do, not always...
<1> btw, man textbooks would be books with all the Unix manpages?
<0> now those i have seen
<0> back in the day i remember falling asleep with the sunos manuals
<5> the return of SDL_GetVideoSurface is 100% equivalent to the one of SDL_SetVideoMode, or can they vary?
<6> http://pastebin.com/872621
<6> http://pastebin.com/872629 <-- the code that produce all those errors
<6> my personal guess is that I need to include other libraries, judging by the undefined references to things
<1> pastebin.com is the slowest thing on earth
<6> yeah, right now, it is
<6> I spammed it with the source like 8 times
<6> thinking it didn't go through, because it took so long
<1> right now?
<6> alternative?
<1> I dont remember it fast, since like 1 year ago
<6> usually it pops right up
<6> must be the hours I use it
<5> rafb.net/paste/ is what I always use
<1> psyklops: show how you're compiling it
<6> http://rafb.net/p/I1aH9o27.html
<6> oh yeah...
<1> pastebin finally loaded now
<6> just running gcc SDLpractice.cpp
<6> nothing else..
<5> ...
<1> use g++ instead ;)
<6> hm, didn't know the difference
<1> and add SDL libraries OF COURSE
<5> lol
<1> well gcc is for C, g++ is for C++
<6> still errors
<1> and if you're using <string>...
<1> -lSDL
<5> psyklops: and add SDL libraries OF COURSE
<1> (ugh)
<6> thought having the #include <SDL.h> in there would have done that
<1> that's not a library, that's the headers
<1> you shouldn't be using SDL if you don't have that basic knowledge about C programming
<6> I'm about 3 weeks into my beginning C++ cl***.. we aren't up to this yet
<5> ok, so on my SDL cl***es wrapper
<5> should I have a getSurface on the Surface cl*** that returns the SDL surface or should I use friends?
<6> well thanks for the help
<1> yuriks: I dont know how 'friend' works on C++
<5> PovAddict: it's basically "frinds can look at private stuff"
<1> yuriks: but why would you need to get the SDL_surface if everything is nicely wrapped?
<5> "friends*"
<1> for derived cl***es?
<5> PovAddict: well, SDL_BlitSurface still needs the SDL_Surface for some stuff ;)
<1> so it would be surface->blit(other surface,x,y,w,h) right?
<1> lol -> http://qdb.us/74054
<5> actually, you're right I don't need either
<1> btw if you need *derived* cl***es to access native SDL_Surface, remember 'protected' :)
<5> docwiki is down, that ****s =(
<1> !mirrors
<1> d.a.m.n.i.y
<1> s/y$/t
<5> damnit? =P
<1> yea
<5> "I f*** hate people that f***ng censor their own f*** words!"
<1> s/\*\*\*/uck
<5> =]
<1> LOL
<1> "Update! A fix for the fix is now available as 0.2.1-rc1. 0.2 fixed the original bug but introduced another bug which coincidentally acted exactly the same."
<5> PovAddict: haha, what is that? lmao
<1> http://burningsmell.org/SDL_reader/
<5> oh, a txt reader, fascinating =]
<7> is it particularly hard/easy to write something for/under linux and then cross compile it to execute under win
<7> using sdl or course
<7> im mostly talking about using the graphics capabilities
<8> well considering you'll probably want to test it in windows you might be better off compiling it there
<7> ok but i have a working linux system
<7> and am more interested in dev'ing under linux
<8> compiling in both environments I meant
<5> http://burningsmell.org/sandisk/
<7> i am happy to reboot to test it
<5> crap that DOES look ugly
<5> I think my blit function has some hundreds of variants =P
<5> bouma: yes it is possible
<5> but considering the trouble you may as well install it on windows
<5> develop on Linux and when it comes the time to test and release binaries reboot into windows to compile and do some testing
<5> and they all just call the mother function
<8> only thing I would advise against is testing it in wine, I had a lot of apps that worked ok in wine but wouldn't run at all in windows
<7> does this mean cygwin ?
<5> http://burningsmell.org/faf/ < this does look handy
<5> bouma: no, it means mingw
<5> random C question:
<5> SDL_Surface *dst_surf = (dst ? dst : SDL_GetVideoSurface());
<5> is there any shortcut to that so I don't need to type dst twice? =]
<1> doubt it
<1> well in fact yes...
<1> SDL_Surface *dst_surf = dst; if(!dst_surf) dst_surf=SDL_GetVideoSurface();
<5> well, that's kind of "non-shortcut" but, heh
<1> "so I don't need to type dst twice"
<1> I know it's even longer
<1> :P
<1> although you cant type dst_surf without dst
<1> here's a way to type dst once:
<1> #define d dst
<1> SDL_Surface *dst_surf = (dst ? dst : SDL_GetVideoSurface());
<1> DAMN
<1> #define d dst
<1> SDL_Surface *dst_surf = (d ? d : SDL_GetVideoSurface());
<1> there
<5> lol
<0> an itty-bitty web server?
<7> ok
<7> im really clutching at straws heere
Return to
#sdl
or
Go to some related
logs:
MC broomy
obsification perl
gentoo cross-gcc-stage1
yup.rpm suse
#openzaurus
#suse
downlaod 30M
samba debian c compiler cannot create executables
#lisp
install SABnzbd ubuntu
|
|