Starting to think my brain just isn't built to code.Gah. I'm trying to stay positive, but I'm struggling so badly with a Coursera mini-project.
It's due in about 56 hours. :SIf you don't struggle with a project it wasn't worth doing.
So much time. You can sleep in about 56 hours.
Gah. I'm trying to stay positive, but I'm struggling so badly with a Coursera mini-project.
I have work tomorrow.
I am. We should team up to help each other!Are you doing the Intro Python course from Rice University? I haven't even started this week's yet.
in complexity theory actually is? I guess when traversing through a list for example, it would be the number of its elements, but surely it's not always that simple? Can anyone help me to grasp what the input size
I feel this should be really easy to understand, but somehow I'm getting hung up on this.
I'm using it for the first time too - from what I undertand, requestAnimationFrame sends a request to the browser to repaint the screen as soon as possible - the time it aims for is meant to give you as close to 60fps as possible, and less when the tab is in the background, to save on power. So, the following gives you 60, as long as you keep the updating under the time of a 1/60th of a second:I have a question to HTML5-gaf (if it exists
I hear that requestAnimationFrame is the new king in town.
Well, I just cant wrap my head around it, honestly.
Currently, the game I am working on uses two loops. One is the update loop, done at set intervals (1000/60 ms, basically), the other is the draw loop, done at set intervals, again (1000/30 ms).
The problem is this: I do not really understand how the requestAnimationFrame decides when to render stuff. And if it aims to 60fps, how can I force 30fps instead? The game uses manually drawn sprites, so there really is no gain for smoother animations, as it would only make the animation finish faster. Do I request an empty frame every time after a normal renderframe for 30fps or what?
Also, I am currently working with two canvases (one for the static backgrounds, other for the UI and the units), but I plan on doing three, actually. The back layer will be the background, the middle layer for animated units (30fps refresh), and the front layer would be the UI, which includes pointers, cursors, menu switches, which can easily be done at 60 or even 120fps, so that would further mess with rAF-s. And I am also thinking of introducing a fourth layer speficially for spell effects, which would mix traditional pixelart with canvas-powered effects. Hm.
function mainloop() {
//...updating, drawing...
requestAnimationFrame(mainloop);
}var fps = 30;
function mainloop() {
//...updating, drawing...
setTimeout(function() {
requestAnimationFrame(mainloop);
}, 1000 / fps);
}var updateFPS = 60,
doDraw = true;
function mainloop() {
//...updating...
if (doDraw){
//...drawing...
}
setTimeout(function() {
doDraw = !doDraw;
requestAnimationFrame(mainloop);
}, 1000 / updateFPS);
}I believe they use your name if you filled in one, while repos will show your username.
...cd /path/to/my/repo$ git remote add origin https://[username]@bitbucket.org/[username]/[folder].git
$ git push -u origin --all # to push up the repo for the first timecd /path/to/my/repogit init$ git remote add origin https://[username]@bitbucket.org/[username]/[folder].gitgit add . # this adds all the filesgit commit -a -m "Initial commit"git push -u origin --allThe C++ way of doing things with streams is a little complicated to set up and understand, but std:
sprintf is not well liked, as you can easily end up with buffer overflow exploits. I may scoff at Microsoft's hated for strcpy and std::transform, but there's a very real problem in sprintf in that you cannot know how big a buffer to allocate for the output.
snprintf is a little safer, as you can both limit the amount of data you write to ensure you remain within your buffer, and you can query the amount of space the formatted output would take up, and be certain you've allocated enough memory for it. Though, this function is only standard in C++11 or C99.