Fusion

Sadly I don't think what you want to do is possible, the closest you can get to this is a switch case.
Select Case Value Case 1 picPostion1.Image = picPlayer.Image Exit Select Case 2 picPostion2.Image = picPlayer.Image Exit Select Case 3 picPostion3.Image = picPlayer.Image Exit SelectEnd Select  It's a tad bit better than a if else tree but sadly I don't think you can do what you want Sorry if I am wrong

using System;using System.Diagnostics;class TheTerminator{    static void Main(string[] args)    {        Console.WriteLine("What process you wish to close:");        string process = Console.ReadLine();        foreach (Process theVictim in Process.GetProcessesByName(process))        {            try            {                theVictim.Kill();                Console.WriteLine("Termination successful!");            }            catch (Exception e)            {                Console.WriteLine("Termination failed!");            }        }        Console.ReadKey();    }} C# is love, C# is lyfe.

One tip, never pick up a pros playing style, invent your own. Be that random player that actually outplays it's opposition. I am a SMFC and played in CEVO-M and ESEA-O, I actually found it really easy to predict people, awpers mostly, they all used to try to play like JW, same spots and all. AKs used to like to hold the SAME angle, for example on D2 the headshot spot on ramp. Nuke on the ramp going to lower head glitching, mirage left side windowed crouched down or crouched in Connector. Cache gene/headshot/Fork and above fork. Inferno crouching at the end of car. It's just too eazy, I could prefire everyone almost everytime that's only as T, on CT it's even EASIER to predict the Ts just in short, don't try to play like a pro, invent your own style! Peak like GOD himself. It's gonna be hard but there are different ways to peak each corner, just don't be that guy who crab walks out scoped with AWP. Also another tip, learn to trace heads, I see a lot of people struggle. Also spraying. Don't spray too much, that's where I started to lose my touch.1 tap is the only way . Good lucK! When you get to Nova level or so (Nova 2) join CEVO, when you get to MGE to DMG join ESEA.

Nah, the NSA does this all the time and nobody complains

Note: This isn't directed towards you if you're a complete beginner who has never started coding yet. Once you get started though, it wont be long before this information is relevant to you so come back after you can start making your own simple programs.
 
Introduction
 
We get a lot of topics here where someone posts their code that wont work and is (politely) asking us to fix it. Commonly they wont give us any extra information about the problem. Maybe you've done this yourself or were going to. Please read on.
 
It's great that there are people on these forums willing to help you out even if you don't do any debugging. However, it's to everyone's benefit, especially your own, if you start learning how to pinpoint and solve your issues yourself. This doesn't mean you'll be able to solve all your own problems, and we're still here for you, but at the very least you'll learn how to provide more information when asking for help.
 
A large part of programming is writing fresh new code to accomplish a task. Another large part of programming is figuring out why the code you, or someone else, wrote isn't working correctly. This process of identifying and removing errors is known as debugging. Every programmer should start learning to debug early because it's so helpful regardless of your skill level. So after you've went through a few tutorials and learned how to run some simple programs, it's a good time to jump into debugging.
 
There are 2 places where you can start debugging:
Using print statements Using a debugging tool In the future it will be useful to get into formal testing but don't worry about that at this stage.
 
Using Print Statements
 
Sometimes, no matter how advanced you are, all you need is a quick print statement to solve your issue. And it's a good place for beginners to start because they don't need to learn anything new. You may have already been doing this without knowing what the word "debugging" is and if so, great.
 
All you need to do is to put print statements in your code that provide you with useful information. There are far too many languages where each language may have multiple options for printing so obviously I can't list them all, but you'll usually learn one way of doing it in your first couple tutorials. Many tutorials start you out with the traditional "Hello World" example so in many cases you learn how to output text to the screen in lesson 1. Here are some examples.
// JavaSystem.Out.Println("...");// Python 2.7.xprint "..."// Python 3.xprint("...")// C#/VB.NETConsole.WriteLine("...");// Cprintf("...");// C++cout << "...";// PHPecho "...";// etc The point of using print statements for debugging is to help figure out what is actually going on when you run your code. What is in that variable? What does that function return? Did I get the correct input from the user? Does the code enter the if block or the else block? What is happening in that loop? etc
 
It's a very simple method of debugging but it can still lead you towards your solution.
 
Using a debugging tool
 
