|
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. |
On December 20 2013 11:20 Cyx. wrote:Show nested quote +On December 20 2013 11:02 Maero wrote:On December 20 2013 10:11 Cyx. wrote:On December 20 2013 09:26 Maero wrote:On December 20 2013 07:49 Vilanoil wrote:
int sumAge(PlayerList list){
//stuff
}
int sumAge(){
return sumAge(this);
}
// is called in main with
players.sumAge();
I'm not sure but it seems like that is a recursive call of sumAge() and that (this) is automatically referring to the list players. Would be awesome if someone could explain this. All this is really doing is giving you a shorthand to sum the ages of the PlayerList this method is being called from. Ex.
PlayerList a;
PlayerList b; // pretend these have stuff in it
a.sumAge(b); // performs the operation on PlayerList b (I assume summing up the ages...)
a.sumAge(); // calls the non-parameterized one, then falls back to the parameterized method
// Basically...
a.sumAge() == a.sumAge(a);
Let me know if that doesn't make sense! It seems like a strange implementation, but that is the literal way that it is working. But I guess the question is... good lord, why, please why something so awfully confusing? players.sumAge() will call sumAge(this)... calling players.sumAge(this) within that function just means you end up calling sumAge(this, this) basically. It's literally just adding an extra definition and extra confusion to something that should be one method. I see absolutely zero sense in doing it this way instead of just writing sumAge() to do the actual summing of ages, and then not bother with the definition that has an extra parameter (which never even gets used). We completely agree! But he asked for an explanation of how it was working, so that's what I provided  The note at the end about it being a strange implementation was alluding to your point - there's no real good reason to put it together in that way and either one or the other would work fine (depending on how the method interacts with other PlayerList age sums). okie, cool =) I guess I just wasn't sure if it was like... a Java thing or something (I mostly use C++) or if it was as totally weird as it seemed. @Vilanoil: were you given the code like that (for your class) or did you write the whole PlayerList class yourself?
The given like that:
int sumAge(PlayerList list)
{
// *** your implementation ***
}
// *************************************************************************
// recursive computation of sum of games of all players in the list
int sumAge()
{
return sumAge(this);
}
All we had to do is filling the gaps and all methods are give in this way ... It was confusing for us too~
But i guess i will just forget about it since it seems pretty useless
|
On December 20 2013 17:09 Vilanoil wrote:Show nested quote +On December 20 2013 11:20 Cyx. wrote:On December 20 2013 11:02 Maero wrote:On December 20 2013 10:11 Cyx. wrote:On December 20 2013 09:26 Maero wrote:On December 20 2013 07:49 Vilanoil wrote:
int sumAge(PlayerList list){
//stuff
}
int sumAge(){
return sumAge(this);
}
// is called in main with
players.sumAge();
I'm not sure but it seems like that is a recursive call of sumAge() and that (this) is automatically referring to the list players. Would be awesome if someone could explain this. All this is really doing is giving you a shorthand to sum the ages of the PlayerList this method is being called from. Ex.
PlayerList a;
PlayerList b; // pretend these have stuff in it
a.sumAge(b); // performs the operation on PlayerList b (I assume summing up the ages...)
a.sumAge(); // calls the non-parameterized one, then falls back to the parameterized method
// Basically...
a.sumAge() == a.sumAge(a);
Let me know if that doesn't make sense! It seems like a strange implementation, but that is the literal way that it is working. But I guess the question is... good lord, why, please why something so awfully confusing? players.sumAge() will call sumAge(this)... calling players.sumAge(this) within that function just means you end up calling sumAge(this, this) basically. It's literally just adding an extra definition and extra confusion to something that should be one method. I see absolutely zero sense in doing it this way instead of just writing sumAge() to do the actual summing of ages, and then not bother with the definition that has an extra parameter (which never even gets used). We completely agree! But he asked for an explanation of how it was working, so that's what I provided The note at the end about it being a strange implementation was alluding to your point - there's no real good reason to put it together in that way and either one or the other would work fine (depending on how the method interacts with other PlayerList age sums). okie, cool =) I guess I just wasn't sure if it was like... a Java thing or something (I mostly use C++) or if it was as totally weird as it seemed. @Vilanoil: were you given the code like that (for your class) or did you write the whole PlayerList class yourself? The given like that:
int sumAge(PlayerList list)
{
// *** your implementation ***
}
// *************************************************************************
// recursive computation of sum of games of all players in the list
int sumAge()
{
return sumAge(this);
}
All we had to do is filling the gaps and all methods are give in this way ... It was confusing for us too~ But i guess i will just forget about it since it seems pretty useless
This is like... the weirdest fucking intro to recursion ever. You guys have talked about the implicit reference to "this" in method definitions right?
|
Hey guys, I'm new to python and I'm trying to create a simple hangman game from one of my books. So far everything is good but I failed to recreate the part of the game that shows the dashes and the correct letters that you've guessed so far, such as PY---N I tried looking at the code example in the book but couldn't really understand how or why it works. I've copied the specific parts of the code that I don't understand.
I've commented each line to walk you through what I understand is happening.
so_far = "-" * len(word) # Creates dashes based on the length of the word
while wrong < MAX_WRONG and so_far != word:
print("\nSo far, the word is:\n", so_far) #Main loop, but I've cut out all the irrelevant stuff
guess = input("\n\nEnter your guess: ")
#Checking the Player's guess
if guess in word: #If the letter is in the word, let's say the word is PYTHON and the guess is O
print("\nYes!", guess, "is in the word!")
new = ""
for i in range(len(word)): #A sequence 0-6 is generated and this loop repeats 6 times
if guess == word[i]: #If the guess string matches the string from the index
new += guess # concatenate the guess string to whatever is in new
else:
new += so_far[i] #So new now becomes - in the first iteration
so_far = new #Once the loop ends so_far should look like ----O-
Am I understanding it right? And also... How do you even plan for this sorta thing? The book had an intro on pseudo code but I had never imagined to use a for loop and an if condition in this sort of combination.
|
On December 20 2013 17:51 Cyx. wrote:Show nested quote +On December 20 2013 17:09 Vilanoil wrote:On December 20 2013 11:20 Cyx. wrote:On December 20 2013 11:02 Maero wrote:On December 20 2013 10:11 Cyx. wrote:On December 20 2013 09:26 Maero wrote:On December 20 2013 07:49 Vilanoil wrote:
int sumAge(PlayerList list){
//stuff
}
int sumAge(){
return sumAge(this);
}
// is called in main with
players.sumAge();
I'm not sure but it seems like that is a recursive call of sumAge() and that (this) is automatically referring to the list players. Would be awesome if someone could explain this. All this is really doing is giving you a shorthand to sum the ages of the PlayerList this method is being called from. Ex.
PlayerList a;
PlayerList b; // pretend these have stuff in it
a.sumAge(b); // performs the operation on PlayerList b (I assume summing up the ages...)
a.sumAge(); // calls the non-parameterized one, then falls back to the parameterized method
// Basically...
a.sumAge() == a.sumAge(a);
Let me know if that doesn't make sense! It seems like a strange implementation, but that is the literal way that it is working. But I guess the question is... good lord, why, please why something so awfully confusing? players.sumAge() will call sumAge(this)... calling players.sumAge(this) within that function just means you end up calling sumAge(this, this) basically. It's literally just adding an extra definition and extra confusion to something that should be one method. I see absolutely zero sense in doing it this way instead of just writing sumAge() to do the actual summing of ages, and then not bother with the definition that has an extra parameter (which never even gets used). We completely agree! But he asked for an explanation of how it was working, so that's what I provided The note at the end about it being a strange implementation was alluding to your point - there's no real good reason to put it together in that way and either one or the other would work fine (depending on how the method interacts with other PlayerList age sums). okie, cool =) I guess I just wasn't sure if it was like... a Java thing or something (I mostly use C++) or if it was as totally weird as it seemed. @Vilanoil: were you given the code like that (for your class) or did you write the whole PlayerList class yourself? The given like that:
int sumAge(PlayerList list)
{
// *** your implementation ***
}
// *************************************************************************
// recursive computation of sum of games of all players in the list
int sumAge()
{
return sumAge(this);
}
All we had to do is filling the gaps and all methods are give in this way ... It was confusing for us too~ But i guess i will just forget about it since it seems pretty useless This is like... the weirdest fucking intro to recursion ever. You guys have talked about the implicit reference to "this" in method definitions right?
No we didn't cover anything like this. The only way we used "this" so far was actually in variable declaration in classes, eiter in the constructors or the class methods. ..
|
On December 20 2013 18:32 lannisport wrote:Hey guys, I'm new to python and I'm trying to create a simple hangman game from one of my books. So far everything is good but I failed to recreate the part of the game that shows the dashes and the correct letters that you've guessed so far, such as PY---N I tried looking at the code example in the book but couldn't really understand how or why it works. I've copied the specific parts of the code that I don't understand. I've commented each line to walk you through what I understand is happening. + Show Spoiler +
so_far = "-" * len(word) # Creates dashes based on the length of the word
while wrong < MAX_WRONG and so_far != word:
print("\nSo far, the word is:\n", so_far) #Main loop, but I've cut out all the irrelevant stuff
guess = input("\n\nEnter your guess: ")
#Checking the Player's guess
if guess in word: #If the letter is in the word, let's say the word is PYTHON and the guess is O
print("\nYes!", guess, "is in the word!")
new = ""
for i in range(len(word)): #A sequence 0-6 is generated and this loop repeats 6 times
if guess == word[i]: #If the guess string matches the string from the index
new += guess # concatenate the guess string to whatever is in new
else:
new += so_far[i] #So new now becomes - in the first iteration
so_far = new #Once the loop ends so_far should look like ----O-
Am I understanding it right? And also... How do you even plan for this sorta thing? The book had an intro on pseudo code but I had never imagined to use a for loop and an if condition in this sort of combination.
It seems like you understand most of it. new += so_far[i] is basically saying "don't update this character in so_far"
I think it's a lot more intuitive to update so_far in place. This does the same thing but you can get rid of new:
for i in range(len(word)):
if guess == word[i]:
so_far[i] = word[i]
How do you plan this sort of thing? To me this is the most intuitive solution, i guess it just comes with experience.
|
On December 21 2013 04:28 scudst0rm wrote:Show nested quote +On December 20 2013 18:32 lannisport wrote:Hey guys, I'm new to python and I'm trying to create a simple hangman game from one of my books. So far everything is good but I failed to recreate the part of the game that shows the dashes and the correct letters that you've guessed so far, such as PY---N I tried looking at the code example in the book but couldn't really understand how or why it works. I've copied the specific parts of the code that I don't understand. I've commented each line to walk you through what I understand is happening. + Show Spoiler +
so_far = "-" * len(word) # Creates dashes based on the length of the word
while wrong < MAX_WRONG and so_far != word:
print("\nSo far, the word is:\n", so_far) #Main loop, but I've cut out all the irrelevant stuff
guess = input("\n\nEnter your guess: ")
#Checking the Player's guess
if guess in word: #If the letter is in the word, let's say the word is PYTHON and the guess is O
print("\nYes!", guess, "is in the word!")
new = ""
for i in range(len(word)): #A sequence 0-6 is generated and this loop repeats 6 times
if guess == word[i]: #If the guess string matches the string from the index
new += guess # concatenate the guess string to whatever is in new
else:
new += so_far[i] #So new now becomes - in the first iteration
so_far = new #Once the loop ends so_far should look like ----O-
Am I understanding it right? And also... How do you even plan for this sorta thing? The book had an intro on pseudo code but I had never imagined to use a for loop and an if condition in this sort of combination. It seems like you understand most of it. new += so_far[i] is basically saying "don't update this character in so_far" I think it's a lot more intuitive to update so_far in place. This does the same thing but you can get rid of new:
for i in range(len(word)):
if guess == word[i]:
so_far[i] = word[i]
How do you plan this sort of thing? To me this is the most intuitive solution, i guess it just comes with experience.
Correct me if I'm wrong, but I think Python strings are immutable - meaning the way he has it so far is the way to go about it ^^ Testing in an interpreter gives:
>>>hello = "HelloWorld!"
>>>hello[2] = "a"
Traceback (most recent call last):
File stdin, line 1, in <module>
TypeError: 'str' object does not support item assignment
|
Yep. Any operations on a python string must result in a new string. Good illustration Cyx.
Edit: Just to contribute something: One way around this is to turn the string into a list instead, modify an element, and rejoin. e.g.
>>> str = "string"
>>> str = list(str)
>>> str[2] = 'a'
>>> str = ''.join(str)
>>> str
'staing'
But the way in your book is probably just about the same as far as efficiency goes, if not a little better.
|
On December 21 2013 10:30 Maero wrote:Yep. Any operations on a python string must result in a new string. Good illustration Cyx. Edit: Just to contribute something: One way around this is to turn the string into a list instead, modify an element, and rejoin. e.g.
>>> str = "string"
>>> str = list(str)
>>> str[2] = 'a'
>>> str = ''.join(str)
>>> str
'staing'
But the way in your book is probably just about the same as far as efficiency goes, if not a little better.
Please don't use str as a name for a variable as it is a built-in function/type. By assigning a value to it you overwrite its default value which can cause all kinds of problems in a bigger program. You probably know this Maero but it might be worth to point it out to people learning Python.
|
I am trying to write a program to crack zip passwords in c/c++ with mpi using brute force. I know how to distribute the work through mpi. There are a few libraries to unzip files like minizip, libzip etc. I will try to unzip the file using them with for loops and incrementing passwords in each process with different starting points, But... this seems really inefficient. Can anyone give me pointers?
|
Hello TL! I have started trying to create a TicTacToe game and ran into a problem with the graphics. Currently I can create the window and the background I like using fillRect to fill the background blue, and then fillRect to fill each square black, leaving blue bars in between. However, I would like help adding in something that redraws/draws over what exists when I click on the window. The graphics documentation is confusing the hell out of me. There is probably 1 call that needs to be made to do this, but I've trawled through a bunch of SO questions and the documentation and nothing has shown up.
My code is:
+ Show Spoiler +import java.awt.Color;
import java.awt.Graphics;
import java.awt.event.MouseEvent;
import java.awt.event.MouseListener;
import javax.swing.JFrame;
public class GraphicsStart extends JFrame implements MouseListener{
private static final long serialVersionUID = 1L;
final int boardDimensions = 600;//Pixel dimensions of the square board.
final int xDivisions = 3;//Brackets of each dimension.
final int yDivisions = 3;
final int frameWidth = 5;//Width of frame in pixels. Occurs on both sides, so double.
public GraphicsStart(){
setTitle("TicTacToe - Graeme Cliffe");
setSize(boardDimensions,boardDimensions);
setVisible(true);
setDefaultCloseOperation(EXIT_ON_CLOSE);
addMouseListener(this);
}
public void paint(Graphics g){
g.setColor(Color.BLUE);
g.fillRect(0, 0, boardDimensions, boardDimensions);//Creates the background.
g.setColor(Color.BLACK);
for (int xInc = 0; xInc < xDivisions; xInc++){//Increments through the Xs
for (int yInc = 0; yInc <yDivisions; yInc++){
g.fillRect(xInc*(boardDimensions/xDivisions), yInc*(boardDimensions/yDivisions),
xInc + (boardDimensions/xDivisions)-frameWidth, yInc +(boardDimensions/yDivisions)-frameWidth);
//Each box is 195x195, and there are currently 9 of them.
}
}
}
public void mouseClicked(MouseEvent e){
//This is where the magic should happen but what should be called? Ideally I would draw over the old image with some new rectangle.
int xClick = e.getX();
int yClick = e.getY();
repaint();
}
public static void main(String args[]) {
GraphicsStart demo = new GraphicsStart();
}
@Override
public void mouseEntered(MouseEvent arg0) {
}
@Override
public void mouseExited(MouseEvent arg0) {
}
@Override
public void mousePressed(MouseEvent arg0) {
}
@Override
public void mouseReleased(MouseEvent arg0) {
}
}
|
On December 22 2013 03:09 Isualin wrote:
I am trying to write a program to crack zip passwords in c/c++ with mpi using brute force. I know how to distribute the work through mpi. There are a few libraries to unzip files like minizip, libzip etc. I will try to unzip the file using them with for loops and incrementing passwords in each process with different starting points, But... this seems really inefficient. Can anyone give me pointers?
Well, given that you are trying to crack the password with brute force, I can't imagine there would be an "efficient" method of brute forcing since brute forcing is by nature inefficient.
|
On December 22 2013 15:40 betaflame wrote:Show nested quote +On December 22 2013 03:09 Isualin wrote:
I am trying to write a program to crack zip passwords in c/c++ with mpi using brute force. I know how to distribute the work through mpi. There are a few libraries to unzip files like minizip, libzip etc. I will try to unzip the file using them with for loops and incrementing passwords in each process with different starting points, But... this seems really inefficient. Can anyone give me pointers? Well, given that you are trying to crack the password with brute force, I can't imagine there would be an "efficient" method of brute forcing since brute forcing is by nature inefficient.
Not entirely. Brute forcing just means blind guessing, iterating through all options. There are still ways to be efficient.
Onto a problem I'm having, anybody know of a good way to create a string based on Perl regex embedded into a normal string? Tried String::Random, but it only creates a string if the input is solely regex.
|
|
|
On December 22 2013 11:56 WarSame wrote:Hello TL! I have started trying to create a TicTacToe game and ran into a problem with the graphics. Currently I can create the window and the background I like using fillRect to fill the background blue, and then fillRect to fill each square black, leaving blue bars in between. However, I would like help adding in something that redraws/draws over what exists when I click on the window. The graphics documentation is confusing the hell out of me. There is probably 1 call that needs to be made to do this, but I've trawled through a bunch of SO questions and the documentation and nothing has shown up. My code is: + Show Spoiler +import java.awt.Color;
import java.awt.Graphics;
import java.awt.event.MouseEvent;
import java.awt.event.MouseListener;
import javax.swing.JFrame;
public class GraphicsStart extends JFrame implements MouseListener{
private static final long serialVersionUID = 1L;
final int boardDimensions = 600;//Pixel dimensions of the square board.
final int xDivisions = 3;//Brackets of each dimension.
final int yDivisions = 3;
final int frameWidth = 5;//Width of frame in pixels. Occurs on both sides, so double.
public GraphicsStart(){
setTitle("TicTacToe - Graeme Cliffe");
setSize(boardDimensions,boardDimensions);
setVisible(true);
setDefaultCloseOperation(EXIT_ON_CLOSE);
addMouseListener(this);
}
public void paint(Graphics g){
g.setColor(Color.BLUE);
g.fillRect(0, 0, boardDimensions, boardDimensions);//Creates the background.
g.setColor(Color.BLACK);
for (int xInc = 0; xInc < xDivisions; xInc++){//Increments through the Xs
for (int yInc = 0; yInc <yDivisions; yInc++){
g.fillRect(xInc*(boardDimensions/xDivisions), yInc*(boardDimensions/yDivisions),
xInc + (boardDimensions/xDivisions)-frameWidth, yInc +(boardDimensions/yDivisions)-frameWidth);
//Each box is 195x195, and there are currently 9 of them.
}
}
}
public void mouseClicked(MouseEvent e){
//This is where the magic should happen but what should be called? Ideally I would draw over the old image with some new rectangle.
int xClick = e.getX();
int yClick = e.getY();
repaint();
}
public static void main(String args[]) {
GraphicsStart demo = new GraphicsStart();
}
@Override
public void mouseEntered(MouseEvent arg0) {
}
@Override
public void mouseExited(MouseEvent arg0) {
}
@Override
public void mousePressed(MouseEvent arg0) {
}
@Override
public void mouseReleased(MouseEvent arg0) {
}
}
It's "simple"
First you need to figure out which square you are in, then you draw exactly like before, just with a new color
|
On December 21 2013 10:30 Maero wrote:Yep. Any operations on a python string must result in a new string. Good illustration Cyx. Edit: Just to contribute something: One way around this is to turn the string into a list instead, modify an element, and rejoin. e.g.
>>> str = "string"
>>> str = list(str)
>>> str[2] = 'a'
>>> str = ''.join(str)
>>> str
'staing'
But the way in your book is probably just about the same as far as efficiency goes, if not a little better.
How about:
newString=oldString[:2]+"a"+oldString[3:]
|
On December 22 2013 18:15 bangsholt wrote:Show nested quote +On December 22 2013 11:56 WarSame wrote:Hello TL! I have started trying to create a TicTacToe game and ran into a problem with the graphics. Currently I can create the window and the background I like using fillRect to fill the background blue, and then fillRect to fill each square black, leaving blue bars in between. However, I would like help adding in something that redraws/draws over what exists when I click on the window. The graphics documentation is confusing the hell out of me. There is probably 1 call that needs to be made to do this, but I've trawled through a bunch of SO questions and the documentation and nothing has shown up. My code is: + Show Spoiler +import java.awt.Color;
import java.awt.Graphics;
import java.awt.event.MouseEvent;
import java.awt.event.MouseListener;
import javax.swing.JFrame;
public class GraphicsStart extends JFrame implements MouseListener{
private static final long serialVersionUID = 1L;
final int boardDimensions = 600;//Pixel dimensions of the square board.
final int xDivisions = 3;//Brackets of each dimension.
final int yDivisions = 3;
final int frameWidth = 5;//Width of frame in pixels. Occurs on both sides, so double.
public GraphicsStart(){
setTitle("TicTacToe - Graeme Cliffe");
setSize(boardDimensions,boardDimensions);
setVisible(true);
setDefaultCloseOperation(EXIT_ON_CLOSE);
addMouseListener(this);
}
public void paint(Graphics g){
g.setColor(Color.BLUE);
g.fillRect(0, 0, boardDimensions, boardDimensions);//Creates the background.
g.setColor(Color.BLACK);
for (int xInc = 0; xInc < xDivisions; xInc++){//Increments through the Xs
for (int yInc = 0; yInc <yDivisions; yInc++){
g.fillRect(xInc*(boardDimensions/xDivisions), yInc*(boardDimensions/yDivisions),
xInc + (boardDimensions/xDivisions)-frameWidth, yInc +(boardDimensions/yDivisions)-frameWidth);
//Each box is 195x195, and there are currently 9 of them.
}
}
}
public void mouseClicked(MouseEvent e){
//This is where the magic should happen but what should be called? Ideally I would draw over the old image with some new rectangle.
int xClick = e.getX();
int yClick = e.getY();
repaint();
}
public static void main(String args[]) {
GraphicsStart demo = new GraphicsStart();
}
@Override
public void mouseEntered(MouseEvent arg0) {
}
@Override
public void mouseExited(MouseEvent arg0) {
}
@Override
public void mousePressed(MouseEvent arg0) {
}
@Override
public void mouseReleased(MouseEvent arg0) {
}
}
It's "simple" First you need to figure out which square you are in, then you draw exactly like before, just with a new color
Well that's the problem. I can figure out which square was clicked on no problem! But then I have no idea what you are supposed to use to redraw over the old one.
Ideally the pseudocode would be:
public void repaint(){
getOldPaint();
newPaint = combineOldAndNewPaint();
paintOver(newPaint);
}
But I don't know any of those commands in Java's Graphics or Swing and haven't been able to find them through trawling for an hour or 2.
So I decided to switch over to something I saw used in a guide, which was to have a JFrame and JPanel class. Hopefully this works better.
|
On December 23 2013 02:39 WarSame wrote:Show nested quote +On December 22 2013 18:15 bangsholt wrote:On December 22 2013 11:56 WarSame wrote:Hello TL! I have started trying to create a TicTacToe game and ran into a problem with the graphics. Currently I can create the window and the background I like using fillRect to fill the background blue, and then fillRect to fill each square black, leaving blue bars in between. However, I would like help adding in something that redraws/draws over what exists when I click on the window. The graphics documentation is confusing the hell out of me. There is probably 1 call that needs to be made to do this, but I've trawled through a bunch of SO questions and the documentation and nothing has shown up. My code is: + Show Spoiler +import java.awt.Color;
import java.awt.Graphics;
import java.awt.event.MouseEvent;
import java.awt.event.MouseListener;
import javax.swing.JFrame;
public class GraphicsStart extends JFrame implements MouseListener{
private static final long serialVersionUID = 1L;
final int boardDimensions = 600;//Pixel dimensions of the square board.
final int xDivisions = 3;//Brackets of each dimension.
final int yDivisions = 3;
final int frameWidth = 5;//Width of frame in pixels. Occurs on both sides, so double.
public GraphicsStart(){
setTitle("TicTacToe - Graeme Cliffe");
setSize(boardDimensions,boardDimensions);
setVisible(true);
setDefaultCloseOperation(EXIT_ON_CLOSE);
addMouseListener(this);
}
public void paint(Graphics g){
g.setColor(Color.BLUE);
g.fillRect(0, 0, boardDimensions, boardDimensions);//Creates the background.
g.setColor(Color.BLACK);
for (int xInc = 0; xInc < xDivisions; xInc++){//Increments through the Xs
for (int yInc = 0; yInc <yDivisions; yInc++){
g.fillRect(xInc*(boardDimensions/xDivisions), yInc*(boardDimensions/yDivisions),
xInc + (boardDimensions/xDivisions)-frameWidth, yInc +(boardDimensions/yDivisions)-frameWidth);
//Each box is 195x195, and there are currently 9 of them.
}
}
}
public void mouseClicked(MouseEvent e){
//This is where the magic should happen but what should be called? Ideally I would draw over the old image with some new rectangle.
int xClick = e.getX();
int yClick = e.getY();
repaint();
}
public static void main(String args[]) {
GraphicsStart demo = new GraphicsStart();
}
@Override
public void mouseEntered(MouseEvent arg0) {
}
@Override
public void mouseExited(MouseEvent arg0) {
}
@Override
public void mousePressed(MouseEvent arg0) {
}
@Override
public void mouseReleased(MouseEvent arg0) {
}
}
It's "simple" First you need to figure out which square you are in, then you draw exactly like before, just with a new color Well that's the problem. I can figure out which square was clicked on no problem! But then I have no idea what you are supposed to use to redraw over the old one. Ideally the pseudocode would be: public void repaint(){ getOldPaint(); newPaint = combineOldAndNewPaint(); paintOver(newPaint); } But I don't know any of those commands in Java's Graphics or Swing and haven't been able to find them through trawling for an hour or 2. So I decided to switch over to something I saw used in a guide, which was to have a JFrame and JPanel class. Hopefully this works better.
You do exactly the same - you just draw "on top" of the old graphics and it replaces it
|
repaint just calls the normal paint method. So change that one. Dont implement your own repaint.
You dont paint over something. You clear everything and paint from scratch.
i.e. after your 2 for loops change to another color. And then g.fillRect with the parameters of the clicked box:
g.setColor(Color.RED);
g.fillRect(0*(boardDimensions/xDivisions), 0*(boardDimensions/yDivisions),
0 + (boardDimensions/xDivisions)-frameWidth, 0 +(boardDimensions/yDivisions)-frameWidth);
If the clicked one is the (0,0) one.
You can also do this change in the initial for loops and check if the current one is the one which is clicked and change colors accordingly.
if (xInc == xClicked && yInc == yClicked) g.setColor(Color.RED);
// draw your normal rectangle as before
g.setColor(Color.BLACK);
|
United States10328 Posts
I did my first ever TopCoder contest today and got blue!
On the other hand, I failed at coding a binary search (to find the rightmost element strictly less than the query) for like 15 minutes! :D :D
|
On December 23 2013 02:39 WarSame wrote:Show nested quote +On December 22 2013 18:15 bangsholt wrote:On December 22 2013 11:56 WarSame wrote:Hello TL! I have started trying to create a TicTacToe game and ran into a problem with the graphics. Currently I can create the window and the background I like using fillRect to fill the background blue, and then fillRect to fill each square black, leaving blue bars in between. However, I would like help adding in something that redraws/draws over what exists when I click on the window. The graphics documentation is confusing the hell out of me. There is probably 1 call that needs to be made to do this, but I've trawled through a bunch of SO questions and the documentation and nothing has shown up. My code is: + Show Spoiler +import java.awt.Color;
import java.awt.Graphics;
import java.awt.event.MouseEvent;
import java.awt.event.MouseListener;
import javax.swing.JFrame;
public class GraphicsStart extends JFrame implements MouseListener{
private static final long serialVersionUID = 1L;
final int boardDimensions = 600;//Pixel dimensions of the square board.
final int xDivisions = 3;//Brackets of each dimension.
final int yDivisions = 3;
final int frameWidth = 5;//Width of frame in pixels. Occurs on both sides, so double.
public GraphicsStart(){
setTitle("TicTacToe - Graeme Cliffe");
setSize(boardDimensions,boardDimensions);
setVisible(true);
setDefaultCloseOperation(EXIT_ON_CLOSE);
addMouseListener(this);
}
public void paint(Graphics g){
g.setColor(Color.BLUE);
g.fillRect(0, 0, boardDimensions, boardDimensions);//Creates the background.
g.setColor(Color.BLACK);
for (int xInc = 0; xInc < xDivisions; xInc++){//Increments through the Xs
for (int yInc = 0; yInc <yDivisions; yInc++){
g.fillRect(xInc*(boardDimensions/xDivisions), yInc*(boardDimensions/yDivisions),
xInc + (boardDimensions/xDivisions)-frameWidth, yInc +(boardDimensions/yDivisions)-frameWidth);
//Each box is 195x195, and there are currently 9 of them.
}
}
}
public void mouseClicked(MouseEvent e){
//This is where the magic should happen but what should be called? Ideally I would draw over the old image with some new rectangle.
int xClick = e.getX();
int yClick = e.getY();
repaint();
}
public static void main(String args[]) {
GraphicsStart demo = new GraphicsStart();
}
@Override
public void mouseEntered(MouseEvent arg0) {
}
@Override
public void mouseExited(MouseEvent arg0) {
}
@Override
public void mousePressed(MouseEvent arg0) {
}
@Override
public void mouseReleased(MouseEvent arg0) {
}
}
It's "simple" First you need to figure out which square you are in, then you draw exactly like before, just with a new color Well that's the problem. I can figure out which square was clicked on no problem! But then I have no idea what you are supposed to use to redraw over the old one. Ideally the pseudocode would be: public void repaint(){ getOldPaint(); newPaint = combineOldAndNewPaint(); paintOver(newPaint); } But I don't know any of those commands in Java's Graphics or Swing and haven't been able to find them through trawling for an hour or 2. So I decided to switch over to something I saw used in a guide, which was to have a JFrame and JPanel class. Hopefully this works better.
Probably an easier and more elegant way to do the game would be creating a grid (for example a two dimensional vector) and do the actual playing there.
|
|
|
|
|
|
EPT
