Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Reelya]

I managed to fix the issue by reverse engineering some demos in the end, and tweaking them until they did what I want. It turns out the issue was in trying to encapsulate the physics inside my own sprite class, the scope of the various bits and bobs wasn't being maintained properly, because I just copied the code into the constructor of my class. I had assumed it was an encapsulated system and you just need a "body" object and that's that. But nah, you need to permanently store all the sub shit. It's a messy as hell system and not at all encapsulated, I don't really like the design at all.

[TheBiggerFish]

What?  I don't think instance variables go in the constructor...
I know Java doesn't do instance variables like that.

[Antsan]

Use emacs and autoconfig on the Linux of your choice.

[Antsan]

Yeah, most IDEs seem to be more of a roadblock than helpful.
You'll have to read some stuff about autoconfig, though.

[Antsan]

Well, Debian is pretty configurable on installation, but I guess, if you install a graphical interface, that still has some superfluous stuff.
LFS would be the extreme choice – you only install what you need, but that would take a lot of time.

If you have Windows, there was a nice gui for qemu somewhere. It was really easy to use, very intuitive and stuff.

[miauw62]

...


Install gentoo?

[Reelya]

What?  I don't think instance variables go in the constructor...
I know Java doesn't do instance variables like that.

No, there were some initializer structs that you set the data in then feed to the main Body object. I naively assumed that once you did that you set the Body object permanently then didn't need the initializer structs anymore. But it breaks if the initializer structs go out of scope after they're used and this wasn't well documented.

[TheBiggerFish]

What?  I don't think instance variables go in the constructor...
I know Java doesn't do instance variables like that.

No, there were some initializer structs that you set the data in then feed to the main Body object. I naively assumed that once you did that you set the Body object permanently then didn't need the initializer structs anymore. But it breaks if the initializer structs go out of scope after they're used and this wasn't well documented.

Ah.  I have absolutely no idea what you're talking about.

[3man75]

Hey guys I need help in determning a way to fix the following code:

Spoiler: Code (click to show/hide)

#include <iostream>
#include <cmath>
#include <iomanip>

using namespace std;