Debugging tools offer many features and is a lot more useful than print statements in most cases. Essential, you get to pause your program at any line of code while it's running. While it's paused, you can have a look around at things like what value a variable currently holds. You can step through a program line by line, pausing at each line to make sure things are happening correctly or you can stop at only the specific lines you want. Sounds useful right? It'll take a little more work to learn how to use these tools, but once you do it'll make your coding life easier.
 
If you are using an IDE, like Visual Studio, Eclipse, IntelliJ, Code::Blocks, etc, then they will have a built in debugging tool. If you prefer text editors like Notepad++, Sublime Text 2, etc, they may have a debugging tool, perhaps through an extension, but if not you may be able to download a standalone option. For example GDB is a standalone command line debugger commonly used with C. Many browsers also have developer tools that have debuggers. For example you can debug Javascript inside Chrome and Firefox. 
 
The best way to learn to use these tools is to look for tutorials for the specific debugger that you use. It's also more likely to be in the language you're using which might make it easier for you to follow. Many debuggers are very similar though so if you learn to use one in say Visual Studio, you can probably then figure out how to use one in another IDE like IntelliJ.
 
Here are some debugger tutorials for reference but feel free to go out and find your own.
Visual Studio (1) Code::Blocks (1) Eclipse (1) GDB (1) Chrome (1) If anyone wants to help me add to this list, contact me and I'll add it in. Being an IDE guy, I'm not familiar with many options in the text editor/standalone areas.
 
Conclusion
 
So now that you know you should be debugging, when you run into a problem with your code then give it a try. It's perfectly fine if you can't solve your problem yet, we are still here to help. It's the trying and information gathering that will help you learn and become a better programmer. Treat each error as an opportunity to learn something new.
 
So now that you're more informed, here are the things to post when requesting help:
Purpose - What is the code supposed to accomplish? Code - The code itself (remember to use these forums [ code ] tags) Error - What is the error message you are receiving when trying to build or run your program? Line of Error - What line is the error message pointing at? Any additional information you think might be useful that you found while debugging. With debugging, even if you can't solve something yourself, you might find that your question becomes more narrow. You'll no longer be asking "Why doesn't my program work?" but instead asking more specific questions.
 
And even if you're just stuck on the "I can't even get my program to run so I can't debug it" problem, you can still post the first 4 points I mentioned and someone can better help you get things up and running.
 
 
If you have any questions/comments post below or send me a private message. Happy Coding!

Looking at the specs of that laptop I would say no. I would just bite the bullet with the slowness.

A lot!
 
Start with basic things:
IPv4/6
Wireshark
Protocols (Learn the basics, FTP, HTTP, HTTPS, SSL, TLS, IMAP, POP, RDP, etc.)
Learn a packets structure(TCP/IP and UDP)
Firewalls
Proxies
VPN
Learn about sockets
Subnetting
HTTP GET and POST requests.
TCP(SYN, ACK)
 
Much more.

That is a beautiful pc man! Mine looks like shit compared to that.

Omg.
 
My thoughts on printing:

 
Nice man I am making a nice project in C# atm. I got a job working for someone haha. He wants to start a company so I told him I could give him his programs etc.

It could be:

1. Video card is overheating

2. Video card is about to kick the bucket

3. You're monitor has a loose connector

4. You're monitor is about to kick the bucket

5. Alma Wade is in the room

bruhh use partpicker

Haha I helped you

I'm that guy.
 
 
Who likes to get likes on posts that may or may not be relevant to the OP.

Bro wut da effff I told erryone it was FaZe FusioN[MLG]

It's just Logitech Gaming Software, download it here.
 
http://support.logitech.com/en_us/product/gaming-software

You hand, pillow, bed, couch don't count
 
Lol look @ that.

Nice man good for you! I miss my ex, Kappa.

Terry your right hand doesn't count ffs

Good luck man, stay safe!

Yea if it wasn't for me starting with a laptop I wouldn't know shit about them.

This one looks decent battery life only around 3 1/2 hours..... But I mean a gaming laptop isn't really the best for that long lasting game. Specially only for 1k.

Very well could be, you are correct no way in hell you are maxing. 

It's mostlikely a Ribbon cable if it's a laptop. so you really can't use it. Laptops LOVE ribbon cables. Displayport does look like sata btw.

Looking at the specs of that laptop I would say no. I would just bite the bullet with the slowness.

Good luck man, stay safe!