- Forum
- General C++ Programming
- X and Y coordinate problems
X and Y coordinate problems
closed account (GbX36Up4)
Here is my code so far:
#include <allegro.h>
int x = 10;
int y = 10;
int textboxy1 = 400;
int main()
{
allegro_init();
set_color_depth(32);
install_keyboard();
set_gfx_mode(GFX_AUTODETECT_WINDOWED, 1040, 680, 0, 0);
while ( !key[KEY_ESC]) {
clear_keybuf();
acquire_screen();
textout_ex(screen, font, "________________________________________________________________________________________________________________________________", 7, textboxy1, makecol(255, 255, 255), makecol(0, 0, 0));
textout_ex(screen, font, "#", 40, 40, makecol(255, 255, 255), makecol(0, 0, 0));
textout_ex(screen, font, " ", x, y, makecol(0, 0, 0), makecol(0, 0, 0));
if (key[KEY_UP]) --y;
if (key[KEY_DOWN]) ++y;
if (key[KEY_LEFT]) --x;
if (key[KEY_RIGHT]) ++x;
if (x == 1){ ++x;}
if (y == 399){ --y;}
if (y == 0){ ++y;}
if (x == 1032){ --x;}
if (x > 30 && x < 41) { --x;}
if (x < 30 && x > 41) { ++x;}
if (y > 30 && y < 41) { ++y;}
if (y < 30 && y > 41) { --y;}
textout_ex(screen, font, "e", x, y, makecol(0, 0, 255), makecol(0, 0, 0));
release_screen();
rest(5);
}
return 0;
}
END_OF_MAIN();
I placed a wall (#) and basically i need it so that if you coordinates are ? and ? then you cannot continue. I tried using
if (x > 30 && x < 41) { --x;}
if (x < 30 && x > 41) { ++x;}
if (y > 30 && y < 41) { ++y;}
if (y < 30 && y > 41) { --y;}
but it just ends up letting me pass by the Y but then I cannot go back up and then I cannot pass the x at all. The line at the bottom is supposed to be there, in the future it will be where diolouge (excuse my spelling XD) will be displayed. I tried not using the && and just having only one test per each if statement but that didn't work either. I don't know if it is the way i'm coding or if it is impossible simply using ifs. Any help is appreciated. Thanks!
#include <allegro.h>
int x = 10;
int y = 10;
int textboxy1 = 400;
int main()
{
allegro_init();
set_color_depth(32);
install_keyboard();
set_gfx_mode(GFX_AUTODETECT_WINDOWED, 1040, 680, 0, 0);
while ( !key[KEY_ESC]) {
clear_keybuf();
acquire_screen();
textout_ex(screen, font, "________________________________________________________________________________________________________________________________", 7, textboxy1, makecol(255, 255, 255), makecol(0, 0, 0));
textout_ex(screen, font, "#", 40, 40, makecol(255, 255, 255), makecol(0, 0, 0));
textout_ex(screen, font, " ", x, y, makecol(0, 0, 0), makecol(0, 0, 0));
if (key[KEY_UP]) --y;
if (key[KEY_DOWN]) ++y;
if (key[KEY_LEFT]) --x;
if (key[KEY_RIGHT]) ++x;
if (x == 1){ ++x;}
if (y == 399){ --y;}
if (y == 0){ ++y;}
if (x == 1032){ --x;}
if (x > 30 && x < 41) { --x;}
if (x < 30 && x > 41) { ++x;}
if (y > 30 && y < 41) { ++y;}
if (y < 30 && y > 41) { --y;}
textout_ex(screen, font, "e", x, y, makecol(0, 0, 255), makecol(0, 0, 0));
release_screen();
rest(5);
}
return 0;
}
END_OF_MAIN();
I placed a wall (#) and basically i need it so that if you coordinates are ? and ? then you cannot continue. I tried using
if (x > 30 && x < 41) { --x;}
if (x < 30 && x > 41) { ++x;}
if (y > 30 && y < 41) { ++y;}
if (y < 30 && y > 41) { --y;}
but it just ends up letting me pass by the Y but then I cannot go back up and then I cannot pass the x at all. The line at the bottom is supposed to be there, in the future it will be where diolouge (excuse my spelling XD) will be displayed. I tried not using the && and just having only one test per each if statement but that didn't work either. I don't know if it is the way i'm coding or if it is impossible simply using ifs. Any help is appreciated. Thanks!
closed account (GbX36Up4)
I found a solution, just create another if statement so that if he is passing through 1 - 39 THEN HE CAN pass through, otherwise he can't. Thanks for the help anyway D:<
closed account (GbX36Up4)
Still not working D: really frustrated.
#include <allegro.h>
int x = 10;
int y = 10;
int textboxy1 = 400;
int pastlocy;
int pastlocx;
int main()
{
allegro_init();
set_color_depth(32);
install_keyboard();
set_gfx_mode(GFX_AUTODETECT_WINDOWED, 1040, 680, 0, 0);
while ( !key[KEY_ESC]) {
clear_keybuf();
acquire_screen();
textout_ex(screen, font, "________________________________________________________________________________________________________________________________", 7, textboxy1, makecol(255, 255, 255), makecol(0, 0, 0));
textout_ex(screen, font, "#", 40, 40, makecol(255, 255, 255), makecol(0, 0, 0));
textout_ex(screen, font, " ", x, y, makecol(0, 0, 0), makecol(0, 0, 0));
if (key[KEY_UP]) --y;
if (key[KEY_DOWN]) ++y;
if (key[KEY_LEFT]) --x;
if (key[KEY_RIGHT]) ++x;
if (x == 1){ ++x;}
if (y == 399){ --y;}
if (y == 0){ ++y;}
if (x == 1032){ --x;}
if (y == 29) { pastlocy = 29;}
if (y == 32) { pastlocy = 32;}
if (x == 29) { pastlocx = 29;}
if (x == 32) { pastlocx = 32;}
if (x > 30 && x < 31) { --x;}
if (x < 30 && x > 31) { ++x;}
if (y > 30 && y < 31) { ++y;}
if (y < 30 && y > 31) { --y;}
if ( x > 1 && x < 30 && pastlocy == 29) { ++y;}
if ( x > 1 && x < 30 && pastlocy == 32) { --y;}
pastlocy = 0;
if ( y > 1 && y < 30 && pastlocx == 29) { ++x;}
if ( y > 1 && y < 30 && pastlocx == 32) { --x;}
pastlocx = 0;
textout_ex(screen, font, "e", x, y, makecol(0, 0, 255), makecol(0, 0, 0));
release_screen();
rest(5);
}
return 0;
}
END_OF_MAIN();
My guess is that after going down it re-registers the pastloc or something?
#include <allegro.h>
int x = 10;
int y = 10;
int textboxy1 = 400;
int pastlocy;
int pastlocx;
int main()
{
allegro_init();
set_color_depth(32);
install_keyboard();
set_gfx_mode(GFX_AUTODETECT_WINDOWED, 1040, 680, 0, 0);
while ( !key[KEY_ESC]) {
clear_keybuf();
acquire_screen();
textout_ex(screen, font, "________________________________________________________________________________________________________________________________", 7, textboxy1, makecol(255, 255, 255), makecol(0, 0, 0));
textout_ex(screen, font, "#", 40, 40, makecol(255, 255, 255), makecol(0, 0, 0));
textout_ex(screen, font, " ", x, y, makecol(0, 0, 0), makecol(0, 0, 0));
if (key[KEY_UP]) --y;
if (key[KEY_DOWN]) ++y;
if (key[KEY_LEFT]) --x;
if (key[KEY_RIGHT]) ++x;
if (x == 1){ ++x;}
if (y == 399){ --y;}
if (y == 0){ ++y;}
if (x == 1032){ --x;}
if (y == 29) { pastlocy = 29;}
if (y == 32) { pastlocy = 32;}
if (x == 29) { pastlocx = 29;}
if (x == 32) { pastlocx = 32;}
if (x > 30 && x < 31) { --x;}
if (x < 30 && x > 31) { ++x;}
if (y > 30 && y < 31) { ++y;}
if (y < 30 && y > 31) { --y;}
if ( x > 1 && x < 30 && pastlocy == 29) { ++y;}
if ( x > 1 && x < 30 && pastlocy == 32) { --y;}
pastlocy = 0;
if ( y > 1 && y < 30 && pastlocx == 29) { ++x;}
if ( y > 1 && y < 30 && pastlocx == 32) { --x;}
pastlocx = 0;
textout_ex(screen, font, "e", x, y, makecol(0, 0, 255), makecol(0, 0, 0));
release_screen();
rest(5);
}
return 0;
}
END_OF_MAIN();
My guess is that after going down it re-registers the pastloc or something?
Your code isn't making any sense. Try something like this:
|
|
I propose a design change. Right now, you're letting the player move and then you check to see if they are in a wall or if they are going off the screen. A better solution would be to check where the player will be going and if they are not going to hit a wall or about to go off the screen then let them move, otherwise don't let them move.
Also, just so you know, none of these conditions will ever be satisfied:
And I don't know what you're doing with these:
"If x is between 1 and 30 exclusively and if y is 29 (since paslocy == y in this case), then increment y". I can't grasp how that would be useful. Same thing with all the other similar cases. Whatever they are, they're wrong ;)
Anyway, it'll probably be a lot easier to get it to work if you check first then move as opposed to the other way around.
Also, just so you know, none of these conditions will ever be satisfied:
|
|
And I don't know what you're doing with these:
if ( x > 1 && x < 30 && pastlocy == 29) { ++y;}"If x is between 1 and 30 exclusively and if y is 29 (since paslocy == y in this case), then increment y". I can't grasp how that would be useful. Same thing with all the other similar cases. Whatever they are, they're wrong ;)
Anyway, it'll probably be a lot easier to get it to work if you check first then move as opposed to the other way around.
closed account (GbX36Up4)
@Modshop
if y is greater than 0, that means that if they are at 1 they can still move off the screen, so shouldn't be:
? My new solution was that if the whole of x and y was being pushed back, and i was pushing forward with a new statement, wouldn't they cancel each other out? So I was simply going to write it as:
@shacktar
That code I used to tell if they are coming from above, below, left or right. lets say they are coming through from below and pass through x 1 and x 39. Well my solution was to make it so that they CAN pass through 1 - 39, but not through 40. To do so i have to simply make:
the pastloc lets me see if they are coming from above, below, left, or right, so i can either --y, --x, ++y, or ++x, depending on the situation because a simple ++x wont work for all possible directions.
I must be stupid, there is no integer between 30 and 31 -_-
**EDIT** Upon having a good nights rest and looking over this code I can easily say I was in some sort of stupid state while writing this code. Most things I cannot remember writing or why they are even there, I'm going to spend some time re-writing things and get back to you when I get things back to "normal"
if (key[KEY_UP] && y>0) y--;if y is greater than 0, that means that if they are at 1 they can still move off the screen, so shouldn't be:
if (key[KEY_UP] && y>1) y--;? My new solution was that if the whole of x and y was being pushed back, and i was pushing forward with a new statement, wouldn't they cancel each other out? So I was simply going to write it as:
|
|
@shacktar
That code I used to tell if they are coming from above, below, left or right. lets say they are coming through from below and pass through x 1 and x 39. Well my solution was to make it so that they CAN pass through 1 - 39, but not through 40. To do so i have to simply make:
if ( x > 1 && x < 30 && pastlocy == 29) { ++y;}the pastloc lets me see if they are coming from above, below, left, or right, so i can either --y, --x, ++y, or ++x, depending on the situation because a simple ++x wont work for all possible directions.
|
|
I must be stupid, there is no integer between 30 and 31 -_-
**EDIT** Upon having a good nights rest and looking over this code I can easily say I was in some sort of stupid state while writing this code. Most things I cannot remember writing or why they are even there, I'm going to spend some time re-writing things and get back to you when I get things back to "normal"
Last edited on
closed account (GbX36Up4)
|
|
The main loop of the game makes it so that currentmsg always equals 1, regardless to if they pressed x or not. As far as I know there is no way to NOT do a loop, and still not have variables be re-assigned every loop unless I learn how to multithread? or I can make an if statement to figure out if x has been pressed yet, and if it has the message will never again show up? but in a long term project it will be hard having to constantly create and change variables just to tell if a button has been pressed.
closed account (GbX36Up4)
if (key[KEY_LEFT] && y > 40 && y < 150 && x == 30){ --x;}Even more problems...
| The main loop of the game makes it so that currentmsg always equals 1, regardless to if they pressed x or not. |
Is that what you want? If not, you can declare/initialize currentmsg outside the loop.
| As far as I know there is no way to NOT do a loop, and still not have variables be re-assigned every loop unless I learn how to multithread? |
I've read this question a bunch of times and it doesn't make any sense to me :(
| I can make an if statement to figure out if x has been pressed yet, and if it has the message will never again show up? |
That seems like a good solution. With good design, the "has a button been pressed" issue shouldn't be a big deal. Realistically, you would only need to keep track of the state of only a few special keys.
closed account (GbX36Up4)
Thanks, I am currently creating collisions, I finally got it to work right, now I'm having some simple x, and y problems that will be fixed after some testing:
|
|
closed account (GbX36Up4)
|
|
I have mastered the art of collision :D
Topic archived. No new replies allowed.