Jump to content

  • Log In with Google      Sign In   
  • Create Account


Member Since 08 Mar 2013
Offline Last Active Aug 17 2014 08:01 PM

#5174089 pointer value

Posted by on 16 August 2014 - 08:49 AM

You are creating a pointer to an object of size float, but you are never creating memory to store the actual float. When you dereference the pointer you are accessing memory that is not available to you. Becareful also that the memory you create stays within scope for the entire duration that the function you are calling requires it or you will get an access violation.

These are difficult to track down.

#5166797 How low a level do you understand between 'SW' and HW?

Posted by on 14 July 2014 - 02:20 PM

One of things that you have to remember is that your concept of "mouse" is really just an area in video memory being written to in a certain way which would produce a recognizable image as "cursor". this is accomplished by operations at the cpu level that produce a value that the video output understands to be a certain "color". The reason why I use quotations is because these concepts dont exist to the computer, but are manufactured so that you as the user can intetact with the system to produce meaningful results. Assembly is just a human readable form of binary data, and what a higher end compiler does is translate its easier to read langauge into binary instructions for the cpu to assign memeory locations a value that can later be used to do something.

#5065137 Probably a stupid question...

Posted by on 26 May 2013 - 09:47 PM

I would imagine that each point.z is a function of the radius. As the distance from the mouse cursor increases, height decreases.

#5047253 Visualizing and writing algorithms

Posted by on 27 March 2013 - 09:17 AM

I would imagine that most architects and drafters can't imagine the entire building they are creating either.  But that doesn't stop them from doing it.


Try to remember that programming is really a translation of an idea into machine language.  The first thing i try to do is imagine and write down what it is i want to do:


I want to have a box that rotates.


then I try to imagine and write down the steps that are involved:


Intialize a window

intialize a system to draw objects

create a cube

draw the cube


I then break down each step into more involved parts.  The pattern here is to start with a simple idea and progressivly make it more detailed, before you wirte a single peice of code.


The more pedesign you do the easier it is to write your code.  I cannot emphasize this point enough.  Great buildings are designed before they are built, and are not trial and errors.  Architects don't stand at the site and direct where to put each support, only to change their mind if it doesn't work.  If you write code by trial and error, your systems will be small and trivial. But if you can learn to design your code before you start to program, you soon realize that you debug less, create more intersting and thoughtful programs, and it will be less stressful and more fun.


BTW, people who write code using one letter variables write code that is usually hard to read, difficult to debug, and probably took a long time to write.  Try using more meangingful names when designing your code.  It will make debugging less difficult, it communicates to the human much easier, and is easier to read by more people. 

#5044828 Beginner Programmer Help

Posted by on 20 March 2013 - 04:10 AM

Instead of having a seperate class to list the members of the array, it might be easier to call a mthod in your buy class which lists the items in the players array. 


Something like



//Lists the contents of the players inventory

Consider abstrqcting your classes a little more.  The buy class, which i think you intend to be some sort of portal with which the player interacts to purchase items, would not hold the inventory of the player, but would instead only add or remove from it.  A design solution might be this:



//holds items
class Inventory;

//has an inventory
class Player;

//holds items for sale
//interacts with the Inventory class that it gets from the player.
class Buy;

This way you do not need to be creating memory, but need only create objects and pass by reference.

#5041031 Little help needed

Posted by on 08 March 2013 - 07:31 PM

You can create a base class the has static members which pertain to the input aspects.  Because static memebers are visible to all the members of the class, these static members only get intialized once, but are available to all classes that derive from the input base class. 


To destroy this class you could do several things.  Call a function called TerminateInput() that shuts down all the static members, or out the code into the destructor. 


In all honesty though, input is usally just  a player thing.  I don't see why you would need to do this.