int main(){


   float morningRate = 0.12;
   float afternoonRate = 0.55;
   float nightRate = 0.35;

   float startTime;
   int minutes;

   float totalCharge;
   float hours;

   float totalMinuitesAllowed = .59;
   float minuiteRemainder;

   //times
   float timeMorningBegins = 00.00;
   float timeMorning = 06.59;
   float timeAfternoonstart = 07.00;
   float timeAfternoon = 19.00;
   float timeNight = 19.01;
   float nightCap = 23.59;

   //float nightCap is to give a cieling so that not EVERYTING above 19.01 is given. In a sense a invalidation check.
   float fixingMinuites;

   cout << "Input the time your call started." <<
      "Refer to the times above and avoid using negative numbers or numbers outside the rates"
      << endl << endl;
   cin >> startTime;


   //Static cast below is making it so 16 - 16.28. Below I get the decimal of a number.
   minuiteRemainder = startTime - static_cast<int>(startTime);

   cout << minuiteRemainder << endl;
   cout << startTime - static_cast<int>(startTime) << endl;


   if (startTime > 23.59 || startTime < 0){

      cout << "Error starting time cannot be negative or over 23.59." << endl;
   }
   else if (minuiteRemainder > .59 || minuiteRemainder < 0){
      cout << "Error minuites above 59 are not accepted. Nor are negatives.";
      /*19.33 is being caught here.
      Turning it the other way allows for something like 11.111 to be accepted. FIX NEEDED.*/
   }
   else {

      cout << "Please input how long your conversation lasted in minutes." << endl;

      cin >> minutes;

      cout << "MINUTES:" << minutes << " MINREMAINDER: " << minuiteRemainder << endl;

      if (minutes < 0){
         cout << "Error #2. Minutes cannot be inputted as a negative." <<
            "What kind of conversation gives you time anyways? Try again," << endl << endl;
      }
      else if (startTime <= timeMorning || startTime >= timeMorningBegins){
         // In here is my code for the morning rate.
         cout << "Because you talked for: " << minutes << " minutes. It will cost you: "
            << minutes*morningRate << "." << endl;
         cout << "MORNING!";

      }
      //14.-33

The code is for a long-distance charing program that tells you how much to pay when you call someone at some point. You firstly charge by WHEN they call which I get with starting time and how LONG the call was with minutes.


My problem comes in at that if I input 19.-33 it skips my error check at line 51 or else if (miniuteremainder <code>).

I've been told that one way to fix is to nest my If's but I wanted to know why this dosen't work and if it can be tweaked so it can work properly. Also If I start nesting them where should I start nesting them?



Example: call during our morning rates and the call lasted 10 minutes.

morningRate*minutes

mornningrate = X
minutes = 10

[TheBiggerFish]

...Can you take TWO arguments (hours/minutes)?  IE:

Code: [Select]

if(minutes > 59 || minutes < 0)
//throw error OR convert hours to minutes and try again.
if (hours > 24 || hours < 0)
//error, but having the capability to handle days, as unlikely as it
//is to occur in real life, might be a feature to add.


[RulerOfNothing]

If you input 19.-33 into the C++ console input then you get 19 as a result (because C++ stops reading when it encounters an invalid character)

[i2amroy]

So, I've remembered why I haven't ever actually learned openGL or did any major coding project- Codeblocks does not like libraries. At all. I've spent days (literal days) trying to make libraries work with it, and got nowhere. So, I'm ditching it for whatever else you can recommend here for developing code for c++. IDE, text editor, some distro of Linux- I'll take any suggestions at this point.

Personally I'm a huge fan of CLion, though you basically need to be a student or something similar if you want to get it for free (right side of the "buy and renew" page).

[3man75]

...Can you take TWO arguments (hours/minutes)?  IE:

Code: [Select]

if(minutes > 59 || minutes < 0)
//throw error OR convert hours to minutes and try again.
if (hours > 24 || hours < 0)
//error, but having the capability to handle days, as unlikely as it
//is to occur in real life, might be a feature to add.


Prof isn't asking for that stuff yet. but I'm a bit loss on the rest. Are you saying to make a varriable cap for 60 min's and then using that at the conditions?

[TheBiggerFish]

I'm saying get two variables, hours and minutes, and store/check them separately.  So, if I understand you correctly, yes.

[3man75]

I'm saying get two variables, hours and minutes, and store/check them separately.  So, if I understand you correctly, yes.

But why would you make two IF's? If one of the ifs for error are triggered then why check the rest?

Doing If (Hours <24) and if (minutes <.59) would make two seprate checks and that could continue the program despite its answer being flawed.

Also I think I should drop in the complete code to show my gripe. I think it'll be more clear.

Spoiler (click to show/hide)

#include <iostream>
#include <cmath>
#include <iomanip>

using namespace std;

int main(){


   float morningRate = 0.12;
   float afternoonRate = 0.55;
   float nightRate = 0.35;

   float startTime;
   int minutes;

   float totalCharge;
   float hours;

   float totalMinuitesAllowed = .59;
   float minuiteRemainder;

   //times
   float timeMorningBegins = 00.00;
   float timeMorning = 06.59;
   float timeAfternoonstart = 07.00;
   float timeAfternoon = 19.00;
   float timeNight = 19.01;
   float nightCap = 23.59;

   //float nightCap is to give a cieling so that not EVERYTING above 19.01 is given. In a sense a invalidation check.
   float fixingMinuites;

   cout << "Input the time your call started." <<
      "Refer to the times above and avoid using negative numbers or numbers outside the rates"
      << endl << endl;
   cin >> startTime;


   //Static cast below is making it so 16 - 16.28. Below I get the decimal of a number.
   minuiteRemainder = startTime - static_cast<int>(startTime);

   cout << minuiteRemainder << endl;
   cout << startTime - static_cast<int>(startTime) << endl;


   if (startTime > 23.59 || startTime < 0){

      cout << "Error starting time cannot be negative or over 23.59." << endl;
   }
   else if (minuiteRemainder > .59 || minuiteRemainder < 0){
      cout << "Error minuites above 59 are not accepted. Nor are negatives.";
      /*19.33 is being caught here.
      Turning it the other way allows for something like 11.111 to be accepted. FIX NEEDED.*/
   }
   else {

      cout << "Please input how long your conversation lasted in minutes." << endl;

      cin >> minutes;

      cout << "MINUTES:" << minutes << " MINREMAINDER: " << minuiteRemainder << endl;

      if (minutes < 0){
         cout << "Error #2. Minutes cannot be inputted as a negative." <<
            "What kind of conversation gives you time anyways? Try again," << endl << endl;
      }
      else if (startTime <= timeMorning || startTime >= timeMorningBegins){
         // In here is my code for the morning rate.
         cout << "Because you talked for: " << minutes << " minutes. It will cost you: "
            << minutes*morningRate << "." << endl;
         cout << "MORNING!";

      }
      //14.-33

      else if (startTime >= timeAfternoonstart || startTime <= timeAfternoon){
      // In here is my code for the afternoon rate.
      cout << "Because you talked for: " << minutes << " minutes. It will cost you: "
      << minutes*afternoonRate << "." << endl;
      cout << "AFTERNOON!";
      }
      else if (startTime <= timeNight || startTime >= nightCap){
      cout << "Because you talked for: " << minutes << " minutes. It will cost you: "
      << minutes*nightRate << "." << endl;
      cout << "NIGHTTIME!";
      //above is the code for the night rate.
      }

      cout << "Thank you for using our services." << endl;

      }

If you input this and type 19.-33 you'll see it's caught on the second type of error and not the first where it should be caught. I want the -33 to be caught at minute remainder and not minutes. I want to know if this can be tweaked to be correct. If so could you please show me? Otherwise is nesting the If's my only hope?