SuperMario | SuperMario at Window os develop by Java with Swing | Theme library

Utter responses are not supposed to be dynamic. Use the action by itself to create a dynamic response.

bg1rect and bg2rect are no pygame.sprite.Sprite objects, but they are pygame.Rect objects.
You have to use the method colliderect rather than pygame.sprite.collide_rect():

print(pygame.sprite.collide_rect(bg1rect, bg2rect))

Your character "A" is not moving because cursorX + 1 and cursorX - 1 will not assign new value (cursor position) to it self. It just adds +1 and substracts -1 from its current value. You need to assign new value to cursorX. You need to use Increment operator (++) and Decrement operator (--).

I checked the original code and cannot find the actual jump mechanics anywhere in Mario.java. I can see if the vertical velocity of mario is other then 0 it should run the jumping animation. So perhaps, if the falling physics are in place and you run off a cliff you will see the jumping animation playing.

So I guess you just need to apply some force to the character. Something along the lines of b2Body.applyForceToCenter(0f,10f,true) or b2Body.setLinearVelocity(0f, 10f);. This could go into the render method when you check for a key press or if you are using a InputProcessor it can go in the keyDown method.

The code you are showing introduces an asynchronous primitive, Promise, which can be passed around and used to access a resource that hasn't been populated yet.

In this case, you want an Image that is fully loaded and has image data that you can use. However, you can't access the image data until a network request finishes that would fetch the image data.

For example, this won't work:

This feels really weird, because you'd typically define solid areas rather than those the player can walk inside. You'll want your player to jump after all, rather than having them glued to the ground.

The rest is pretty straightforward:

• Iterate over all solid objects and determine whether the player and the solid rectangle overlap.
• If they do, determine which distance is smaller (x or y). This lets you determine which axis to move the player.
• Determine which direction the player leaves the solid area quicker, i.e. which direction to push the player.
• Push the player in the calculated direction and repeat the checks.

Depending on your map complexity this can become rather complex, so you'll most likely want some sorting/spatialisation to reduce the number of comparisons (e.g. skip checking impossible/far away shapes).

sf::Time defines these overloads of operator*¹:

I'm not going to rewrite your program to make it multi-threaded as that's behind the scope of answering a specific question. I can give you a description of what's required though as a starting point.

First of all, a simpler way to fix this without threads would be to use something like signals to stop the playing of the tune. This is what happens when you press Ctrl-C. Your program is reading input from your IR though, so as far as I can tell using threads looks necessary to both reading IR input and playing of sound happen at the same time.

I'm not familiar with Arduino but I'm assuming you have something like pthreads. You would need to get familiar with that. It is not a trivial change as using threads is very different paradigm and takes time to get your head around if you haven't used them before. The main thing to get your head around is that code is executing in more than one place.

Your main thread, the beginning process before any thread is created, would be running loop() so it can respond to any IR input. Having it in its own thread lets it respond to any user input. The problem with your code right is that it must wait for the playing of the tune in playSuperMario() to return before it can process any new input.

You would create a thread somewhere during initialization. This thread will be what plays the tune. It needs to be able to start the tune based on IR input. Also you'll need to define the behavior of things like what happens if the "ON" button is pressed while it's already playing? Does it start again, stop or is that ignored and it keeps playing?

You'll need one or more variables used by both threads. This will require mutex protection so only one thread can read/write it at a time. Let's say there's a global variable isPlaying initially set to true. When the off button is pressed this would be changed to false. Your playSuperMario() and buzz(), etc. functions would need to check if this value is false in its loops. If false then it will return immediately.

That's a general pointer to how to handle this hope it helps.