Frustrating problem with my game... - Page 2

SimReality · 05-17-2008, 05:48 PM

Quote:

Originally Posted by Link9228

Hey guys, thanks for the help. I'm really close to getting all the kinks out. And those of you up top, you don't have to be so negative towards people. Yes it's helpful to post what your code is when you are having problems, but it doesn't necessarily mean we are retarded people who don't know how to program and we are trying to get everyone else to do the work for us. This is the only problem we have had, and the program's almost done

We're not trying to be negative or mean. But honestly if the poster had spent a few days (or even hours) reading some C# tutorials (not XNA, mind you) you would have likely been able to solve this problem on your own. This won't be the last either. You will likely encounter lots of these little problems because you fundamentally don't understand the language. It's ok; you are just beginning programming. But please do yourself a favor and learn C# first.

I'll throw this link in here as the advice I gave someone on the XNA forums earlier: http://nick.gravelyn.com/2008/05/17/...ke-zune-games/.

Link9228 · 05-17-2008, 06:36 PM

ok, but it took me a while to figure out how to fix it too, and i do know the language. I've read 2 books on c# programming, though that was a while ago. And i know i personally learn more from code debugging than when i'm reading what something does and then coding examples

SimReality · 05-18-2008, 01:28 AM

Granted everyone learns different. I won't argue that. But the fact is that this is, quite frankly, a trivial C# problem. This is simple variable scope and access. This should be something that you really need to know if you plan to do programming in C# as it is a pretty fundamental idea of how the language works. If you don't understand variable scope and access, then you do not understand C#.

I'm not being mean or putting people down; I'm trying to help. I didn't become a Microsoft MVP and get a job programming by not knowing what I'm talking about. I'm not trying to be high and mighty with that statement either. I'm simply saying that I have the experience in programming to know what I'm talking about. So perhaps it might be in the best interest of the original poster to take a listen to what I (and three [two in this thread, one on the linked XNA forum post] other Microsoft MVPs) have told him.

tenritsu · 05-18-2008, 08:39 AM

Hey greenskull, it helps to have a basic understanding of how C# works before you try to dig too deep into the language. If you work by just modifying code, you're going to be limited in your scope in terms of how much you know and what methods (not programming methods :P) can solve certain problems. I dont' know your programming experience, but if you're approaching C# with knowledge of BASIC or non-object oriented programming, it's going to be hard to grasp some of the concepts without first understanding objects and classes and whatnot.

Remove Advertisements Sponsored Links
Zune Boards Advertisement

05-17-2008, 06:36 PM	#22 (permalink)
Link9228 Jr. Member Join Date: Nov 2007 Location: Pennsylvania Posts: 360 Reputation: 17 $zB: 313 Donate	ok, but it took me a while to figure out how to fix it too, and i do know the language. I've read 2 books on c# programming, though that was a while ago. And i know i personally learn more from code debugging than when i'm reading what something does and then coding examples

05-18-2008, 01:28 AM	#23 (permalink)
SimReality Jr. Member Join Date: May 2008 Posts: 410 Reputation: 60 $zB: 353 Donate	Granted everyone learns different. I won't argue that. But the fact is that this is, quite frankly, a trivial C# problem. This is simple variable scope and access. This should be something that you really need to know if you plan to do programming in C# as it is a pretty fundamental idea of how the language works. If you don't understand variable scope and access, then you do not understand C#. I'm not being mean or putting people down; I'm trying to help. I didn't become a Microsoft MVP and get a job programming by not knowing what I'm talking about. I'm not trying to be high and mighty with that statement either. I'm simply saying that I have the experience in programming to know what I'm talking about. So perhaps it might be in the best interest of the original poster to take a listen to what I (and three [two in this thread, one on the linked XNA forum post] other Microsoft MVPs) have told him.

05-18-2008, 08:39 AM	#24 (permalink)
tenritsu Experienced Zuner Join Date: May 2008 Posts: 183 Reputation: 13 $zB: 94 Donate	Hey greenskull, it helps to have a basic understanding of how C# works before you try to dig too deep into the language. If you work by just modifying code, you're going to be limited in your scope in terms of how much you know and what methods (not programming methods :P) can solve certain problems. I dont' know your programming experience, but if you're approaching C# with knowledge of BASIC or non-object oriented programming, it's going to be hard to grasp some of the concepts without first understanding objects and classes and whatnot.

Sponsors