Welcome, Guest. Please login or register. Did you miss your activation email?

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - workmad3

Pages: [1] 2 3 ... 5
1
General / Obfuscating Ruby
« on: July 09, 2008, 09:16:13 am »
unfortunately no there isn't yet. Too much of the ruby language relies on run-time compilation of source code and people haven't figured out a way to compile it and keep those features yet.

And no, I don't know of any way of encrypting or hiding the source code, but with a little ingenuity or googleing you shouldn't have a problem with obfuscating it :)

2
Network / Packet Send and Receive
« on: June 30, 2008, 12:05:07 pm »
Well, you are sending the packet twice... that may be a problem.

3
General / Anoying problem
« on: June 30, 2008, 12:00:06 pm »
have you done something like build a release build of your code with the debug libraries linked this time?

4
Feature requests / Outlined text
« on: June 26, 2008, 09:14:05 pm »
Quote from: "Laurent"
To get the corners, you can still draw the string 8 times :D


I think it would still look wrong with curved characters (like S, C, etc. :))

5
Network / Client identification
« on: June 26, 2008, 09:02:32 pm »
sizeof(Buffer) is perfectly valid and suitable there. sizeof when used on a static sized array will give you the size of the type (in this case, char so 1) multiplied by the size of the array.

Using strlen() would actually be less suitable for sending network packets. If you used a union like this:
Code: [Select]

template<typename T>
union conversion
{
   char cRep[sizeof(T)];
   T nRep;
};

in order to package arbitrary classes as network data then using strlen would be an error as it would bomb out if you had any 0 values in the class.

6
Window / [Solved] undefined reference to `_gluPerspective@32'
« on: June 26, 2008, 08:52:52 pm »
Are you using SFML 1.2 or SFML 1.3? With  1.2, you need to include the headers yourself, and with 1.3 you just need Window.hpp.

7
Feature requests / Outlined text
« on: June 26, 2008, 08:29:33 pm »
Most professional games will use custom bitmap fonts designed for their UI and outlined as necessary with that :)
And if you want to generate some, then I can recommend this:
http://www.codehead.co.uk/cbfg/

8
Graphics / [Solved] Opacity for Sprites?!
« on: June 26, 2008, 09:21:11 am »
do a google search on alpha transparency to see what he means :)

9
Feature requests / Outlined text
« on: June 26, 2008, 09:19:32 am »
I've been thinking about the drawing in all directions and realised there is a slight problem with it... it won't get corners, which would leave the outline looking very bad, especially at higher font sizes if the outline size increases with it.

10
Feature requests / Outlined text
« on: June 25, 2008, 03:05:28 pm »
hmm... thinking about that, it would require a bit of trickery to change the letter spacing in the smaller version in order to centre them. Still, that's the method I would consider doing as it only involves some (probably minor) calculations and 2 string draws.

The other option I can think of that may be possible is to see if you could get a pixel shader to outline the text. That would manage it in a single pass rather than 2 (or 5) but would mean that with outlines, no other postFX effects could be done on text (unless it was exposed as a postFX function that could be called in another effect). It may not be possible to do entirely in pixel shaders though (the method I can think of would require having a vertex shader that creates a varying variable that can be used in the pixel shader to detect distance from the edge of the character)

11
Feature requests / Outlined text
« on: June 25, 2008, 02:47:50 pm »
surely the 'brute force' method would really be to draw the string twice. Once with the outline colour at the requested size, and once on top of it at about 0.2p smaller in the text colour to create the outline?

12
General / Anoying problem
« on: June 25, 2008, 12:41:24 pm »
About the only extra thing I know is that if you are using collections from the standard library (and sometimes even raw arrays) then a frequent debug feature is for them to be padded so as to detect things like overflows. If these are allocated with the release allocator and then released with the debug destructor (it can happen. Getting the correct destructor called when there are 2 versions in different dlls is difficult to say the least) then the memory appears corrupted because the padding characters aren't correct and you get that lovely error.

13
General / Anoying problem
« on: June 25, 2008, 11:52:58 am »
Not sure why you didn't get the problem before. I started with 1.2 (built myself with VS2008) and always had it if I link incorrectly.

I guess it is up to Laurent to reveal if he has added any particularly interesting stuff in debug builds that would cause this now :)

14
General / Anoying problem
« on: June 25, 2008, 09:28:55 am »
I had that for a while... it turned out to be I was linking a bedug build of my program to the release build of the library, which alters memory layouts etc :)

15
General / [Solved] Designing questions
« on: June 17, 2008, 01:46:30 pm »
I'll send it over this evening when I get home from work then :)

Pages: [1] 2 3 ... 5