Update info: Greatly expanded number of classes to provide a better foundation for future updates Began and almost finished file&actor interaction methods for Variables Mode button now works (to an extent) Known issue: Cannot properly switch from the mode changing screen to the main calculator screen

(This was posted yesterday but didn't send) Originally posted for assistance reasons (suggested by danpost) https://www.greenfoot.org/topics/63293/30

https://www.greenfoot.org/topics/63463/ I was asked to post my world code by danpost (even though I had stated that I had posted my scenario and included the link to the scenario) and my comment was auto-marked as spam. It contained zero spam or offensive language. I am now not allowed to continue to ask for help on my own discussion for the duration of the review period. It's been 2 days. The review period is meant to be 24h. This project is due in less than 2 weeks and I don't have time for this. Please help.

Notice for those who intend to use this scenario: (This is my 2nd alternate account after my main account and first alternate account were put under review for comments that contained code which contained links to external java-help-related sites within comments. I uploaded this scenario on my main account, 444Jam444) This project was being made for a school project in which I had to abide by the documentation that I had made prior to the task. Unfortunately, when creating the documentation for this project, I underestimated the workload and overestimated my abilities and the time period for implementing this solution. With the due date right around the corner, and my 72-page documentation in dire need of changes before the due date (<2 days), it is unlikely that many major changes will occur before then. As this is not a passion project either, I am unlikely to continue working on it after the due date. Be warned, the software contains an unhealthy amount of bugs that I have no idea the cause behind them, code that has been untested, as well as a complete and utter lack of intrinsic documentation due to lack of time. I have, however, included the links to the sites that I used to help me (Disclaimer: CLICK AT YOUR OWN RISK! I'm not responsible for any user of this scenario clicking on any links within the scenario's source code! While I can say that I'm sure none of the links are harmful, I am not at fault for any user going to any links in the source code. I've already had 2 accounts under review for similar reasons). For those interested in improving this scenario, I give permission for anyone to use the source code as their own, as long as it is used for non-commercial use, as long as user 444Jam444 is mentioned.

Known bugs: Mode, Alpha, Store do not have an image for being invalid, nor do they have the required methods. Little-to-no interaction has been put in place for the Alpha button. Del and AC disappear when valid, despite having an image for being valid. Index has issues, the last index of the calculation string cannot be accessed, and as a result, the first input actually becomes the last input, whereas following inputs behave as normal unless the user attempts to place their next input at the last index. Currently, pressing = throws an index out of bounds error due to some faulty regex on line 299 of Calculate. Buttons disappear if invalid when the Calculator first initialises, only to reappear when a button is pressed. The calculation will go off screen if the user provides too much input. Possible issues: A plethora of unknown issues in code that has remained untested, such as; makeshift click-and-drag code in other worlds, makeshift code used for a search algorithm, most of the software. Unfinished areas such as displaying files for the user to read through and select.

It still doesn't work a little, when calculating some example, the program stops + everything is calculated in "int", it is better if it is in "dooble". a little help, in order to remove any errors on stopping the program, use try {"Dangerous code"}catch(Exception e){}

try{ "Dangerous code" }catch(Exception e){}

Yeah, I have been using try...catch. Some calculations are in int due to either a. poor design choices earlier on with less understanding b. rounding due to the absolute complexity of trying to calculate things like "(decimal)!" Also, the project was way too ambitious for the time constraints. Never trust your past-self to make good decisions. Past-me is an idiot.

It is a little jank, but this is the first time in the entire history of the existence of this project that it can calculate something at all, just happens to be the day before it's due. Not much I can really do without decreasing the potential for getting marks in the submission of the project.

I appreciate your good wishes in my development. Except my development ends in about 6h 50minutes when this project is due... I might not continue development after, but I'll probably let someone else pick it up as long as I'm credited :)