The Big Programming Thread - Page 157

Prev 1 155 156 157 158 159 1031 Next

Thread Rules
1. This is not a "do my homework for me" thread. If you have specific questions, ask, but don't post an assignment or homework problem and expect an exact solution.
2. No recruiting for your cockamamie projects (you won't replace facebook with 3 dudes you found on the internet and $20)
3. If you can't articulate why a language is bad, don't start slinging shit about it. Just remember that nothing is worse than making CSS IE6 compatible.
4. Use [code] tags to format code blocks.

SiPa

Germany129 Posts

August 17 2012 13:02 GMT

#3121

wow thanks so much!
at least VS2010 thinks it's cool (still producing mass errors, when trying to compile, but i will tend to them after fixing all the red underlined stuffs ^^)

omarsito

22 Posts

August 17 2012 16:11 GMT

#3122

Hey tlers, got a quick question about eclipse. I cant find the option to increase the "code window" (check picture) without dragging the slider.

http://imgur.com/5D46K

If anybody has the answer please pm or just reply! thanks.

MisterD

Germany1338 Posts

August 17 2012 17:04 GMT

#3123

On August 18 2012 01:11 omarsito wrote:
Hey tlers, got a quick question about eclipse. I cant find the option to increase the "code window" (check picture) without dragging the slider.

http://imgur.com/5D46K

If anybody has the answer please pm or just reply! thanks.

try "reset perspective" from the window menu.

Thorakh

Netherlands1788 Posts

August 19 2012 20:37 GMT

#3124

Java code!

Why oh why is this

+ Show Spoiler +

import java.util.*;

public class RunProgram
{
	public static void main(String[] args)
	{
		Scanner sc = new Scanner(System.in);
		int a = 0;
		boolean correctAnswer = false;
		
		while (!correctAnswer)
		{
			System.out.println("Please enter an integer:");
			try
			{
				a = sc.nextInt();
				correctAnswer = true;				
			}
			catch (Exception e)
			{
				System.out.println("You didn't enter an integer!");
			}
		}
		
		System.out.println("int = " + a);	
	}
}

giving me this

+ Show Spoiler +

Please enter an integer:
b
You didn't enter an integer!
Please enter an integer:
You didn't enter an integer!
Please enter an integer:
You didn't enter an integer!
Please enter an integer:
You didn't enter an integer!
Please enter an integer:
You didn't enter an integer!
...

as console output? I suspect it has something to do with the Scanner because

+ Show Spoiler +

import java.util.*;

public class RunProgram
{
	public static void main(String[] args)
	{
		int a = 0;
		boolean correctAnswer = false;
				
		while (!correctAnswer)
		{
			System.out.println("Please enter an integer:");
			try
			{
				Scanner sc = new Scanner(System.in);
				a = sc.nextInt();
				sc.close();
				correctAnswer = true;				
			}
			catch (Exception e)
			{
				System.out.println("You didn't enter an integer!");
			}
		}
		
		System.out.println("int = " + a);	
	}
}

gives me

+ Show Spoiler +

Please enter an integer:
b
You didn't enter an integer!
Please enter an integer:

as expected.

Why do I have to generate a new Scanner object for this to work?

I am 100% sure I am making a dumb mistake here but I can't for the life of me seem to figure it out! I'm completely stumped.

beamerkun

Poland112 Posts

August 19 2012 20:55 GMT

#3125

You're leaving that 'b' character in buffer - look that in second example you make a new scanner (thus, a new buffer) every time somebody enters line.

Thorakh

Netherlands1788 Posts

August 19 2012 21:05 GMT

#3126

On August 20 2012 05:55 beamerkun wrote:
You're leaving that 'b' character in buffer - look that in second example you make a new scanner (thus, a new buffer) every time somebody enters line.

Ah, of course! Is there a more elegant solution than adding a variable that simply 'eats' the incorrect input

+ Show Spoiler +

import java.util.*;

public class RunProgram
{

	public static void main(String[] args)
	{
                Scanner sc = new Scanner(System.in);
		int a = 0;
		boolean correctAnswer = false;
		String rubbish = "";
				
		while (!correctAnswer)
		{
			System.out.println("Please enter an integer:");
			try
			{
				a = sc.nextInt();
				
				correctAnswer = true;				
			}
			catch (Exception e)
			{
				System.out.println("You didn't enter an integer!");
			        rubbish = sc.next();
			}
		}
		
		System.out.println("int = " + a);	
	}
}

or is making a new Scanner object and closing it every loop an acceptable solution?

Kambing

United States1176 Posts

August 19 2012 21:47 GMT

#3127

On August 20 2012 06:05 Thorakh wrote:

Show nested quote +

Ah, of course! Is there a more elegant solution than adding a variable that simply 'eats' the incorrect input

+ Show Spoiler +

import java.util.*;

public class RunProgram
{

	public static void main(String[] args)
	{
                Scanner sc = new Scanner(System.in);
		int a = 0;
		boolean correctAnswer = false;
		String rubbish = "";
				
		while (!correctAnswer)
		{
			System.out.println("Please enter an integer:");
			try
			{
				a = sc.nextInt();
				
				correctAnswer = true;				
			}
			catch (Exception e)
			{
				System.out.println("You didn't enter an integer!");
			        rubbish = sc.next();
			}
		}
		
		System.out.println("int = " + a);	
	}
}

or is making a new Scanner object and closing it every loop an acceptable solution?

The rubbish variable is unnecessary. You can simply call sc.next() to consume the offending input without storing the returned value in a variable. Note you are only creating one Scanner object here (connected to System.in).

Probably more importantly is that using a try-catch to handle the case where the input is not an integer is not good style. Instead, you should use the hasNextInt() method of the Scanner class to test to see if the next token in the input stream is an integer. If it is not, then you can repeatedly prompt the user until they enter a number.

(Note that ripping out input from System.in by token is a little weird as it is not entirely clear when the prompting occurs. You could argue that it would be better to use readLine() to explicitly grab a line of input from the user and then test that resulting String to see if it is an integer.)

green.at

Austria1459 Posts

August 19 2012 21:59 GMT

#3128

Does it work if you use sc.flush()? Also, you could use a regex to check if the input is valid.

Kambing

United States1176 Posts

August 19 2012 22:04 GMT

#3129

Scanner objects don't have a flush method. And using a regex to check input well-formedness is overkill if all he's looking to enforce is that the input is a valid integer.

white_horse

1019 Posts

August 20 2012 02:01 GMT

#3130

Ok I'm trying to make a program that outputs 100 random lowercase letters in rows of 10. I got this far below,but when "I run the program, it ouputs nothing. Can you guys help me? thanks

+ Show Spoiler +

#include <iostream>
#include <cstdlib>
using namespace std;

void randomgen(char ch1, char ch2)
{
for(int i = 1; i <= 100; i++)
{
cout << static_cast<char>('ch1' + rand() % ('ch2' - 'ch1' + 1));
cout << " ";
if (i % 10 == 0)
{
cout << endl;
}
}
}

int main()
{
char a, z;
randomgen(a, z);

return 0;

}

edit: It's not letting me indent any of the code -_-

tec27

United States3696 Posts

August 20 2012 02:20 GMT

#3131

Use code tags.

But anyway, first thing, you shouldn't be single-quoting your variable names, single quotes are only for char literals. Secondly, you never initialized your a and z variables. If you intend them to be equal to 'a' and 'z', you need to do something like:

char a = 'a';
char z = 'z';

Alternatively you could just pass those values in ( randomgen('a', 'z') ) and not store them in variables.

Judging from your code, it looks like you don't quite understand the difference between variable names and variable values. Variable names are like an address on a mailbox. They tell the compiler what location you're referring to, but the compiler can make no assumptions from the name as to what the location contains. Thus, if you have a char variable named 'a', for all the compiler knows you're storing the value 'f' there. Similarly, if you quote a variable name as a literal (IE: 'ch2' in your code) the compiler will look at this as a literal and nothing else. It will not replace this with either value or the name of what was passed into your function.

IreScath

Canada521 Posts

August 21 2012 16:50 GMT

#3132

I can't figure this out.. When using WaitWindow or WaitWindowLike in my Perl module... It doesn't wait for the app that is launching

code:


my $pid = StartApp("D:\\Musemage\\Musemage.exe");
print 'Launching app.';

#the following should wait for 30 seconds for the app to appear, then continue.
WaitWindow("Musemage",30);

print 'Found window.';
print $pid;

I've also tried WaitWindowLike() to no avail. Its not even like the app just isnt launching.. It is, however the program never waits and just prints 'found window' immediately.

output when run:


Starting [D:\Musemage\Musemage.exe]
new pid:=5372
Launching app.Found window.5372

After Launching app, the script should wait until Musemage window has launched (takes about 8 seconds), and THEN out put the rest... however "found window.5372" prints the same time as "launching app", then the perl script finishes... THEN about 4 seconds after that Musemage finally opens.

The only thing I'm thinking is I'm using WaitWindow wrong? I've tested with wait time at 3 - 3000000.

IreScath

Canada521 Posts

August 21 2012 16:52 GMT

#3133

I should also note that the WaitWindow function just calls Win32::GuiTest::WaitWindow(@_);

supereddie

Netherlands151 Posts

August 21 2012 17:05 GMT

#3134

There is a difference between the app loading and the app creating it's main window. The window can be created immediately (and hidden) while the app actually loads. I assume WaitWindow finds the hidden window.

Additionally, WaitWindow has a return value. try print_r(WaitWindow(.....)) to see what it returns; I guess it is an array of window handles that match the name.

SilSol

Sweden2744 Posts

August 21 2012 17:08 GMT

#3135

I wish i could do programming! That'd be awesome

Maybe someone could teach me the basics?

IreScath

Canada521 Posts

August 21 2012 17:19 GMT

#3136

On August 22 2012 02:05 supereddie wrote:
There is a difference between the app loading and the app creating it's main window. The window can be created immediately (and hidden) while the app actually loads. I assume WaitWindow finds the hidden window.

Additionally, WaitWindow has a return value. try print_r(WaitWindow(.....)) to see what it returns; I guess it is an array of window handles that match the name.

Yea I think you are correct... Its spitting a number out (5835818 for example)... Anyone know of a wait to wait until the window is actually loaded up and visible?

supereddie

Netherlands151 Posts

August 21 2012 17:25 GMT

#3137

There probably is a way to query the visibility of a window by using the window handle - check the Perl docs.

@SilSol: You start by thinking logically and linear; both in detail (individual lines/code blocks/methods) and in the large scale (complete program or even interfacing with other programs). If you can do that, you have the basics.

white_horse

1019 Posts

August 21 2012 18:00 GMT

#3138

On August 20 2012 11:20 tec27 wrote:
Use code tags.

But anyway, first thing, you shouldn't be single-quoting your variable names, single quotes are only for char literals. Secondly, you never initialized your a and z variables. If you intend them to be equal to 'a' and 'z', you need to do something like:

char a = 'a';
char z = 'z';

that helped thanks

Deleted User 101379

4849 Posts

August 21 2012 18:32 GMT

#3139

On August 22 2012 02:25 supereddie wrote:
There probably is a way to query the visibility of a window by using the window handle - check the Perl docs.

@SilSol: You start by thinking logically and linear; both in detail (individual lines/code blocks/methods) and in the large scale (complete program or even interfacing with other programs). If you can do that, you have the basics.

I usually tell people to basically think about how they would solve a given problem by hand with pen&paper, then write it down step by step and after that turn every step into the corresponding code. The end result might not be perfect code or the best and fastest solution but it is a solution that works.

Many people think of programming like something complex and obscure which scares them off since programmers tend to always talk about optimization, ideal sorting algorithms, program design, database normalization, RAII, OOP and all that stuff. Once they understand that programs actually just do stuff you would do yourself, just that computers do it a billion times faster, it gets easier for them to actually turn problems into codified solutions since they no longer try to understand programming but instead start to understand solving problems.

supereddie

Netherlands151 Posts

August 21 2012 19:00 GMT

#3140

Yup, programming is more about problem solving (and analyzing) than writing code. Learning the syntax, keywords and specifics of your programming language is useful, but if you can't solve problems you won't be able to write any :p

Prev 1 155 156 157 158 159 1031 Next

Please or register to reply.

The Big Programming Thread - Page 157

Completed

Ongoing

Upcoming