Jump to content
  • Advertisement

xllx_relient_xllx

Member
  • Content Count

    171
  • Joined

  • Last visited

Community Reputation

100 Neutral

About xllx_relient_xllx

  • Rank
    Member
  1. xllx_relient_xllx

    How much RAM do you have?

    I have 1 Terabyte. relient
  2. xllx_relient_xllx

    People of Space: Do Not Look Directly At NYC (pictures)

    Is it just me or does the building in the first picture look fake? It looks like it's straight out of a game, lol. Anyway. You took some very nice looking pictures there, pinacolada =) relient
  3. Very interesting. Thanks for the input man. relient Edit: I've succeeded in accomplishing my task by using CombineRgn and SelectClipRgn with the guidance of: Guide to WIN32 Regions by Paul Watt. Ratings and gratitude to all those who chipped in. [Edited by - xllx_relient_xllx on September 10, 2005 1:34:44 AM]
  4. Quote:Original post by Roboguy Quote:Original post by GetWindowRect Roboguy: I know a char* is a type of reference, but I am not using that, I am using char [256] not char*. Arrays are pointers. No. Arrays are NOT pointers. relient
  5. Okey dokey, thanks guys. relient
  6. Is it possible? The only function I know of that can exclude part of a region is ExcludeClipRect. The problem with it is that if you want to exclude a region of an arbitrary size othar than rectangular, you can't, because you're limited to rectangles only. Here's what I'm trying to do in my app.. I'm currently working on a hit-test button - with regions. This button is rectangular round, drawn with RoundRect(). I want to exclude this button from being painted so it will not flicker when the window is resized. Using ExcludeClipRect does not yield the desired results because it excludes a rectangular button and makes my round rect button appear to have white pointy edges. Is there any function similar to ExcludeClipRect but for excluding regions of arbitrary (not rectagular) size? If not, what other function/s could I use to accomplish this task, if any? Thanks in advance, relient
  7. xllx_relient_xllx

    The most popular programming language is...

    It's good to see C has the second spot. It's the first language I started with, the one I'm currently programming with, and it'll probably continue being my primary language for a while until I get this windows API wrapped around my head pretty good. I'm old style, I know =) relient
  8. xllx_relient_xllx

    Having problems...

    I would also like to add something else.. The diffrence between <stdlib.h> and "stdlib.h" is not such a matter of importance. Because, the former tells the compiler to look for the stdlib.h library in the compilers main library folder (or something of that sort) first, and, the latter tells it to look in the programs current directory (where your compiled files reside) first. In light of that. I think you should, like most everyone else, use < .. > for standard library's and " .. " for the ones you create. BTW: I actually meant to use < .. > in my first example =) relient
  9. xllx_relient_xllx

    Having problems...

    Are you sure you're including the C standard library "stdlib.h"? ... "#include "stdlib.h"
  10. xllx_relient_xllx

    Screen flickering

    Check this out, Flicker-Free Drawing in Windows relient
  11. xllx_relient_xllx

    Need help adding onto a character array

    This is your problem: cUsername[iStartTxt] = "."; cUsername[iStartTxt + 1] = "t"; cUsername[iStartTxt + 2] = "x"; cUsername[iStartTxt + 3] = "t"; change it to this: cUsername[iStartTxt] = '.'; cUsername[iStartTxt + 1] = 't'; cUsername[iStartTxt + 2] = 'x'; cUsername[iStartTxt + 3] = 't'; Problem: You are assigning string literals to a byte (index). That's impossible. You need character assignment, not string literal assingment. relient
  12. xllx_relient_xllx

    Gas outage

    Yeah, There might be a gas outage. I myself went to fill up my car a couple minutes ago because I don't know if tommorow there won't be no gas. long lines! It's better to be safe than sorry. relient
  13. xllx_relient_xllx

    GUI

    Free Win32 Online Tutorial Here: winprog Very good book on making GUI apps w/C here: Windows Programming relient
  14. xllx_relient_xllx

    arrays of functions [c++]

    I realize C and C++ are not entirely the same but, on many fronts, it is. On that note, I don't think the '&' is necessary for each function you need the address of since; an function automatically exposes its address with just its name. Correct me if I'm wrong. relient
  15. xllx_relient_xllx

    My Text Keeps flashing

    Where is your GamePaint() function being called from? under BeginPaint()? more source code would be helpful. This might do it: http://www.catch22.net/tuts/flicker.asp. relient.
  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!