Hi @user1406 and welcome to the CS50 community. Here you go,
In order to declare a new variable, in the variables palette, click "Make a Variable". A box will appear. Type the name of the variable you want to create, and select weather it should be "for all sprites" (global) or "for this sprite only" (private). Press OK. The image of the button looks like:
Head to CS50 Submit and choose your pset on the left under Assignments
Under My History, you should see your submissions for this pset. Click on the top-most submission
On the screen that appears, you should see a window with No File
Selected. If you move your mouse toward the window’s lefthand side,
you should see a list of the files you uploaded. ...
Don't worry about the wrong submission and you don't have to resubmit the form again. You may drop Robert Bowden a note at email@example.com about the ungraded psets providing your edX email and name.
You don't need an XID account for CS50x. You just need an Edx account to enroll in the course, which will also serve as your CS50 Submit authentication.
The only deadline for the 2015 offering of the course is December 31, 2015, by which all projects should be submitted. There is a proposed schedule for Edx students available if you need the psychological ...
Yes, you can continue. Any pset that you have submitted and has been graded will carry forward. However, to continue, you must do the 2017 course psets (it's actually the Harvard on-campus fall 2016 material). Additionally, if you want to redo any psets that have been graded, you would need to do the new psets instead.
To repeat, if it's been graded, it'...
The new versions of submit50 and check50 require cs50/ at the beginning of the problem identifier. The submission instructions have been updated to reflect this. The correct identifier is now cs50/2017/x/crack.
Yes, you can. The final deadline is 31 Dec 2014.
pset0 isn't submitted through the submit page. The instructions are listed at the end of the pset.
How to Submit
To submit this problem set, head to the URL below.
You’ll find that a few questions await. Be extra-sure that your answers are correct, particularly your email ...
While your program will likely pass the automated tests of C50, in terms of design, you could think of the following:
As per the problem description,
Visa uses 13- and 16-digit numbers
Your program seems to consider a 13-digit number invalid
You may not necessarily need to duplicate card into card1 and run them digit-to-digit twice to do the checks. ...
The new submission system went into effect a couple of days ago (July 29, 2019).
You can submit your final project directly on github. You are only required to submit a README.md file describing your project, so the easiest is to do that directly on github.com
First, go to http://cs50.me/cs50x and make sure you are set up for the CS50x course in the new ...
One of your issues is you appear to be using the Harvard Fall 2016 problem sets, which are no longer active (and are for registered Harvard students).
If you are an edX student, be sure you are using the edX materials found here: https://courses.edx.org/courses/course-v1:HarvardX+CS50+X/courseware
Also, hello.c is no longer graded because the code is ...
I'm no expert, but I thought I'd give it a try since I just finished the problem set myself:
Your questions 1 and 2 are related. GET and POST are methods that determine how data is submitted to the server. With GET the data is appended to the URL (for example when you search 'cats' on Google, you can see 'cats' in the search results' URL). POST carries the ...
The button does the action defined in the action attribute of the <form> tag. text is not a valid type for a button (see MDN doc on button and form) but it doesn't fail because, well, browsers have to be very (very) forgiving because there is a lot of bad code out there. If you validate your code (type="text") with a code validator (for example Nu Html ...
You have changed the board logging routine and that is what check50 is complaining about. check50 depends on that output (log.txt) to verify the result. Here is the routine from the distribution code:
// log the current state of the board (for testing)
for (int i = 0; i < d; i++)
for (int j = 0; j < d; j++)
The 2016 course deadline has passed. The 2017 submissions haven't opened yet. But you don't have to resubmit any psets that have already been graded, as your gradebook will carry over to the 2017 course. You need only submit psets that you haven't already submitted. (but not yet, as the 2017 submissions system is changing and is not yet ready).
The code has two serious problems. First, it is trying to write to a file that hasn't been opened. The code checks for the signature in the first block and doesn't find it. Then, the first line after the if statement's code block for opening the file, the fwrite() call tries to write to temp, which hasn't been opened yet. This is the seg fault.
Second, you ...
load(). Scope. Pointers. Remember, when you return to the caller (main), you don't expect the address of content to be different, only the contents of content. Since &content is passed to load, this line content = malloc(sizeof(BYTE) * BYTES); changes that address (and the reallocs change it again). This line from the spec applies:
stores the ...
I may be wrong, but it seems to me that if you zip all the files together in the directory that you built the executable, including the modified make file, and then upload, it should work. If not, you can always resubmit a working solution later.
As a test, look at the command used to run check50 locally:
check50 2014.fall.pset5.speller dictionary.c ...
The problem was very funny =)
I understood incorrect description : "hardcode file name"
Before that i just forced user to type file name card.raw, i thought this was requirement by:
For simplicity, you should hard-code "card.raw" in your program; your program need not accept any command-line arguments.
Just haven't read it carefully ^_^
Yes, I am. I tried it through both Chrome within the appliance (per the pset instructions), then through Chrome on my Mac OS, and I got the same behavior. I then tried through Safari and it worked, so it must be a cache issue. I will mark the issue as resolved.